[Tilesathome] Tileset as one file v2

[Matthias Julius]

spaetz <osm at sspaeth.de> writes:

> The userid is a bit special, in that it is the only value that can't
> (and shouldn't) be set by the client as it only applies within the
> context of a single server installation. So treating it a bit
> separately is ok IMHO.
>
> Now, it still requires the server to both modify at the beginning and
> the end of the file in v2. Ideally, the server could leave the
> metadata section alone and have just the user filled in data tere.

I had added the userid to the meta-data because I felt it belongs
there and I left it in the header to make transition easier.  I should
add to the wiki page that only one is required.

In any case adding the userid to the meta data is easy, just append
"\nUser-Id: <id>" to the file.

>> mtime might get lost when copying a file across different systems or
>> media like HTTP.  I think it is better if all relevant information
>> is contained in the file.  This is worth the 25 bytes it will take,
>> IMHO.
>
> (You mean the 183 MB per layer :-) (if all 16m tileset files were
> stored)

which only takes 10 of the more complex tiles to use up.  When the
tile server operates at 99.99 % disk capacity where those 183 MB
matter we have other problems.

> Can you tell me how I can use a current client for testing to see if
> uploading tileset files work? Is there a config option or a magc
> switch? Would be great to be able to test this with a live client.

The client knows a CreateTileset option to produce them.  But it won't
attempt to upload them.  Now, that the _unstable client has been
migrated I will add the uploading part.  Just give me a day or two.

Matthias