Paul Norman

I did some more thinking and investigations. I started from a few assumptions 1. Users need to be able to input named parameters, not positional ones which will be hard...

A vector tile set normally includes data from sources that imposm can't process (e.g. natural earth). Queries are also how the layers are defined, and those queries are evaluated by...

What are the governance plans for the specification?

> What are the governance plans for the specification? For background, the general requirement for an open standard would be a mix of users and implementers, implementers not dominated by...

ping on this. I could also do a PR if there's agreement and understanding on what the schema is (though if @anandthakker already has something written, I'd prefer that)

- version and extent are specific to MVT, not vector tiles. If we were to specify format it should go a level higher in the json - I assume the...

I'm still 👎 on including the format as a property of the vector_layers object. We should use `name` to be consistent with the rest of the spec, not `id`. I'd...

It makes it technically possible, but doesn't really solve the problem that the user has to know what their system defaults for socket path and other values are.

mod_tile supports redis, but afaik it's untested in production. Kartotherian uses Cassandra for tile caching, but we've looked at the idea of moving this to Postgres to reduce the number...

> That's an important missing feature. My plan was to add an –older [timestamp|now] option to the seed command. > In the meantime you can only delete tiles with commands...