Sector file tools for conversion of coordinates

[Adrian Bjerke]

@Jonas Kuster

I am getting multiple incorrect coordinate convertions now - here are two examples:

594700N 0080917E  gets translated as N059.46.60.000    E008.09.17.000
595349N 0090000E gets translated as N059.53.49.000    E900000000001.00.00.000

[Jonas Kuster]

Once again many thanks for using this tool and reporting the issues you have. Sorry it took a little longer to share the next update. But I had to rework different parts of the code to ensure compatibility with the latest script engine version of the web server. I used this opportunity to check the feedback I received after the previous update.

 

On 5/16/2022 at 11:35 AM, Andreas Fuchs said:

Would it be possible to add "Qutescoop" as output format?

Looking at your examples, I assume the format is DD.dd (so just a short version of the Decimal format, with decimal places instead actual minute values (0-60)). Happy to support you there. So I've added this format to the selection. Maybe do some tests to verify if the outputs are as expected.

 

On 5/16/2022 at 10:33 PM, Jannes van Gestel said:

S033.21.22.680 W056.29.45.964

circle(radius 30nm, S033.21.22.680 W056.29.45.964)

I had to do a major rework of all the code dealing with arcs. And beside other issues, this should now work again. Btw, the short version to draw a circle like this with my tool is S033.21.22.680 W056.29.45.964/30.

 

On 5/20/2022 at 6:14 AM, Chris Gutierrez said:

Dashed Lines would be very helpful to draw realistic Sectors.

At this time, there is no quick way to implement this functionality. But I'll work towards it while improving and fixing other parts of the code.

• I see some longer lines in our screenshot. Is this intentional? Or should a line with 3+ points continuously use the same distances between dashes?
• How about arcs? Are dashes needed there as well? If so, should the tick length be based on distance (as well) or angle?

 

On 5/27/2022 at 9:49 AM, Adrian Bjerke said:

I am getting multiple incorrect coordinate convertions now - here are two examples:

594700N 0080917E  gets translated as N059.46.60.000    E008.09.17.000
595349N 0090000E gets translated as N059.53.49.000    E900000000001.00.00.000

Sorry, the long ones were a newly "added" bug from my side while trying to mitigate the 60 seconds issue. Both examples now work as expected. And I have changed the handling for the 60s issue, should occur even less now, if not vanish at all. But who knows what other bugs I may have implemented. So always thankful for your reports right away.

Edited June 8, 2022 at 11:33 PM by Jonas Kuster

[Andreas Fuchs]

9 hours ago, Jonas Kuster said:

Looking at your examples, I assume the format is DD.dd (so just a short version of the Decimal format, with decimal places instead actual minute values (0-60)). Happy to support you there. So I've added this format to the selection. Maybe do some tests to verify if the outputs are as expected.

Great! I just left home for another working tour, will be back home next week to test it!

[Hongye Rudi Zhang]

9 hours ago, Jonas Kuster said:

Once again many thanks for using this tool and reporting the issues you have. Sorry it took a little longer to share the next update. But I had to rework different parts of the code to ensure compatibility with the latest script engine version of the web server. I used this opportunity to check the feedback I received after the previous update.

 

Looking at your examples, I assume the format is DD.dd (so just a short version of the Decimal format, with decimal places instead actual minute values (0-60)). Happy to support you there. So I've added this format to the selection. Maybe do some tests to verify if the outputs are as expected.

 

I had to do a major rework of all the code dealing with arcs. And beside other issues, this should now work again. Btw, the short version to draw a circle like this with my tool is S033.21.22.680 W056.29.45.964/30.

 

At this time, there is no quick way to implement this functionality. But I'll work towards it while improving and fixing other parts of the code.

• I see some longer lines in our screenshot. Is this intentional? Or should a line with 3+ points continuously use the same distances between dashes?
• How about arcs? Are dashes needed there as well? If so, should the tick length be based on distance (as well) or angle?

 

Sorry, the long ones were a newly "added" bug from my side while trying to mitigate the 60 seconds issue. Both examples now work as expected. And I have changed the handling for the 60s issue, should occur even less now, if not vanish at all. But who knows what other bugs I may have implemented. So always thankful for your reports right away.

Thanks!!!!!!!!!!

[Mubarak Ahmed]

@Jonas Kuster

Wondering if it's possible to add vatSys as an output option, it would be greatly appreciated. 

Quote

vatSys accepts coordinates in any valid ISO 6709 format.

Latitude and Longitude in Degrees:
    ±DD.DDDD±DDD.DDDD         (eg +12.345-098.765)
