Re: x2sys confusion

Thanks for the report.  There were two issues:
1) the multi-segment support had a bug when assigning segment numbers
2) there were no support for 360-degree wrapping

I have addressed these problems in r12693 (GMT5) and r10174 (GMT4).  Attached is revised output figure.
-p

On Jan 1, 2014, at 4:24 PM, 杨磊 <[email protected]> wrote:

> Dear community,
> 
> I use the GMT x2sys to calculate crossover of some tracks, but error happens.
> here is the confusing result <trackshy2.png>
> two crossover points are right, but others near the equator are wrong.
> The data and def file were attached. 
> the codes are :
> gmt x2sys_init CROSSHY2 -Dxys -V -I1 -Cg -Etxt -Gg -Ndk -Wd8 -F 
> gmt x2sys_cross -TCROSSHY2 srl_test_gdr005.txt -Qi -W5 -Ia -V2 > COE_orig.txt
> gmt psbasemap -Rd -JQ4i -P -K -Bxa60 -Bya10g10 -BWSen >trackshy2.ps  
> gawk "NR>4 {print $1,$2,$11}" COE_orig.txt > data.d
> gmt psxy -R -J -O -K  data.d -Sc0.2i  >> trackshy2.ps
> gmt psxy srl_test_gdr005.txt -Sc0.01c -R  -J -P -O  >>trackshy2.ps
> 
> 
> So, where is the point ? the GMT is 5.1.0
> To unsubscribe, send the message "signoff gmt-help" to [email protected] <srl_test_gdr005.txt><xys.def>


To unsubscribe, send the message "signoff gmt-help" to [email protected]