Closed lordfolken closed 7 months ago
According to naviter cup file document: https://downloads.naviter.com/docs/SeeYou_CUP_file_format.pdf
Number field representing the frequency of the airport of length 7. Decimal separator must be a point. It can also be embraced in double quotes: https://en.wikipedia.org/wiki/Airband and is used only in connection with waypoint styles 2, 3, 4, 5
There is also a formatting limit as to the digits: Char0 1 char1 1-3 Char2 0-9 ...
Please remove the NDB/VOR frequencies from the freq field in the cup export. The thought is nice, but unfortunalty violates the standard.
Thanks for the heads up. Fix is online! Complete set of export files available tomorrow.
Super speedy as always! Thank you.
I checked today, and the frequency is still in the field. Could you check? (I take the files from the googlestorage)
Hm, at least for me the columns are now correct, e.g. https://console.cloud.google.com/storage/browser/_details/29f98e10-a489-4c82-ae5e-489dbcd4912f/de_nav.cup;tab=live_object?project=openaip-187622. The frequency is in column 11 with the "freq" header.
Hey, maybe a missunderstanding:
When i download de_nav.cup: name,code,country,lat,lon,elev,style,rwdir,rwlen,rwwidth,freq,desc "ALLGAEU","ALG",DE,4759.833N,01015.733E,617.0M,10,,,,341.000,"NAVAID, ID ALG, Frequency 341.000, Range 25 NM, Magnetic declination 3.476, Aligned to true north FALSE"
Field 11 should be empty for a waypoint type 10. Frequency field is only valid for waypoint types 2,3,4,5 (airfields). Also the frequency has to start with 1 i.e. only Radio Communication frequencies.
I really wish the standard wheren't so limited. But at the moment its what we've got. Thank you. :-)
Ah, yes, I misunderstood. Changes are being deployed now.
Hi,
It seems that the navaid export, is to verbose on the frequency fields It seems to add the word Frequency infront of the frequency. The Frequency field should only be the number.