VRC Forum Index VRC Forums
Support, bug reports and general discussion related to the Virtual Radar Client for VATSIM.
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

NOTE: These forums are now read-only. For new posts, please use the appropriate VATSIM forum.
NEW EDDS (Stuttgart) Tower- and Groundsectorfile
Goto page Previous  1, 2, 3, 4, 5, 6, 7
 
Post new topic   Reply to topic    VRC Forum Index -> User Screenshots
View previous topic :: View next topic  
Author Message
MU_ZBW
Member


Joined: 01 Dec 2012
Posts: 11

PostPosted: Tue Feb 03, 2015 5:58 pm    Post subject: Reply with quote

Ross wrote:
You definitely want to make it a 2-pass thing like VRC ... there is no guarantee that the navaids, fixes, and airports will be first and there are likely many, many sector files out there that are like Andrew's.


Yep! I'm definitely going to do it that way. As I mentioned, I was sure that you did the same, probably for the same reasons.

I can definitely appreciate the work you did on parsing these files for VRC. I've noticed that your parser is quite forgiving on a lot of things. I just hope to match conditions with mine.

Jim
Back to top
View user's profile Send private message
Author Message
Andrew Wolcott
Member


Joined: 27 Mar 2010
Posts: 328

PostPosted: Fri Feb 06, 2015 12:25 am    Post subject: Reply with quote

MU_ZBW wrote:
Hey Andrew,

Another question, is there a particular reason why your headers do not go in the order of

#define
[INFO]
[AIRPORTS]
[VORS]
[NDBS]
[FIXES]

and then... AIRWAYS, ARTCC's, SIDs / STARs?

The reason I ask if that my file parser goes sequentially through the file. When it finds a named coordinate, it looks to see if it has already been added and then references those coordinates.

The challenge here is that your SCT file does something like:

[VOR]
[HIGH AIRWAYS]
[FIXES]

And in some of the high airway definitions, there are fixes, but my parser has not actually read those fixes. So it cannot deal with them and therefore would throw an error.

Just wondering what the logic was here, as its the first time I've seen that sequence of headers...

Furthermore:
- I could make the parsing of the file non-linear, it could basically scan for VORS, FIXES, NDBS and then move on to anything that will reference one of those. That must be how VRC is handling this otherwise your SCT file wouldn't work. It's probably the right way and won't add too much code... I'll do it.
- Is it super important that you keep the sequencing of the headers when the file read and then exported again?

Feel free to drop me a pm with your email and we can discuss that way.

Jim


Our most current file, AIRAC 1501, that is not publicly released yet, goes in this format:

Quote:
[INFO]
[VORS]
[NDB]
[FIXES]
[AIRPORT]
[RUNWAY]
[SID]
[STAR]
[LOW AIRWAY]
[HIGH AIRWAY]
[ARTCC]
[ARTCC HIGH]
[ARTCC LOW]
[GEO]
[LABELS]


...And for no particular reason.

None of our airway definitions use fixes. It is all lat/long. Reason being is that I used linestyles in cad to define airway dashes and gaps 10NMs long. Each airway is a separate layer, with line elements.

I did the same thing to display fixes using crosses and VORs using ovals. Makes it look more realistic.

It's not particularly important to maintain the same order of the headers. I'd rather myself keep them in line with the order written in the VRC documents.

AW a t minniecenter d o t o r g
Thats my email

Code:

J10 N041.06.07.337 W100.21.27.292 N041.03.52.199 W100.37.54.404
J10 N041.09.54.502 W099.53.46.694 N041.08.00.947 W100.07.36.991
J10 N041.13.41.448 W099.26.06.094 N041.11.48.002 W099.39.56.394
J10 N041.17.28.175 W098.58.25.496 N041.15.34.839 W099.12.15.793
J10 N041.21.36.063 W098.28.08.083 N041.19.21.457 W098.44.35.196
J10 N041.22.49.721 W097.59.35.779 N041.22.38.203 W098.14.11.065
J10 N041.23.11.926 W097.31.28.272 N041.23.00.823 W097.45.32.026
J10 N041.23.34.127 W097.03.20.765 N041.23.23.027 W097.17.24.518
J10 N041.23.56.329 W096.35.13.258 N041.23.45.230 W096.49.17.011
J10 N041.24.18.528 W096.07.05.750 N041.24.07.427 W096.21.09.504
J10 N041.24.40.725 W095.38.58.243 N041.24.29.625 W095.53.01.997
J10 N041.25.02.917 W095.10.50.736 N041.24.51.822 W095.24.54.490
J10 N041.25.25.110 W094.42.43.229 N041.25.14.016 W094.56.46.982
J10 N041.25.47.301 W094.14.35.722 N041.25.36.205 W094.28.39.475
J10 N041.26.09.903 W093.45.56.682 N041.25.58.395 W094.00.31.968
J10 N041.27.17.692 W093.12.57.978 N041.26.32.297 W093.31.53.468
J10 N041.28.25.057 W092.44.52.609 N041.27.51.378 W092.58.55.294
J10 N041.29.32.400 W092.16.47.237 N041.28.58.731 W092.30.49.921
J10 N041.30.51.420 W091.43.49.062 N041.30.06.067 W092.02.44.552

