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.

2017 VATSpy Update Suggestion Thread


Christoph Reule 1379750
 Share

Recommended Posts

  • Replies 149
  • Created
  • Last Reply

Top Posters In This Topic

  • Christoph Reule 1379750

    67

  • Andreas Fuchs

    9

  • Javier Escandarani

    6

  • Sachin Gnath

    5

Top Posters In This Topic

  • Christoph Reule 1379750

    Christoph Reule 1379750 67 posts

  • Andreas Fuchs

    Andreas Fuchs 9 posts

  • Javier Escandarani

    Javier Escandarani 6 posts

  • Sachin Gnath

    Sachin Gnath 5 posts

Popular Days

  • May 4 2017

    6 posts

  • Feb 12 2017

    6 posts

  • Feb 9 2017

    6 posts

  • Apr 13 2017

    5 posts

Ross Carlson
Posted
Posted

Right, it only detects the prefix up to the first underscore.

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted
Right, it only detects the prefix up to the first underscore.

 

What about callsigns like "ENBD-S" (without underscore)? Would this be correctly detected?

Link to comment
Share on other sites

Ross Carlson
Posted
Posted

Yes, it only looks for underscores as the delimiter.

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted
Yes, it only looks for underscores as the delimiter.

 

Thanks for this clarification, Ross!

 

So, coming back to the issue with the German sub-sectors, I currently see two possible solutions:

  • either alter the callsigns to exclude underscores (e. g. EDMM-N instead of EDMM_N) or
  • define an alias (aka alternate) callsign (e. g. MM-N, MM-NORTH) that could be [Mod - Happy Thoughts]ociated with a corresponding FIR shape.

 

The second possibility will only work if VATTastic does allow to link FIR shape designators to an alias, though.

Link to comment
Share on other sites

Andreas Fuchs
Posted
Posted

Not sure if this is worth the effort, as other programs detect the sub-sectors correctly. Ross, is there any chance that you would fiddle with the code and get this change so it would accept the sub-sectorizations with underscores? Germany is by far not the only vACC that uses this kind of coding.

Link to comment
Share on other sites

Ross Carlson
Posted
Posted

Yeah, I could do that ... I'm planning an update to VATSpy to have the data files auto-download from the server when changes are made. I'll make this change then. No idea when I'll find the time to work on it, though.

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

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted

In the meanwhile only corrected shapes for EDGG, EDMM and EDWW (without sub-sectors) will be provided.

 

Available in the next dataset update.

Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted

Just to give you a summary of all changes already done for the next release:

  • list of airports updated: Ireland, Norway, Slovenia, Sweden
  • sectors updated: Germany (partially, see posts above), India, Norway, Russia, Sweden
  • added Rhein Upper FIR (EDUU)

 

Awaiting your requests and suggestions!

Link to comment
Share on other sites

Brodie Murdoch
Posted
Posted

Hi,

 

Just wanting to confirm with you Chris that the updates that you are doing to VATSPY are the updates that are provided by each VATSIM Division, vACC, ARTCC. Because not every VATSIM Division out there applies to real-world meaning that they dont simulated nor have the capability on following real-world procedures for Example: Creating a UIR in VATSPY that is the same in realworld but doesnt exist in VATSIM. There's no point + UIR's generally are displayed within the VATSIM GRP i.e oceanic sectors or Over-land FSS which are VATSIM Approved from VATGOV's etc. Cause the last thing that we need is for some one to jump on these un-approved positions and get removed from them.

 

Also just remember that FIR's are not ACC's (Area Control Centres)they serve a different purpose.

 

Also one last quick question in your recent post

 

sectors updated: Germany (partially, see posts above), India, Norway, Russia, Sweden

 

Why have you updated the sectors in India as they have been already updated from the VATSIM West Asia Staff a while back in 2016 and nothing has change since the that Division

 

Cheers

BRODIE MURDOCH
Deputy Division Director | VATSIM West Asia Division     
ATC & FIR Manager Specialist Project | Asia Pacific Region   
Network Supervisor Team 4 | VATSIM Network
   
##
 http://vatwa.net/
 
##
 https://www.vat-apac.com/   
03fpOTE_d.webp?maxwidth=1520&fidelity=grand
Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted
Hi,

Just wanting to confirm with you Chris that the updates that you are doing to VATSPY are the updates that are provided by each VATSIM Division, vACC, ARTCC.

 

