I'd like any of the developers to read this draft about a common shared
cache that I'd like to implement in JOSM:
https://josm.openstreetmap.de/wiki/SharedTileCache
Generally this seems sensible. A few comments:
maybe the min free space in the fs, or both.
Min free space in the FS is a good idea.
There's an OSM, but really this isn't about OSM. It's about TMS.
Bing isn't about OSM (even though they graciously let us edit based on
it).
So I'd use TMS rather than osm/tiles.
Agreed.
There are various other free/Open/OpenData sources that offer Tiles eg:
BlueMarble,
CalTopo,
OS NPE,
Other various historical maps.
I don't understand the limit namespace 'squatting' request by the Marble
developer.
Could the reasoning be explained somewhere?
Instead I would list the specific short names used so that applications can
*create* and use the cache even without adhering to the cache.ini specification.
For the tile servers currently offered on the main osm.org website I would name
them:
MapQuest_Open
OSM_Cycle
OSM_Humanitarian
OSM_Mapnik
OSM_Transport
Of course one could use spaces instead of underscores to make things
interesting...
I think zoom/x/y is good. I really don't like the way viking does it
now, which I can never easily remember.
I totally agree!
A conversion program to read an old cache and move it to the new format
would be nice. But for me not a big deal
Note there is cache conversion tool (in python) in the source repository tools
directory - 'viking-cache-mbtile.py'
ATM it only converts a Viking cache into an MBTiles file.
Then you can use the mbutil script (https://github.com/mapbox/mbutil) to
convert the MBTiles files into a TMS layout.
I suspect I will expand this tool to convert directly from a Viking cache
layout to a TMS layout.
Renaming it 'viking-cache.py' might be an idea...
I further notice these 'tools' weren't distributed in build output, which I
fixed in the last couple of days.
A big issue is caching lifetime, in terms of when to recheck the server
With the age=X
It might be an idea to the have an absolute minimum tile age value - such as at
least 24 hours, so any lower values in the age should be ignored and 24 hours
would be used (86400 seconds).
--
___
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