J100 N041.08.53.971 W102.16.29.669 N041.07.35.602 W102.34.24.128
J100 N041.10.56.447 W101.48.29.761 N041.09.55.217 W102.02.29.713
J100 N041.12.58.860 W101.20.29.854 N041.11.57.662 W101.34.29.809
J100 N041.14.36.098 W100.52.27.163 N041.13.51.839 W101.06.28.991
J100 N041.16.04.592 W100.24.23.508 N041.15.20.349 W100.38.25.336
J100 N041.17.33.055 W099.56.19.849 N041.16.48.829 W100.10.21.677
J100 N041.19.01.482 W099.28.16.194 N041.18.17.272 W099.42.18.022
J100 N041.20.29.875 W099.00.12.539 N041.19.45.683 W099.14.14.366
J100 N041.22.10.569 W098.28.13.850 N041.21.14.060 W098.46.10.708
J100 N041.24.51.282 W098.06.26.042 N041.23.37.228 W098.14.19.871
J100 N041.29.09.335 W097.38.53.765 N041.27.00.343 W097.52.39.904
J100 N041.33.27.101 W097.11.21.487 N041.31.18.254 W097.25.07.626
J100 N041.37.44.581 W096.43.49.210 N041.35.35.877 W096.57.35.348
J100 N041.42.01.779 W096.16.16.928 N041.39.53.214 W096.30.03.071
J100 N041.46.18.689 W095.48.44.651 N041.44.10.270 W096.02.30.790
J100 N041.50.32.360 W095.21.31.399 N041.48.27.037 W095.34.58.512
J100 N041.50.34.913 W095.21.12.269 N041.50.32.360 W095.21.31.399
J100 N041.54.16.483 W094.53.30.941 N041.52.25.725 W095.07.21.605
J100 N041.57.57.841 W094.25.49.613 N041.56.07.187 W094.39.40.277
J100 N042.01.38.984 W093.58.08.285 N041.59.48.439 W094.11.58.949
J100 N042.05.11.153 W093.31.32.869 N042.03.29.475 W093.44.17.621
J100 N042.05.19.074 W093.30.26.762 N042.05.11.153 W093.31.32.869
J100 N042.08.38.643 W093.02.40.578 N042.06.58.879 W093.16.33.672
J100 N042.11.58.034 W092.34.54.394 N042.10.18.360 W092.48.47.484
J100 N042.15.03.589 W092.07.05.383 N042.13.34.271 W092.21.00.598
J100 N042.18.02.116 W091.39.14.951 N042.16.32.870 W091.53.10.169
J100 N042.21.00.504 W091.11.24.522 N042.19.31.326 W091.25.19.736
J100 N042.23.20.754 W090.49.30.274 N042.22.29.644 W090.57.29.308
etc etc

;VORS
VORHI N049.53.41.285 W099.56.44.520 N049.53.42.111 W099.56.33.562
VORHI N049.53.42.111 W099.56.33.562 N049.53.44.634 W099.56.22.960
VORHI N049.53.44.634 W099.56.22.960 N049.53.48.551 W099.56.12.959
VORHI N049.53.48.551 W099.56.12.959 N049.53.53.989 W099.56.03.721
VORHI N049.53.53.989 W099.56.03.721 N049.54.00.765 W099.55.56.039
VORHI N049.54.00.765 W099.55.56.039 N049.54.08.493 W099.55.49.681
VORHI N049.54.08.493 W099.55.49.681 N049.54.16.970 W099.55.44.918
VORHI N049.54.16.970 W099.55.44.918 N049.54.26.244 W099.55.42.280
VORHI N049.54.26.244 W099.55.42.280 N049.54.35.544 W099.55.41.160
VORHI N049.54.35.544 W099.55.41.160 N049.54.45.074 W099.55.42.280
VORHI N049.54.45.074 W099.55.42.280 N049.54.54.141 W099.55.44.918
VORHI N049.54.54.141 W099.55.44.918 N049.55.02.822 W099.55.49.681
VORHI N049.55.02.822 W099.55.49.681 N049.55.10.548 W099.55.56.039
VORHI N049.55.10.548 W099.55.56.039 N049.55.17.320 W099.56.03.721
VORHI N049.55.17.320 W099.56.03.721 N049.55.22.600 W099.56.12.959
VORHI N049.55.22.600 W099.56.12.959 N049.55.26.670 W099.56.22.960
VORHI N049.55.26.670 W099.56.22.960 N049.55.29.064 W099.56.33.562
VORHI N049.55.29.064 W099.56.33.562 N049.55.30.017 W099.56.44.520
etc etc