Of course.

 

Why have you updated the sectors in India as they have been already updated from the VATSIM West Asia Staff a while back in 2016 and nothing has change since the that Division

 

I didn't remove or add any sector for India, these are more "optical" changes (they better fit to surrounding sectors of other countries without "gaps").

 

Cheers

Link to comment
Share on other sites

Brodie Murdoch
Posted
Posted

Hi,

 

Yes but the gaps are there for a reason from VATWA to display the TMA Boundary lines as seen from different picutres from the VATWA vACC's

 

Example of 1

 

c9398d4ea26851575b882113604a8002_375x374.jpg

 

VCCF & VOMF FIR Boundary

 

"As shown in the left picture, unnamed triangle should be disregarded.

Orange line is the correct VCCF TMA boundary.

Approximate location of the line is shown in the right picture.

From north VOMF FIR, left of DABAR - ATETA - IDIBI - DEMON - BIKOK - BASUR - N07.00 E077.00 - Vertically south to VRMF FIR."

 

Of course thats the closes thing your gonna get as we all know the geographic corrdinates on coastlines within VATSPY are outdated which they optimized it to fit within VATSPY.

 

So i think chris you may want to double check that the work you are doing for VATSPY are based off whats provide by each Division by actually reading over there procedures, information etc provide on there Website

 

Cheers

BRODIE MURDOCH
Deputy Division Director | VATSIM West Asia Division     
ATC & FIR Manager Specialist Project | Asia Pacific Region   
Network Supervisor Team 4 | VATSIM Network
   
##
 http://vatwa.net/
 
##
 https://www.vat-apac.com/   
03fpOTE_d.webp?maxwidth=1520&fidelity=grand
Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted

Brodie,

 

since I'm not doing this task officially, I encourage you and everyone else to bring in every expertise to help make VATSpy even better...

 

PS: regarding your example given above... the shapes on the screenshot below are based on the data update for India done in 2016, and I see some discrepancy, though...

 

o3i9dqvr.jpg

 

Cheers

Link to comment
Share on other sites

Shrikar Galgali
Posted
Posted

Hello ,

 

The Entire VAT-Spy Update for India vACC has been done by me.

In the above picture , there is absolutely no discrepancy

 

They are two different CTRs : VOMF_CTR and VOTV_CTR.

I agree , they are not 100% accurate but they are definitely 90% accurate which is acceptable by us.

 

51186b8b72.jpg

 

Regards

Shrikar Galgali

Proud Member of VATWA Division

India vACC

26.png

Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted
Hello ,

The Entire VAT-Spy Update for India vACC has been done by me.

In the above picture , there is absolutely no discrepancy

 

They are two different CTRs : VOMF_CTR and VOTV_CTR.

I agree , they are not 100% accurate but they are definitely 90% accurate which is acceptable by us.

 

Hi Shrikar,

 

thanks for the confirmation by your side about VOMF_CTR and VOTV_CTR!

 

Regards

Link to comment
Share on other sites

Gia Pham
Posted
Posted

Hello, ZDC has some change soming up and it would be nice that it can be include in the next VATSPY update.

 

It should be in the Vatspy.dat

 

KDCA|Potomac Combined|38.852083|-77.037722|PCT|KZDC|0

 

Thank you all

Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted
Hello, ZDC has some change soming up and it would be nice that it can be include in the next VATSPY update.

 

It should be in the Vatspy.dat

 

KDCA|Potomac Combined|38.852083|-77.037722|PCT|KZDC|0

 

Thank you all

 

Done!

Link to comment
Share on other sites

Dace Nicmane
Posted
Posted

It would be nice if it was possible to filter/sort the flights by aircraft type.

KntU2Cw.jpg
Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted
It would be nice if it was possible to filter/sort the flights by aircraft type.

 

Hi Dace,

 

unfortunately I can't give you technical support on VATSpy itself. May I suggest to either contact Ross Carlson (developer of VATSpy) directly here in this forum or alternatively here: http://www1.metacraft.com/VRC/forums/viewforum.php?f=10?

 

Thanks!

Link to comment
Share on other sites

Henry Weber
Posted
Posted

I've updated the names of the airports in greenland and I would appreciate it if you could include them in the next update

BGAA|Aasiaat|68.721732|-52.786435||BGGL|0

