Turnpoint descriptions

Paul Remde wrote:
Hi,

I suggest you take a look at some of the waypoint files on the Worldwide
Soaring Turnpoint Exchange by John Leibacher at:
http://acro.harvard.edu/SOARING/JL/TP http://acro.harvard.edu/SOARING/JL/TP

If I understand correctly, John uses perl scripts to create the waypoint
files from data sources. I've found that names are shortened very nicely.
If you asked him, I bet he'd share his method with you. I think the method
involves removing vowels (only when necessary) and using capitals for the
start of new words.

Good Luck,

Paul Remde

"Tuno" wrote in message
ws.com... ws.com...
While working recently on a Java program to combine and geographically
filter turnpoints from multiple .CUP files, I noted that when I use SeeYou
to convert from .CUP to .DA4 (for Filser/LX Nav products) format, the
turnpoint names get truncated to 8 characters and all uppercase. This
presents name collisions for pairs of turnpoints with verbose names like
"Black Canyon North" and "Black Canyon South" -- both get saved with the
name "BLACK CA", which causes LXe to complain when the file is loaded
therein.

Is there a "standard" somewhere for what data are contained in turnpoints
and how they are named? I know .DA4 files are used for LX Nav products;
what
are .CUP files used for (besides SeeYou)?

thx/2NO



And Perl is highly portable between platforms - text manipulation is its forte, but it can equally well handle binary with ease with good format handling.

Rgds,

Derrick.