;HIGH AIRWAY FIXES
FIXES_HI N045.07.49.154 W093.29.29.742 N045.09.48.190 W093.29.29.742
FIXES_HI N045.08.48.681 W093.28.05.354 N045.08.48.681 W093.30.54.130
FIXES_HI N045.11.30.560 W082.28.29.993 N045.13.29.468 W082.28.29.993
FIXES_HI N045.12.30.022 W082.27.05.605 N045.12.30.022 W082.29.54.380
FIXES_HI N045.01.56.062 W092.17.21.631 N045.03.55.302 W092.17.21.631
FIXES_HI N045.02.55.691 W092.15.57.244 N045.02.55.691 W092.18.46.019
FIXES_HI N044.44.19.390 W091.49.30.223 N044.46.19.241 W091.49.30.223
FIXES_HI N044.45.19.324 W091.48.05.836 N044.45.19.324 W091.50.54.611
FIXES_HI N044.24.40.431 W090.36.04.244 N044.26.40.959 W090.36.04.244
FIXES_HI N044.25.40.704 W090.34.39.857 N044.25.40.704 W090.37.28.632
FIXES_HI N046.06.00.882 W093.11.28.172 N046.07.57.876 W093.11.28.172
FIXES_HI N046.06.59.388 W093.10.03.785 N046.06.59.388 W093.12.52.560
etc etc

_________________
Andrew Wolcott
ZMP ARTCC
Back to top
View user's profile Send private message
Author Message
Andrew Wolcott
Member


Joined: 27 Mar 2010
Posts: 328

PostPosted: Fri Feb 06, 2015 12:28 am    Post subject: Reply with quote

Alexander Fath wrote:
A new version of sct_2_dxf is available, which is now able to convert an entire sectorfile into a dxf-file. The new version is v1.7.

The pic shows you on the left the original sctfile, and on the right the converted dxf. If you use autocad you need to set the background to black in order to get the appropriate colors. Autocad handles rgb values different based on background color, and the current hard coded conversion-table from rgb into aci is based on a black background.


Alexander,

Nice job, but again which projection are you converting to?

My latitudes are off from original lat/long, when converting sct2dxf.

You previous made a sct2dxf with no projection. Can you do this again?

With you current file, if I have a VOR at 049N, inside the DXF it becomes placed well north of 49N, somewhere around 6 degrees north of where it is in reality.
_________________
Andrew Wolcott
ZMP ARTCC


Last edited by Andrew Wolcott on Fri Feb 06, 2015 12:34 am; edited 1 time in total
Back to top
View user's profile Send private message
Author Message
Andrew Wolcott
Member


Joined: 27 Mar 2010
Posts: 328

PostPosted: Fri Feb 06, 2015 12:33 am    Post subject: Reply with quote

MU_ZBW wrote:

Great! Thanks. Your Sector files are some of the nicest I've seen. I'll definitely let you know when I have a test version ready.

BTW, as for the export, what is more useful for everyone? Google Earth or Rhino?

Jim


Thank you sir for the compliment Smile

