Alexander Rolek

@dechristopher awesome! This feature has been [requested before](https://github.com/go-spatial/tegola/issues/610) so it's great you tackled it! I should be able to get a review in the next week. cc @gdey @ear7h

Another consideration with this PR is going to be the tile cache. If the query params can produce different features based on the query strings, we're going to need to...

@dechristopher and @kszafran apologies for the slow response. I missed the comments you two dropped in here. I'm interested in bringing this feature to life as well, but I posted...

@bemyak and @kszafran apologies for the slow response and thanks for the effort on this issue. ### Additional context to this discussion: * [The original issue around filtering a layer...

> How about this - once we're ready, we'll create a PR to the upstream, and then we could have a call to discuss it (e.g. on Google Meet)? Love...

@russss again, thanks for the great report. I did some investigation and you're right, there's no check for a map that has 0 layers. I think we could add this...

@Hoovs good catch. The hstore datatype is now handled by `case map[string]pgtype.Text:`

I think using mbtiles as a cache provider makes sense but not so much as a data provider. Tegola data providers expect geometries to work with, not tiles. We could...

Random idea, what if the --config-file flag supported an HTTP path? You could then store the config in one location, and fire a "reload" signal to the tegola server and...

For ease of use we would assume it's a local file unless it has a protocol in front of it (i.e. `http(s)`)