Automate tilejson generation

[rmarianski]

The tilejson tends to fall out of date as we make changes to layers. Ideally, we'd be able to create an automated process to keep them fresh.

[nvkelso]

Should we include more property keys? We have a ton, but only list 1 up to 6 for roads in this config file.

On Jun 29, 2016, at 09:54, Robert Marianski notifications@github.com wrote:

The tilejson tends to fall out of date as we make changes to layers. Ideally, we'd be able to create an automated process to keep them fresh.

―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[rmarianski]

We can try to infer them from the yaml file, but it won't be exactly right. Some queries include properties directly, and we have transforms that update the properties too.

We had also previously discussed being able to generate some documentation and these tilejson files from a single source. Or maybe there's a way that we can annotate the documentation itself to allow us to extract the relevant data to generate the tilejson.

[rmarianski]

Thinking about this a little bit more, we should be able to generate this by annotating the yaml and python transform configuration. Additionally, it might be worthwhile to convert the documentation to a template, and have the lists of possible kind values be injected in from this generated list.

[zerebubuth]

I agree - we can be more explicit about the values we're including, or the lists of keys we expect from the database. That, plus documentation strings and "for more information" links should be able to provide us pretty comprehensive docs in both HTML / Markdown and TileJSON.

[zerebubuth]

Since #1771, this might be within reach? Worth another look soon?