Latitude and Longitude in Degrees and Minutes:
    ±DDMM.MMMM±DDDMM.MMMM     (eg +1234.56-09854.321)
Latitude and Longitude in Degrees, Minutes and Seconds:
    ±DDMMSS.SSSS±DDDMMSS.SSSS (eg +123456.7-0985432.1)
Latitude, Longitude (in Degrees) and Altitude:
    ±DD.DDDD±DDD.DDDD±AAA.AAA         (eg +12.345-098.765+15.9)
Latitude, Longitude (in Degrees and Minutes) and Altitude:
    ±DDMM.MMMM±DDDMM.MMMM±AAA.AAA     (eg +1234.56-09854.321+15.9)
Latitude, Longitude (in Degrees, Minutes and Seconds) and Altitude:
    ±DDMMSS.SSSS±DDDMMSS.SSSS±AAA.AAA (eg +123456.7-0985432.1+15.9)

Edited June 9, 2022 at 09:56 PM by Mubarak Ahmed

[Jonas Kuster]

On 6/9/2022 at 11:55 PM, Mubarak Ahmed said:

@Jonas Kuster

Wondering if it's possible to add vatSys as an output option, it would be greatly appreciated. 

Sure. Are all 3 variants needed or is there a prefered one? Otherwise I would just go for the degrees only (best use of processing power and minimum processing time).

[Mubarak Ahmed]

17 minutes ago, Jonas Kuster said:

Sure. Are all 3 variants needed or is there a prefered one? Otherwise I would just go for the degrees only (best use of processing power and minimum processing time).

Thank you, 

Latitude and Longitude in Degrees:
    ±DD.DDDD±DDD.DDDD         (eg +12.345-098.765)

and 

Latitude, Longitude (in Degrees) and Altitude:
    ±DD.DDDD±DDD.DDDD±AAA.AAA         (eg +12.345-098.765+15.9)

Are the preferred format, also vatSys uses .XML formats it would be nice if the output can follow the structure below for example.  

Quote

 <Area>

-343000.000+1745000.000/

-350000.000+1745000.000/

-350000.000+1741500.000/

-343000.000+1741500.000/

<Area>

Thank you.

Edited June 11, 2022 at 04:13 PM by Mubarak Ahmed

[Jonas Kuster]

17 hours ago, Mubarak Ahmed said:

Thank you, 

Latitude and Longitude in Degrees:
    ±DD.DDDD±DDD.DDDD         (eg +12.345-098.765)

and 

Latitude, Longitude (in Degrees) and Altitude:
    ±DD.DDDD±DDD.DDDD±AAA.AAA         (eg +12.345-098.765+15.9)

Are the preferred format, also vatSys uses .XML formats it would be nice if the output can follow the structure below for example.  

Thank you.

I've added a new option for the output format. Obviously as my tool doesn't work with altitude values, I've skipped the the variant with altitude.

Regarding the xml output, the documentation of vatSys is not yet conclusive to me. While the description of Line and Infill element says, it's children are <Point> elements, your example as well as the default profiles of vatSys says different. And in fact, their content is just the sequence of coordinates without any further structure. Additionally, my tool does not specify if an output is to be used as a line or a polygon, hence it's not clear if the xml export should use Line or Infill elements. Maybe if we elaborate further on this and once the details are clear, I can implement another type of download format.

[Hongye Rudi Zhang]

Hi @Jonas Kustermaybe are you able to add a metric distance? Like XXXXkm

[Jonas Kuster]

Just now, Hongye Rudi Zhang said:

Hi @Jonas Kustermaybe are you able to add a metric distance? Like XXXXkm

Where exactly? If you enter AIP extracts, the unit is already considered.

[Hongye Rudi Zhang]

23 minutes ago, Jonas Kuster said:

Where exactly? If you enter AIP extracts, the unit is already considered.

Generally. In AIP is A circle with radius of 50km centered at ARP or

N213125 E1004357
a clockwised arc with radius of 50km centered at Xishuangbanna ARP
N214143 E1010834 National Boundaries N213125 E1004357

Edited June 12, 2022 at 10:41 AM by Hongye Rudi Zhang

[Jonas Kuster]

 

3 minutes ago, Hongye Rudi Zhang said:

Generally. In AIP is A circle with radius of 50km centered at ARP

As mentioned before, this is already possible. So as an example you can enter: Circle 50 km centered on N400300 E1161938. And it will draw a circle of 50 km around the provided coordinate.