BGBW|Narsarsuaq|61.161111|-45.427778||BGGL|0

BGCO|Nerlerit Inaat|70.741518|-22.648788||BGGL|0

BGGH|Nuuk|64.190833|-51.678056||BGGL|0

BGJN|Ilulissat|69.233060|-51.066390||BGGL|0

BGKK|Kulusuk|65.583060|-37.149720||BGGL|0

BGMQ|Maniitsoq|65.411331|-52.933198||BGGL|0

BGPT|Paamiut|62.012167|-49.670044||BGGL|0

BGSF|Kangerlussuaq|67.016944|-50.689167||BGGL|0

BGSS|Sisimiut|66.951655|-53.722719||BGGL|0

BGTL|Thule A.B.|76.530867|-68.705083||BGGL|0

BGUK|Upernavik|72.789652|-56.129264||BGGL|0

BGUQ|Qaarsut|70.733598|-52.693618||BGGL|0

 

Also the sectors in Iceland & Greenland are outdated. The new ones look like this:

http://vatsim-scandinavia.org/wp-content/uploads/2012/12/Sector-Map1.jpg

Essentially there are now 4 sectors: North, east, south and west.

For more information about this I would suggest to contact Wygene Chong Vatsim ID:1089621

20.png
Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted
I've updated the names of the airports in greenland and I would appreciate it if you could include them in the next update
BGAA|Aasiaat|68.721732|-52.786435||BGGL|0

BGBW|Narsarsuaq|61.161111|-45.427778||BGGL|0

BGCO|Nerlerit Inaat|70.741518|-22.648788||BGGL|0

BGGH|Nuuk|64.190833|-51.678056||BGGL|0

BGJN|Ilulissat|69.233060|-51.066390||BGGL|0

BGKK|Kulusuk|65.583060|-37.149720||BGGL|0

BGMQ|Maniitsoq|65.411331|-52.933198||BGGL|0

BGPT|Paamiut|62.012167|-49.670044||BGGL|0

BGSF|Kangerlussuaq|67.016944|-50.689167||BGGL|0

BGSS|Sisimiut|66.951655|-53.722719||BGGL|0

BGTL|Thule A.B.|76.530867|-68.705083||BGGL|0

BGUK|Upernavik|72.789652|-56.129264||BGGL|0

BGUQ|Qaarsut|70.733598|-52.693618||BGGL|0

 

Hi Henry,

 

these airports are already up-to-date in the current dataset (see here).

 

Also the sectors in Iceland & Greenland are outdated. The new ones look like this:

http://vatsim-scandinavia.org/wp-content/uploads/2012/12/Sector-Map1.jpg

Essentially there are now 4 sectors: North, east, south and west.

For more information about this I would suggest to contact Wygene Chong Vatsim ID:1089621

 

I contacted Wygene about this. Will let you know when I receive more information.

Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted

Also the sectors in Iceland & Greenland are outdated. The new ones look like this:

http://vatsim-scandinavia.org/wp-content/uploads/2012/12/Sector-Map1.jpg

Essentially there are now 4 sectors: North, east, south and west.

 

Request processed and completed. Will be included in the next dataset update.

Link to comment
Share on other sites

Christoph Reule 1379750
Posted
Posted
Good evening

 

I have the latest update installed and have observed a few airport errors.

 

EPMO is not displayed. Its coordinates are 52°27′04″N 020°39′06″E.

LCEN is not displayed. Its coordinates are 35°09′35″N 33°30′00″E.

LCNC is still displayed. It has been a disused airport since 1974.

LECH is incorrectly positioned. Its correct coordinates are 40°12′35″N 0°04′11″E.

LTCB is not displayed. Its coordinates are 40°58′00″N 38°04′48″E.

LTDA is not displayed. Its coordinates are 36°21′46″N 36°16′56″E.

 

 

Cheers

Ryan

 

Done!

 

PS: please supply airport names for any airport data requests, makes things easier...

Link to comment
Share on other sites

Henry Weber
Posted
Posted

Also the sectors in Iceland & Greenland are outdated. The new ones look like this:

http://vatsim-scandinavia.org/wp-content/uploads/2012/12/Sector-Map1.jpg

Essentially there are now 4 sectors: North, east, south and west.

 

Request processed and completed. Will be included in the next dataset update.

Thank you so much!

20.png
Link to comment
Share on other sites

 Share