Make it easy to generate tile.json

[hampelm]

Not a huge deal (the file format is pretty simple), but it would be nice if nodetiles automatically generated an appropriate tile.json for each tileset. Maybe have pass in the relevant properties when creating the map in an options object?

[Mr0grog]

This is definitely a good idea (and shouldn't be too hard). Do you know if the format changed at all between Wax and Mapbox.js? I have not reexamined it since that release. There might be changes to UTFGrid, too.

[bensheldon]

One thing to keep in mind with the tilejson+utfgrids is that the interaction-layer transformation is done with handlebars...embedded in json. Which becomes non-trivial for automatically generating popovers, legends, etc. for an arbitrary dataset. Furthermore, the presentation is tightly coupled to external CSS and JS.

Which isn't a reason not to do it. But is context around my dallying on it.

On Mon, May 13, 2013 at 8:07 AM, Rob Brackett notifications@github.com
wrote:

This is definitely a good idea (and shouldn't be too hard). Do you know if the format changed at all between Wax and Mapbox.js? I have not reexamined it since that release. There might be changes to UTFGrid, too.

Reply to this email directly or view it on GitHub:
#38 (comment)

[Mr0grog]

Hmm, like the helpers for routes, this probably doesn't really belong in core, but we have no better place for it at the moment. We should try and write it as loosely coupled to anything in core as possible.

the interaction-layer transformation is done with handlebars...embedded in json. Which becomes non-trivial for automatically generating popovers, legends, etc. for an arbitrary dataset.

Yeah, I'm not sure we should even attempt to tackle that part. It should be provided by the user. There's still a lot of boilerplate we can take care of, though.