Edited June 12, 2022 at 10:45 AM by Jonas Kuster

[Hongye Rudi Zhang]

9 minutes ago, Jonas Kuster said:

As mentioned before, this is already possible. So as an example you can enter: Circle 50 km centered on N400300 E1161938. And it will draw a circle of 50 km around the provided coordinate.

Edited 8 minutes ago by Jonas Kuster

Ah I see! Thanks!

[Matteo Massini]

Hello,

I'm getting wrong outputs when copying some sectors from AIP Italy. Here are two examples - the arcs should be drawn the other way around. I think it may have to do with the clockwise / anti-clockwise direction of the drawing but I'm not sure.

Thanks in advance, kind regards

[Jonas Kuster]

28 minutes ago, Matteo Massini said:

I'm getting wrong outputs when copying some sectors from AIP Italy. Here are two examples - the arcs should be drawn the other way around. I think it may have to do with the clockwise / anti-clockwise direction of the drawing but I'm not sure.

Unfortunately, textual representation in AIPs is very diverse. This makes it impossible to cover all formats, especially when multiple languages are combined. I suggest to transform the content into one of the proposed formats according the information provided in the empty entry field. If you wish a further follow-up, please share your input text in a reply to this thread. I cannot use screenshots for a detailed analysis.

Please also make sure to access the service via the published URL (see initial post of this thread). Other URLs might still work, but may provide limited/faulty functionality due to different configuration.

[Matteo Massini]

7 minutes ago, Jonas Kuster said:

Unfortunately, textual representation in AIPs is very diverse. This makes it impossible to cover all formats, especially when multiple languages are combined. I suggest to transform the content into one of the proposed formats according the information provided in the empty entry field. If you wish a further follow-up, please share your input text in a reply to this thread. I cannot use screenshots for a detailed analysis.

Please also make sure to access the service via the published URL (see initial post of this thread). Other URLs might still work, but may provide limited/faulty functionality due to different configuration.

I will try adapting the faulty sectors to the proposed formats, in the meantime, here's the two inputs from the screenshots 🙂
 

Linea congiungente i punti/line joining following points:
44°29'14''N 008°51'55''E
44°25'32''N 009°12'00''E
quindi arco di cerchio in senso orario raggio/then arc of
circle in clockwise direction radius 5.0 NM con centro su/
centred on:
44°20'40''N 009°10'20''E
fino a/till point
44°15'42''N 009°11'13''E
quindi linea congiungente i punti/
then line joining following points:
44°13'35''N 008°50'46''E
quindi arco di cerchio in senso orario raggio/then arc of
circle in clockwise direction radius 8.0 NM con centro su/
centred on:
44°21'30''N 008°49'00''E
fino a/till point
44°29'14''N 008°51'55''E

--------------------------------------------------
Linea congiungente i punti/line joining following points:
40°46'58''N 009°29'23''E
40°52'38''N 009°40'14''E
quindi arco di cerchio in senso antiorario raggio/then arc
of circle in anti-clockwise direction radius 5.0 NM con
centro su/centred on:
40°56'46''N 009°36'30''E
fino a/till point
41°00'53''N 009°32'45''E
quindi linea congiungente i punti/
then line joining following points:
40°55'12''N 009°21'53''E
quindi arco di cerchio in senso antiorario raggio/then arc
of circle in anti-clockwise direction radius 5.0 NM con
centro su/centred on:
40°51'05''N 009°25'38''E
fino a/till point
40°46'58''N 009°29'23''E

And, is it possible to draw arcs in an anti-clockwise manner? If so, how do I have to format the input? Anti-clockwise, counter-clockwise, with a space, a hyphen or all attached...

Thanks again for the superfast reply!

 

[Raul Ferraz]

Just for curiosity, did you try to swap the start/end coordinates, and see if it draws as you expect?

[Matteo Massini]

6 hours ago, Raul Ferraz said:

Just for curiosity, did you try to swap the start/end coordinates, and see if it draws as you expect?

I did, and it didn't work - but adapting the AIP Italy syntax to the proposed one made it work like a charm. This tool is literally the best gift I could ask for xD

I updated all of Italy's CTRs in less than an hour lmao

I guess I need no follow up unless it's something that Jonas actually wants to implement 😉 Thanks!

[Jonas Kuster]

8 hours ago, Matteo Massini said:

I will try adapting the faulty sectors to the proposed formats, in the meantime, here's the two inputs from the screenshots 🙂
 

