Ability to tile Terminal Area Charts with Sectional charts

[jamez70]

I was wondering if this was possible at zoom levels above 9 or some other values. I copied the tiles on top of the ones from Sectional and it works but they have a grey border because they aren't stitched together I assume

[N129BZ]

My chartserver app uses OpenLayers as the rendering engine and I added a menu that allows me to select charts by type. When I process the full US sectional chart and the Terminal Area charts, the app puts the TA charts as a overlay layer, so they seamlessly overlay the sectional. I think that is pretty much exactly what you are going for... Are you using leaflet for the map rendering?

[N129BZ]

Actually, that gives me an idea... maybe I can split out the individual TA charts into separate mbtiles db's

[jamez70]

I am using leaflet. No way will I convert over to OpenLayers at this point it would be a total struggle with all the code I've written for Leaflet

[N129BZ]

Are you using mbtiles databases for leaflet, or filesystem?

[jamez70]

I use the filesystem. The results were AMAZING. However, I think you can just go to 12 on the max zoom. 13 is just too much and it took 13 hours to process just the sectionals.

[N129BZ]

Here's a Chicago terminal chart overlaying the US Sectional chart. If this can be done in OL, there's got to be some way to do it in Leaflet...

[N129BZ]

Terminal over sectional, showing Chicago, detroit, Cleveland, and Pittsburgh

[jamez70]

I figured it out

[jamez70]

Milwaukee has a TAC, but its not like the others. I'm not sure how they extract that one.
Here is a screenshot from vfrmap.com

[jamez70]

Its on the lower left side of the Chicago sectional. Come to think of it I think Jacksonville has a similar situation

[N129BZ]

Picking out an inset off the main area chart is probably a little too challenging at the moment... also FYI, I'm implementing the US VFR Planning Chart as # 53 in the list of individual charts.

[N129BZ]

On second thought, I could make a list of any area charts that have an inset feature on the side, and implement a new process that clips off everything but the inset... ??? I just re-remembered how to create clipshapes using QGis...

[jamez70]

I was digging around wondering how they did it. Someone must have some clipshapes already made for it

[N129BZ]

They're pretty easy to create in QGis - once you get the process down... let me know what you want and I'll make them

[N129BZ]

BTW - After checking found that the Jacsonville chart has 2 insets... I think it will work to process all insets as overlays - they're properly geo-referenced in the tiff file, so I should be able to create shape files just for the insets and process the main chart with the inset shape, then when warped and tiled it should come out just fine. I've added a new processing list in settings.json named "insetchartlist" with all of the insets:

"insetchartlist": [
        [9, "Milwaukee"],
        [24, "Jacksonville"],
        [24, "Tampa"],
        [32, "Los_Angeles"],
        [48, "Indianapolis"],
        [49, "Lake_of_the_Woods"],
        [50, "Norfolk"]
    ],

I'll let you know when I've tested it.
Brian

[N129BZ]

After too much time looking into these insets - I find they are not geo-referenced to the main chart, plus their scaling is 2X the scale of the main chart. I think the ability to zoom on the main chart kinda makes an inset a moot point, plus I have no idea how to properly geo-reference it. When I made a shape file for the Indianapolis inset on the St Louis chart and clipped it, produced a Indianapolis.db file, it comes out on the OSM map right where it was physically on the St Louis chart. Maybe some future release, but right now I think the proper way to handle this would be a simple PNG or WEBP of the inset and when clicking on the major airport in the main map, have the inset image pop up.

Since this issue was about overlaying terminal charts and that is working, I'm closing this issue.