Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

vSTARS Temporary NavData updates


Rahul Parkar
 Share

Recommended Posts

Ross Carlson
Posted
Posted

We could probably work something out to use your data in the near term, though I will need to set up my own source for the long term. I have a need for the data for a non-VATSIM commercial product as well.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Rahul Parkar
Posted
Posted

That sounds good,

 

I'm using the data for work on a commercial product outside of VATSIM as well, hence why I have been able to offer AIRAC updates while you set up a system.

 

Cheers!

Rahul

Rahul Parkar

"On second thoughts Nappa, catch it, catch it with your teeth" -- Vegeta

Professional Nerd. (Professionally not professional)

Link to comment
Share on other sites

Ross Carlson
Posted
Posted

The source I've been using for AIRAC data is up to date, but not one I can count on being there forever, which is why I didn't build an autoupdater into version 1 of vSTARS. We can use your data for ad-hoc updates for now and I'll build the auto updater once I establish a reliable relationship for global data on an ongoing basis.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Rahul Parkar
Posted
Posted

That sounds reasonable to me,

 

Also, check your vSTARS inbox.

 

Cheers!

Rahul

Rahul Parkar

"On second thoughts Nappa, catch it, catch it with your teeth" -- Vegeta

Professional Nerd. (Professionally not professional)

Link to comment
Share on other sites

Gene Cao 1100087
Posted
Posted

Rahul, sent you a pm of the fixes that I personally found to be missing. If you are using Jeppesen data, then you should be good as all these fixes show up in Jeppesen.

gcsig.jpg

1100087.jpg

Link to comment
Share on other sites

Rahul Parkar
Posted
Posted

Yep,

 

I got it, I know where I went wrong and will be fixing that ASAP.

 

Cheers!

Rahul

Rahul Parkar

"On second thoughts Nappa, catch it, catch it with your teeth" -- Vegeta

Professional Nerd. (Professionally not professional)

Link to comment
Share on other sites

Tim Roden 987596
Posted
Posted

That file you put up there does not handle multiple waypoints correctly. Example CLARE intersection

CLARE|32760975|-96332136|K4

CLARE|37493889|127995000|RK

you have the RK location in the file not the K4. I need the K4 one. I found several waypoints like that. So far the VOR's are correct.

Tim Roden

ZAN C3

Link to comment
Share on other sites

Rahul Parkar
Posted
Posted

-Ruh Roh-

 

I'll make some more fixes to the parsing script which seemed to be doubling up instead of inputting multiple with the same name.

 

I was accidentally sorting them in the script by name and not a specific ID, causing any doubles to come up with the same Lat Long.

 

Problem Solved - I'll push the changes later today.

 

Updated!

 

Cheers!

Rahul

Rahul Parkar

"On second thoughts Nappa, catch it, catch it with your teeth" -- Vegeta

Professional Nerd. (Professionally not professional)

Link to comment
Share on other sites

Tim Roden 987596
Posted
Posted

Thanks. I thought I was going to have to write it myself.

Tim Roden

ZAN C3

Link to comment
Share on other sites

  • 2 weeks later...
Tim Roden 987596
Posted
Posted

Just noticed in that last file you updated with. there were 5 version of the LAW VOR. All the same location. Make sure that they are coming up with different locations.

Tim Roden

ZAN C3

Link to comment
Share on other sites

Rahul Parkar
Posted
Posted

Tim,

 

Are you sure about that, I just looked at the XML file and there are 2 VORs with the Identifier LAW, both in different positions.

 

AIRAC 1202 will be up once the updates shoot themselves down the chain.

 

Cheers!

Rahul

Rahul Parkar

"On second thoughts Nappa, catch it, catch it with your teeth" -- Vegeta

Professional Nerd. (Professionally not professional)

Link to comment
Share on other sites

Tim Roden 987596
Posted
Posted

Ok, I mispoke, the problem is really worse then that. Any VOR that has a Longitude greater then 100 is missing the minus sign. I was not finding LBB or PVW for my Lubbock approach facility. I looked at TNP out in California an it was a positive number on the Latitude as well.

Tim Roden

ZAN C3

Link to comment
Share on other sites

Rahul Parkar
Posted
Posted

Hmmm, That's weird, Let me take a look before I release 1202, I was certain I'd fixed that.

 

-Edit : No I didn't, but it is now fixed.-

 

Cheers!

Rahul

Rahul Parkar

"On second thoughts Nappa, catch it, catch it with your teeth" -- Vegeta

Professional Nerd. (Professionally not professional)

Link to comment
Share on other sites

Rahul Parkar
Posted
Posted

AIRAC 1202 Uploaded.

 

See original post for link.

 

Cheers!

Rahul

Rahul Parkar

"On second thoughts Nappa, catch it, catch it with your teeth" -- Vegeta

Professional Nerd. (Professionally not professional)

Link to comment
Share on other sites

  • 1 year later...
Rahul Parkar
Posted
Posted

I'll be updating this later tonight with the latest AIRAC cycle.

Rahul Parkar

"On second thoughts Nappa, catch it, catch it with your teeth" -- Vegeta

Professional Nerd. (Professionally not professional)

Link to comment
Share on other sites

  • 1 month later...
Jason Helkenberg 913355
Posted
Posted

Any chance at an update?

Jason Helkenberg

Link to comment
Share on other sites

  • 3 months later...
Casey Diers 981110
Posted
Posted
Any chance at an update?

 

If you are controlling in the US, try here.

Casey

ZDV_CI C1

MTN1474 / Mountain Air VP of Administration / Commercial Captain

Link to comment
Share on other sites

 Share