-
Notifications
You must be signed in to change notification settings - Fork 290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
produce TileJSON #79
Comments
Sounds like a fun idea. Even at the most basic level, producing a basic tilejson automatically would be useful, even without the additional information. with almost no information would still be useful. {
"tilejson": "2.0.0",
"tiles": [ "{{ base domain }}/{{ layername }}/{z}/{x}/{y}.png" ]
} Maybe even just having a setting dict object that is served up as a tilejson, with some sensible default values. I'll try to do this next week, I have a bunch of hacking around memcached that I need to do as well. |
Do you still intend to implement this? I guess it would be a nice way to add metadata to the tiles. |
@prebm I haven't worked on this in a long time, so realistically speaking, it's unlikely I'll get into this again in the near term. |
@idan Ok, thanks. As I can see there is no other way to add metadata to the tiles. Is that right? |
Is there any movement on this? |
An idea is to support providing TileJSON through the TileStache REST API for layers which have been configured in your TileStache config file.
For example if you specify bounds of a layer in your TileStache config file, then the TileJSON for that layer would include those bounds.
The TileJSON would be served up at somewhere like tilestache.cgi/layer-name.jsonp
If TileStache were to support this it could add extra fields to the config file like description, attribution, layer name of UTF grid, etc.
It would also need an extra config option for the public facing URL prefix. ie. http://example.com/ because TileStache won't know this.
There are both pros and cons of supporting this in TileStache, but it is an idea.
The text was updated successfully, but these errors were encountered: