Okay, I have been a LLOONNGG time user of Little Navmap. I actually think? I remember having setup LNM to display the correct VATSIM boundaries at one time, but then I either updated or moved LNM and when I reinstalled, everything was messed up. What I currently have IS:

• In the User Airspaces folder I have these files: Boundaries.geojson and atc_positions.json (this is an IVAO file)
• In Airspace Libraries: I ONLY have Online 'checked'
• In Tools-Map Online: I have "By airspace name vs. callsign" and "By airspace filename vs. callsign" both 'checked'.
• In Display Size for Online Airspaces/Centers: I have "ALL" options 'checked'.
• In LNM Toolbar on Airspaces Tab: I have 'Center, Departure, and Approach', selected to display on the map.

What I have showing on the LNM map is a fair amount of 'CORRECT' airspace boundaries in South America, Asia, Africa, and Most of Europe. In Europe, Centers are displaying correct but a few Approach boundaries are Not (they are Circles).

The United States is the WORST (where I fly most). Nothing is displaying Correctly. Everything (CTR, APP, DPT) are Circles. There are even a few CTR Circles in Canada.

I have tried many different selection options but just can't get everything to look correct. I know that it probably has to do with ATC location Naming issues. I can go into a file and rename boundaries if that's what it takes. I just need to know if I'm using the Correct boundary files and where to make changes if needed.

Thanks in Advance for ANY support with this issue.

Keith

Did you try the airspace boundaries for VATSIM mentioned in the user manual?

Quote

55.2.2. GEOJSON

Further formats for online airspaces are GEOJSON which can be downloaded for VATSIM boundaries at the VATSpy Data Project.
The extension is .geojson.

and

Quote

55.2.4. VATSIM JSON

You can load the files firboundaries.json and traconboundaries.json into the user airspace library of Little Navmap to get more real boundaries for VATSIM online centers instead of the generic circles.

But don't expect too much. There are still a lot of center names which do not match the boundary ids. I already match the centers to the boundaries using all name variations.

I'd rather need better data sources to fix this.

Ale

Thank You Alex for the Quick response. Yes, I have used both the .geojson and the .json files. It's Almost complete coverage except in the North America?. Just wish there was a 'One File' solution. Will keep messing with it.

Thank You Again and I have been a LNM fan from the beginning.

Keith 

I'll check again. Maybe I can find a way to connect the boundaries to the centers.

Alex