On Tue, Sep 16, 2008 at 10:47:21PM +0200, Florian Lohoff wrote: > The first question needs to be "What are you trying to solve?". Yes it > might be nice to have that information but in the end it should be there > for a reason.
For example this is the reason why I currently don't include x,y,base z, and layer info in the tileset file. It's clear from the location the files are stored. And as they are not thought for being transferred a lot, I feel it's fine as it is... > I can see the purpose of finding broken clients/apis but i guess this > information is obsolete after 14 days (3 hours at the commit rate in the > client svn). > So you'd want client version, and data source (API, ROMA, XAPI) and > better put the url in there or some generator name from the osm file as > i'd guess we'll see ROMAs grow like mushrooms. A short unique generator name might make sense. Perhaps better than the URL. > For finding clients a metadata xml file uploaded parallel to the tileset > and deleted after some time would be sufficient. No need to keep that > data forever ... I'd agree with it, but whoever implements, decides. That's how open source works :-) spaetz _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