Linea congiungente i punti/line joining following points:
44°29'14''N 008°51'55''E
44°25'32''N 009°12'00''E
quindi arco di cerchio in senso orario raggio/then arc of
circle in clockwise direction radius 5.0 NM con centro su/
centred on:
44°20'40''N 009°10'20''E
fino a/till point
44°15'42''N 009°11'13''E
quindi linea congiungente i punti/
then line joining following points:
44°13'35''N 008°50'46''E
quindi arco di cerchio in senso orario raggio/then arc of
circle in clockwise direction radius 8.0 NM con centro su/
centred on:
44°21'30''N 008°49'00''E
fino a/till point
44°29'14''N 008°51'55''E

--------------------------------------------------
Linea congiungente i punti/line joining following points:
40°46'58''N 009°29'23''E
40°52'38''N 009°40'14''E
quindi arco di cerchio in senso antiorario raggio/then arc
of circle in anti-clockwise direction radius 5.0 NM con
centro su/centred on:
40°56'46''N 009°36'30''E
fino a/till point
41°00'53''N 009°32'45''E
quindi linea congiungente i punti/
then line joining following points:
40°55'12''N 009°21'53''E
quindi arco di cerchio in senso antiorario raggio/then arc
of circle in anti-clockwise direction radius 5.0 NM con
centro su/centred on:
40°51'05''N 009°25'38''E
fino a/till point
40°46'58''N 009°29'23''E

And, is it possible to draw arcs in an anti-clockwise manner? If so, how do I have to format the input? Anti-clockwise, counter-clockwise, with a space, a hyphen or all attached...

Thanks again for the superfast reply!

I identified the issue being the part "arc of circle", because the algorithm expected only one of the words (arc/circle) to be used, followed by an optional definition of the direction of drawing. In addition, as I expected, the additional repetition originating from the two languages used, caused additional trouble.

Definitely anti-clockwise arcs are supported, by using "arc anti-clockwise" or "circle anti-clockwise". Additional syntax is supported as explained in the input field.

I've updated the algorithm, so that it should handle your input correctly without any changes. Thanks for your feedback.

[Teodor-Gabriel Petrica]

@Jonas Kuster
Hello, 

Would be possible to add a new tool to draw rectangles as in exemple below?

AN AREA BOUNDED BY 5NM EITHER SIDE OF A STRAIGHT LINE CONNECTING THE FLW POINT OF COORD: 435000N0231500E-462339N0230347E-434700N0234800E

The problem is that I cannot find the exact coordinates of the points located 5 NM left/right of the each point to create them manually.

Thank you,
 

[Jonas Kuster]

2 hours ago, Teodor-Gabriel Petrica said:

@Jonas Kuster
Hello, 

Would be possible to add a new tool to draw rectangles as in exemple below?

AN AREA BOUNDED BY 5NM EITHER SIDE OF A STRAIGHT LINE CONNECTING THE FLW POINT OF COORD: 435000N0231500E-462339N0230347E-434700N0234800E

The problem is that I cannot find the exact coordinates of the points located 5 NM left/right of the each point to create them manually.

Thank you,
 

I'm not sure if I understand your idea. Is it a kind of buffer? But only around a line?

Maybe some pictures help to also demonstrate the use case.

[Teodor-Gabriel Petrica]

On 12/13/2022 at 8:32 PM, Jonas Kuster said:

I'm not sure if I understand your idea. Is it a kind of buffer? But only around a line?

Maybe some pictures help to also demonstrate the use case.

Hello @Jonas Kuster,

The area defined by the description below is in the attach.

(yellow line)

AN AREA BOUNDED BY 5NM EITHER SIDE
OF A STRAIGHT LINE CONNECTING THE FLW POINT OF COORD:
435000N0231500E-462339N0230347E-434700N0234800E

Another example:

(blue line)

AN AREA BOUNDED BY 5NM EITHER SIDE
OF A STRAIGHT LINE CONNECTING THE FLW POINTS OF COORD:
442332N0274336E-443800N0274600E-454100N0271000E-463100N0265400E
454100N0271000E-443800N0274600E-442332N0274336E

[Jonas Kuster]

I'll consider your request for future developments.

[Matisse VanWezer]

When the sector file coordinates do not contain milliseconds, it causes issues with the conversions. 

Either hours become minutes or, seconds get nullified.

[Hongye Rudi Zhang]

Hi @Jonas Kuster, maybe possible add a select function to close polygon automatically? Like given coord A B C and export as A B C A

Edited January 28, 2023 at 10:49 PM by Hongye Rudi Zhang