Order cache by tile names #300
Conversation
This changes the cache directory layout to give its contents more semantic information. It creates sub-directories like `-48+013/` when cache images are saved. This allows to see which data has been downloaded for a region. It also enables manual pruning of a region if needed without additional tools to deal with the Slippy tile names. TODO: It does not move existing files into the new structure yet.
|
Or did you have the started work on the http://localhost:5000 map in mind for looking at the cache? |
|
This is a really interesting idea. I wonder if there is a way to do this but still allow and find the existing set of cache? Or maybe a tool to 'organize' these the first time? |
|
I pull that back and suggest leaving the cache layout as is for now. The current layout is even useful because it allow to directly serve a Slippy Map from it ;) I think the idea of having a map frontend showing the current state of AutoOrtho and its tiles could be a valuable addition and I think your idea with the web server in AutoOrtho and HTTP + WebSocket is the right way to do it. Just being able to look at it to understand how X-Plane accesses DDSs and AutoOrtho downloads and delivers would be awesome. Additionally it could have functions like manually downloading an area (for a given zoom level or zoom level range), pre-caching for a given route (.fms file) or deleting an area from cache. Finally I'll be able to use my Webdev skills ;) |
|
Yeah I think incorporating a showing available scenery to the map tool is a
good idea. Could be handy generally and for debugging purposes, and
probably not too hard to do. This is currently written in Flask and the JS
uses leaflet, which should have no trouble referencing a local endpoint for
maps.
I haven't looked too much into setting it up to switch between
openstreemaps and local stuff, but should be quite doable. I'm more of a
hack on the webdev side, so definitely happy to have you take a look.
The stats page also probably needs some work as well:
* Loses data on refresh
* Just collects data forever until you refresh
* Automatic layout is handy, but could be more efficient (maybe like a
grid?)
…-Matt
On Wed, Aug 30, 2023 at 12:43 PM Jonas Eberle ***@***.***> wrote:
I pull that back and suggest leaving the cache layout as is for now. The
current layout is even useful because it allow to directly serve a Slippy
Map from it ;)
I think the idea of having a map frontend showing the current state of
AutoOrtho and its tiles could be a valuable addition and I think your idea
with the web server in AutoOrtho and HTTP + WebSocket is the right way to
do it.
Just being able to look at it to understand how X-Plane accesses DDSs and
AutoOrtho downloads and delivers would be awesome.
Additionally it could have functions like manually downloading an area
(for a given zoom level or zoom level range), pre-caching for a given route
(.fms file) or deleting an area from cache.
Finally I'll be able to use my Webdev skills ;)
—
Reply to this email directly, view it on GitHub
<#300 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVEDLFM7A6VBLXBE22BWODXX5UUHANCNFSM6AAAAAA26DN6QE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This changes the cache directory layout to give its contents more semantic information.
It creates sub-directories like
-48+013/when cache images are saved.This allows to see which data has been downloaded for a region. It also enables manual pruning of a region if needed without additional tools to deal with the Slippy tile names.
TODO: It does not move existing files into the new structure yet.
So that's currently just a proposal for a more obvious cache structure.