-
Notifications
You must be signed in to change notification settings - Fork 11
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
Return tilejson #4
Comments
Do we consider this fixed? There's still some stuff (descriptions, comments, etc...) missing from the TileJSON. Do we want to include those and, if so, do we have a source we can get them from? |
description works if the XML has a description set. center looks to be the one that remains an issue with avecado echoing the string from the XML when the JSON should have an array. bounds is probably the same, but doesn't show up in world-wide testing. |
What do you reckon the best thing to do is? Put the contents of |
currently center is repeated verbatim, and produces valid json but invalid tilejson. The right thing to do is create an array out of the string in the XML. On the other hand, I'm not sure it actually matters, given that I've yet to find a workflow that actually relies on bounds or center. |
MBS relies on a valid center. |
Fixes #4 This does not validate that the parameter in the Mapnik XML is valid, but if it is valid, it will result in a valid TileJSON.
The
data.xml
for Mapnik includes information for returning a tilejsonThat JSON fragment doesn't include all the information needed for a tilejson, but other parameters provide the name, min/max zoom, center. The required
"tiles"
key may need another command line option, since that varies depending on the hostname, and if you are accessing it remotely, localhost doesn't work.To-do:
mapbox/tilejson-spec#14 has some examples of the format, since it's not formally documented
The text was updated successfully, but these errors were encountered: