CFS data

[twhitehead]

@lordfolken a couple of months ago, you mentioned doing a pulls request to include data from my CFS extraction code.

The patch I was waiting/working on is in XCSoar, and I have beat my CFS extraction code to the point where I consider the data nearly read for release. Here are some screen shots. The biggest thing I am likely to change at this point is dropping some of the CFS fields that aren't relevant to gliding (e.g., customs, services, etc.) to help it all fits on one screen.

I have poked though this repo a bit, and now I am following up with you to get an idea of the steps. Note that

• the data only covers the Ontario province in Canada as that is the only one I buy the CFS for (the code should work fine for the other provinces too, but I haven't actually tried it)

I also have a custom map file for SW Ontario (haven't pushed the latest to that repo yet) based on Provincial and Federal data sources, and custom waypoints too. Here is a screenshot of the custom maps with last year's data.

The map has more verticies than it needs, and the way XCSoar drops points to simplify the map when zooming out creates some fully-zoomed-out artifacts (presumably this affects the default one too?). I believe I have come up with an algorithm to recompute the verticies to simplify it and make it robust to dropping points, but I haven't had time to implement it yet.

Please note that I may not necessarily respond right away, but I do continuing working on these things as I use them.

[lordfolken]

I made this a discussion, because i think you touch on one or two different subjects. We can then open issues for those.

We can include the output of your code in xcsoar-data-content. That way it would appear in the file manager on xcsoar, so it could be downloaded automatically. The best and most losley coupled integration, would be that you host the output on your github page, that way we can reference it via remote/.
The French airspace is configured here in a similar fashion: https://github.com/XCSoar/xcsoar-data-content/blob/master/data/remote/airspace/country/FR-ASP-National-PlaneurNet.txt.json
They have some github actions for building and publishing to the github-io page. https://github.com/planeur-net/airspace/tree/main/.github/workflows

The map file:
I want data to be generatable. So i don't want to upload or add random xcm files i get from somewhere.
To facilitate this, i wrote a topology extractor that uses osm data. This currently makes a lot nicer maps than what is currently available from the downloads. I also took care to reduce the points and make it manageable for xcsoar.
https://github.com/XCSoar/xcsoar-mapgen-topology

As to the artefacts: i know they are there.. but haven't yet had the time to bughunt.