Gliding Software > TpSelect
Waypoints exported to SeeYou Cup file error
Chris Lewis:
I exported points within 250Km of Lasham and the waypoints were selected correctly but Latitude was output as E000 00 000 instaed of correct reference. IS there a fix for this
jeff:
I just tried this with TpSelect V2.1 and found no problems. For example, the entry for Lasham is:
--- Code: ---"Lasham Clubhouse","LAS",UK,5111.359N,00101.899W,618ft,4, , ,,"Turn Point, Centre of Clubhouse, Clubhouse is N of peritrack, E of Hangar. P-L, ##. Difficult to find."
--- End code ---
You'll note that in SeeYou format, the cardinal letter comes at the end of the coordinate, not at the beginning as in your example. This is what confuses me.
If you could post the line for LAS you got in your file, it would help me to work out what might be causing your problem.
Chris Lewis:
Jeff,
Here's a copy from the cup file I exported from TP Select. The file appears to contain the latitude but when I open it in SeeYou the Latitude read E000 00 00. I have upgraded from 3.31 to 3.5 of SeeYou to see if this cured the problem but the same happens on both releases.
Any Clues? The previous release of TPSelect appeared to work with cup files.
Chris Lewis
"Lasham Start Southeast","LA1",UK,5109.832N,00059.906W,538ft,1, , ,,"Turn Point, Centre of complex of chicken sheds, Southwood Farm, 2 NMl SE of airfield, ##. Local knowledge required."
"Lasham Start East","LA2",UK,5111.656N,00100.639W,574ft,1, , ,,"Turn Point, Concrete Plinth, Centre of rectangle of concrete surrounded by woods - Oil Installation, ##. Local knowledge required."
"Lasham Church","LA3",UK,5110.692N,00102.033W,600ft,1, , ,,"Turn Point, Spire, Village centre, SW side of airfield, ##. Difficult to find."
"Lasham Start South","LA4",UK,5110.179N,00102.644W,581ft,1, , ,,"Turn Point, A 339 crossroads, Where Lasham/Bentworth road crosses A 339, ##. Difficult to find."
"Lasham Start West","LA5",UK,5111.098N,00106.360W,548ft,1, , ,,"Turn Point, Moundsmere Manor Swimming Pool, Pool is immediately W of large country houseW of a large area of woodland, #. Local knowledge required."
"Lasham Start North","LA6",UK,5112.551N,00103.076W,568ft,1, , ,,"Turn Point, Herriard Church Tower, 1.5 NMl NNW of airfield, just E of A 339, #. Local knowledge required."
"Lasham Finish West","LA7",UK,5111.294N,00102.501W,615ft,1, , ,,"Turn Point, N of W end of peritrack, E of road access from A339, ##. Local knowledge required."
"Lasham Golden Pot","LA8",UK,5111.051N,00059.295W,600ft,1, , ,,"Turn Point, B3349 crossroads, Golden Pot pub east of airfield. Odiham ATZ to N, ##. Difficult to find."
"Langport","LAG",UK,5102.471N,00249.181W,161ft,1, , ,,"Turn Point, A372/Rail, A372 br over rly E edge of town. Yeovilton traffic to the SE. Difficult to find."
Chris Lewis:
Jeff,
This is a copy of the Cup file created by previous release of TpSelect and trhis imports OK to SeeYou
"LASHAM CLUBHOUSE",LASH1M,UK,5111.367N,00101.900W,189.0m,1,,,,"CLUBHOUSE"
"LASHAM FINISH W",LA7,UK,5111.483N,00102.833W,188.4m,1,,,,
"LASHAM START SE",LA1,UK,5110.383N,00100.517W,188.4m,1,,,,
"LASHAM START W",LA5,UK,5111.167N,00106.600W,188.4m,1,,,,
The last 3 entries I added manually in See Youm the lashgam clubhouse entry was from the TPSelect extract.
Looking at the file the new file appear to contain a lot more information.
Regards
Chris Lewis
jeff:
Well I'm assuming you exported that file from SeeYou, because it's not the original file created by TpSelect. TpSelect outputs the BGA trigraphs, so I'm not sure where LASH1M came from. Also TpSelect elevations are specified in feet not metres. You would probably get it expressed in metres on a file export from SeeYou, though.
The latest release (V2.1) was specifically to fix an unrelated problem with SeeYou format and was tested successfully by the two people that asked for the change.
So while you are obviously experiencing a problem, it cannot be quite as you describe it. Can you try creating a fresh TpSelect file and importing that into SeeYou?
Navigation
[0] Message Index
[#] Next page
Go to full version