SUA (Special Use Airspace)

Rod wrote:

Can any decipher the problem here? We just received a file for use with GNII
(ex-Cambridge) that contains all the special use airspace / glider zones,
etc., for Switzerland. When I load the file the follow message appears and
must be tapped through about 100 times before it end (get to the end of the
code):

"SUA latitude out of range."

0 deg, 73 min, 75 sec

"SUA longitude out of range."

0 deg, 72 min, 95 sec

I realize that it may look like the obvious, i.e. 72 minutes and 75 seconds,
but I find nothing that appears to be out of whack. Any help would be
appreciated. The file is attached in case anyone would care to have a look.

Thanks,
Rod

Name: Airspace.sua
Airspace.sua Type: unspecified type (application/octet-stream)
Encoding: x-uuencode

After a look on the file, I conjecture that the coordinates are in the form
Nddmmss Edddmmss, where d's are degrees, m's minutes ans s's seconds. Nothing
seems to be wrong in the file, except the line number 1090 containing:

POINT=N472810 E0053671

where the minutes of longitude (71) exceed 60.

OTOH I searched for lines containing the values shown in the error
messages, as contiguous sequence of numbers, i.e. 7375 or 7295, and found
only the followimg ones, prefixed by their line number:

317 CLOCKWISE RADIUS=10.000 CENTRE=N473758 E0072958 TO=N474537 E0072026
348 ANTI-CLOCKWISE RADIUS=10.000 CENTRE=N473758 E0072958 TO=N472855 E0072341
353 CLOCKWISE RADIUS=20.000 CENTRE=N473757 E0072953 TO=N474416 E0070148
363 ANTI-CLOCKWISE RADIUS=20.000 CENTRE=N473757 E0072953 TO=N472625 E0070548
367 CLOCKWISE RADIUS=25.060 CENTRE=N473758 E0072958 TO=N474441 E0065414
377 ANTI-CLOCKWISE RADIUS=25.060 CENTRE=N473758 E0072958 TO=N472722 E0065627
658 POINT=N473754 E0091356
1217 POINT=N462655 E0073756
1404 POINT=N472951 E0071150

Nothing wrong I can see in these lines, but maybe they contained some parasite
(non printing) character that was dropped when the file was attached.

Otherwise I conjecture some failure during download (bad cable ? bad connector ?)
that produced loss or duplication of some characters.

Try opening the file in SeeYou, which supports that format. It might be
easier to analyze the error there.

Robert Ehrlich wrote:

Rod wrote:

Can any decipher the problem here? We just received a file for use with GNII
(ex-Cambridge) that contains all the special use airspace / glider zones,
etc., for Switzerland. When I load the file the follow message appears and
must be tapped through about 100 times before it end (get to the end of the
code):

"SUA latitude out of range."

0 deg, 73 min, 75 sec

"SUA longitude out of range."

0 deg, 72 min, 95 sec

I realize that it may look like the obvious, i.e. 72 minutes and 75 seconds,
but I find nothing that appears to be out of whack. Any help would be
appreciated. The file is attached in case anyone would care to have a look.

Thanks,
Rod

Name: Airspace.sua
Airspace.sua Type: unspecified type (application/octet-stream)
Encoding: x-uuencode


After a look on the file, I conjecture that the coordinates are in the form
Nddmmss Edddmmss, where d's are degrees, m's minutes ans s's seconds. Nothing
seems to be wrong in the file, except the line number 1090 containing:

POINT=N472810 E0053671

where the minutes of longitude (71) exceed 60.

OTOH I searched for lines containing the values shown in the error
messages, as contiguous sequence of numbers, i.e. 7375 or 7295, and found
only the followimg ones, prefixed by their line number:

317 CLOCKWISE RADIUS=10.000 CENTRE=N473758 E0072958 TO=N474537 E0072026
348 ANTI-CLOCKWISE RADIUS=10.000 CENTRE=N473758 E0072958 TO=N472855 E0072341
353 CLOCKWISE RADIUS=20.000 CENTRE=N473757 E0072953 TO=N474416 E0070148
363 ANTI-CLOCKWISE RADIUS=20.000 CENTRE=N473757 E0072953 TO=N472625 E0070548
367 CLOCKWISE RADIUS=25.060 CENTRE=N473758 E0072958 TO=N474441 E0065414
377 ANTI-CLOCKWISE RADIUS=25.060 CENTRE=N473758 E0072958 TO=N472722 E0065627
658 POINT=N473754 E0091356
1217 POINT=N462655 E0073756
1404 POINT=N472951 E0071150

Nothing wrong I can see in these lines, but maybe they contained some parasite
(non printing) character that was dropped when the file was attached.

Otherwise I conjecture some failure during download (bad cable ? bad connector ?)
that produced loss or duplication of some characters.

--
Change "netto" to "net" to email me directly

Eric Greenwell
Washington State
USA

Eric Greenwell wrote:

Try opening the file in SeeYou, which supports that format. It might be
easier to analyze the error there.

I should elaborate: when I've had SUA file problems, Glide Navigator
would often choke on it, but SeeYou would attempt to display it anyway.
The bad airspace would be immediately obvious on map, allowing me to go
to the right place in the file and fix it.
--
Change "netto" to "net" to email me directly

Eric Greenwell
Washington State
USA

Thanks for tips on the screwy file. This is supposed to be the updated
version for the upcoming Swiss Championships next week. Re the download
issue, other who use GNII are experiencing the same problems.

I'll pull it up in SeeYou and see what happens.

Regards,
Rod