A place to indicate your skills and willingness to assist, as well as a listing of all the latest vacancies to assist with technical development
By Ross Carlson 887155
#524416 I don't think it would be more realistic to use a hard coded value ... airspace just varies too much. Granted, there is less variance with approach and tower airspace than there is with center, but center airspaces are arguably the most important to get right here, because they cover so much of the planet compared to the underlying facilities.

I think it would be worth using the data we have for airspace boundaries, even if it changes from time to time ... it doesn't change all that often, and it would be far more accurate than just using a fixed-size circle for each center facility.
By Neil Farrington 1104841
#524418 Agreed on all counts... we're literally saying the same thing.

I wasn't at all suggesting it would be a solution people would use, since it would be so inaccurate - it's a stepping stone to the end goal, for a small project, for a new programmer.
By Grant Meder 1297722
#524479 I'd like to ask a quick question this JSON file.

If I'm looking at the Moncton FIR, I first see the
Code: Select all{"icao":"CZQM","isOceanic":"0","isExtension":"1","points":[["48.500000","-62.000000"],["44.446667","-56.051667"]]}

So I was thinking "Wow, this FIR only has 2 points?" Then I see right after that line of code this:

Code: Select all{"icao":"CZQM","isOceanic":"0","isExtension":"0","points":[["49.300000","-61.000000"],["49.533333","-61.000000"],["51.000000","-58.000000"],["51.283333","-57.000000"],["51.735000","-57.000000"],["52.196389","-58.142778"],["51.633333","-59.500000"],["51.333333","-59.500000"],["50.833333","-60.000000"],["50.833333","-62.083333"],["51.416667","-64.000000"],["53.700000","-64.916667"],["54.416667","-65.333333"],["55.083333","-65.083333"],["55.355556","-64.000000"],["57.550000","-64.000000"],["58.471111","-60.351111"],["57.000000","-59.000000"],["53.000000","-54.000000"],["49.000000","-51.000000"],["45.000000","-51.000000"],["45.000000","-53.000000"],["44.446667","-56.051667"],["43.600000","-60.000000"],["41.866667","-67.000000"],["44.933333","-67.000000"],["45.625000","-67.775000"],["45.783333","-67.806944"],["45.825000","-67.583333"],["46.143056","-67.216667"],["46.200000","-67.216667"],["46.536111","-67.300000"],["46.572500","-67.249167"],["46.611944","-67.203333"],["46.645278","-67.170278"],["46.698333","-67.127500"],["46.744444","-67.097778"],["46.792222","-67.074167"],["46.841389","-67.056667"],["46.891389","-67.045556"],["46.941667","-67.040556"],["46.992222","-67.042222"],["47.042500","-67.050278"],["47.091944","-67.064722"],["47.140556","-67.085278"],["47.187500","-67.112222"],["47.232778","-67.145000"],["47.275833","-67.183611"],["47.316667","-67.227778"],["47.354444","-67.276944"],["47.389444","-67.330556"],["47.420833","-67.388889"],["47.448611","-67.450833"],["47.472778","-67.516389"],["47.492778","-67.584722"],["47.508611","-67.655556"],["47.520278","-67.728056"],["47.527500","-67.801944"],["47.530278","-67.876389"],["47.528611","-67.950833"],["47.522778","-68.025000"],["47.733333","-67.950000"],["47.883442","-66.896275"],["47.999992","-65.940733"],["47.848333","-64.622222"],["48.500000","-62.000000"]]},

So...am I missing something? Why does it have 2 lines of code, and why does one line have only 2 points and the other have a lot more?
By Kieran Samuel Cross 1298134
Grant Meder 1297722 wrote:-snip-

As I said a little further up, I took the sectors from the VAT-Spy file, and really quickly made a piece of code to decode the .dat file and to put it into a JSON format.

Its probable that I messed it up when doing it, which explains those issues. You might be better off writing your own conversion script for this.

Remember, using this file is on your own head - it was taken without permission of Ross, and only uploaded to GitHub by mistake (and since it's Git, there's little point in removing the file now).
By Kieran Samuel Cross 1298134
Grant Meder 1297722 wrote:So do you think that if I combine all of those points it would form the FIR?

It could well do, but it might not at the same time. You might want to try draw with and without, and see what the difference is.
By Aidan Stevens 1346088
#524507 If I remember correctly, you want the second set of coordinates. I’m not quite sure what the first set are, but when drawing just the second set on a map, it shows the proper sector. This is all from memory, so I may be wrong.
By Pedro Rodrigues 1377186
#533318 Extending on the suggestions of others, here is an example you can try out using the Vatsim REST API.

EDGG is the only center position at the moment (in Europe), and he is reporting a center position of lng:8.54312 lat:50.02642, lets assume he is on maximum range (600 miles, or 966 Km).

One could leverage the REST API to query for pilots around his position in a radius of 966 Km, like so:

Code: Select allhttp://vatsim-api.herokuapp.com/controllers?where={"callsign": "EDGG_E_CTR"}

Should give you the center location for EDGG.

Code: Select allhttp://vatsim-api.herokuapp.com/pilots?where={"location": "$near": {"$geometry": {"type": "Point", "coordinates": [8.54312,50.02642]}, "$maxDistance": 966000}}}

Converting the Km to meters, we can query pilots in his scope.
I may or may not be working on adding alerts for such queries.