Paul Norman
Paul Norman
`!ZOOM! < n` and `n > !ZOOM!` currently act differently, with the former causing a syntax error and the latter working.
~~~My error - wrong function, and my eyes saw what I was expecting, not what I had typed.~~~ Or not.
So the SQL I wrote has two calls of ST_AsBinary(way) tegola issued this SQL to the server: ```sql select 0::bigint as osm_id, st_geometrytype(way) as way from ne_ocean where way &&...
> Yes, it is trying to use regular expressions to do the !token! substitution, and for some of the feature discovery, it tries to modify the SQL. It's rudimentary right...
Okay, I found the problem, and it's a regression since v0.3.2 when I last wrote some layers. https://github.com/terranodo/tegola/blob/7fb74f7a88fd2cfda141297fb4e65e58d71a0f09/provider/postgis/postgis.go#L266-L278 This is broken in a number of ways, which I'll try to...
> Regarding needing to blow out the cache for a single tile, this is not necessarily true. tegola cache seed/purge has support for a single zxy tile via `tegola cache...
This issue is looking at where there are two sources for data at the same zoom, #94 doesn't cover that case.
Yes - all the same layer name in this case
> @pnorman I think you could simplify this query using the map `layer_name` config. For more information: https://tegola.io/documentation/configuration/#map-layers It can do half of it - it means I can split...
> Yeah that's still not supported as it brings up a lot of implementation questions like how to handle layer and feature merging / conflict handling. I was thinking iterating...