So long as it is a CAD file, I can work with it. I use AutoCad and Microstation (Prefer Microstation.. it's great having a girlfriend who is an engineer BTW hehe)

However I can, using Global Mapper, import a KML/KMZ and convert to DXF.

Andrew
_________________
Andrew Wolcott
ZMP ARTCC
Back to top
View user's profile Send private message
Author Message
MU_ZBW
Member


Joined: 01 Dec 2012
Posts: 11

PostPosted: Sun Feb 08, 2015 6:40 pm    Post subject: Reply with quote

Hey Ross,

I'm starting to parse some SCT files with my WIP app. After running through a couple of larger SCT files, I came to the conclusion that my sector parsing rules were too harsh. For example I had functions like "isFrequency" which required a word from a Navaid to contain a period and besides that only numbers...

I've seen several failures to accept valid SCT objects as a result. Therefore, I've started to do what I should have done first. Trying to reverse engineer your parsing conditions to make sure mine match. This a bit stupid of me to do, so late in the game... Sad

Anyways, I've documented what I've tested so far. Would be great if you would comment on the outcomes of my first tests which are here:

https://bitbucket.org/jimspree1200/sector2rhino/src/fc9cf017fff790d492954981cfd03c0755d04ddc/VRC%20Parsing%20Rules.txt?at=master

At the moment, I would love to get your feedback on the [Coordinates] observations. Most of the other text I need to clean up. As I wrote above, I've come to the conclusion that VRC is generally just splitting each line into separate words and only strongly checking the coordinates. After coming to that conclusion, I tried to dig in on that alone.

The most exciting thing I *think* I found was the ability for VRC to parse more decimal places in the seconds decimal places of a coordinate. While it would clearly be a hack to use those extra digits, it could result to some more detailed diagrams.

All the best,

Jim
Back to top
View user's profile Send private message
Author Message
Ross
Developer


Joined: 07 Jul 2005
Posts: 6818
Location: Vermont

PostPosted: Sun Feb 08, 2015 6:52 pm    Post subject: Reply with quote

Hi Jim ... most of VRC's parser is based on regular expressions. Let me know if you'd like a copy of the code.
_________________
Ross Carlson - Developer

Back to top
View user's profile Send private message
Author Message
MU_ZBW
Member


Joined: 01 Dec 2012
Posts: 11

PostPosted: Mon Feb 09, 2015 3:28 am    Post subject: Reply with quote

Ross wrote:
Hi Jim ... most of VRC's parser is based on regular expressions. Let me know if you'd like a copy of the code.


Hi Ross,
Now that would be a huge help! I'll shoot you a private message with my email. For now I'll move away from the parser and use what I have until I hear back from you.
Jim
Back to top
View user's profile Send private message
Author Message
MU_ZBW
Member


Joined: 01 Dec 2012
Posts: 11

PostPosted: Sat Feb 28, 2015 5:02 pm    Post subject: Update Reply with quote

Hi Folks,
Just letting you know that I'm chugging along. Am currently able to parse a full sector file, along with saving it again. Working on the 3dm exporter now.. current status can be seen here:

bitbucket downloads

I'm up to SID/STAR parsing which means:
- Colour defines (see materials in screen shot)
- Airports
- Runways
- VORs
- NDBs
- Fixes
- ARTCC
- ARTCC Highs
- ARTCC Lows
- High Airways
- Low Airways
- SID
- STAR

are being written into the file. I'm all preserving all preceding notes (i.e. notes that come before a line) and inline notes (i.e. what follows Wink.

Everything is going into layers (see screen shot) for easily turn on and off parts of the sector. Under the hood I have two projection models possible (straight DMS decimal and mercator).

I'm now just mainly debugging. Rhino is complaining alot about errors that are due to how the sector files are created... for example in a start of a SID, often everyone uses two equal dummy coordinates, and when I try to create a line with the same start and end point, well that is not really a line. Just working through these corner cases.

As soon as I have something that I feel comfortable in sharing, I will do so! If you want a 'development build' just drop me a line and I'm also happy to just send you what I got.

Furthermore, it appears that Rhino also has a special point which you can use to define a world reference for KML exporting. So in theory it should be easy for me to add this point and then you can directly import and export KML's from Rhino.

Jim
Back to top
View user's profile Send private message
Author Message
MU_ZBW
Member


Joined: 01 Dec 2012
Posts: 11

PostPosted: Sun Mar 01, 2015 5:44 pm    Post subject: Reply with quote

Hi All,

I've just finished the first pass of the 3dm exporter. You can find the Windows/Mac version at:

https://bitbucket.org/jimspree1200/sector2rhino/downloads

The application is pretty ugly and totally lacking a UI and pretty error reporting. Here is how you can use it if you want to play around:

- Open app, a open dialog should appear automatically
- Select the .sct2 file you want to parse
- Wait while it parses the file, take note of any errors it finds, those should probably be fixed in your file
- Once the parsing is done, close the application. It will hang for a bit... It's writing files.
- On exit the app will write on the desktop two files:
- TempSector.sct2 - the export of the parsed sector to the .sct2 format
- TempSector.3dm - the rhino file

Let me know if you have any crashes or errors in your .sct2 or .3dm files, or any general feedback.

Jim
Back to top
View user's profile Send private message
Author Message
Alexander Fath
Member


Joined: 28 Jul 2007
Posts: 34

PostPosted: Sat Apr 18, 2015 1:26 pm    Post subject: Reply with quote

Andrew Wolcott wrote:


Alexander,

Nice job, but again which projection are you converting to?

My latitudes are off from original lat/long, when converting sct2dxf.

You previous made a sct2dxf with no projection. Can you do this again?

With you current file, if I have a VOR at 049N, inside the DXF it becomes placed well north of 49N, somewhere around 6 degrees north of where it is in reality.

Sorry Andrew for not replying, I just didn't notice that there had been new posts in this thread and I can't remember that I had anything in my email.


I'm using the Mercator projection.
So here's version v1.7 without projection: http://nav.vatsim-germany.org/files/library/public/sct_2_dxf_without_projection.exe
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    VRC Forum Index -> User Screenshots All times are GMT - 5 Hours
Goto page Previous  1, 2, 3, 4, 5, 6, 7
Page 7 of 7

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group