Alexander Rolek

@gorbypark yeah it's a nasty bug, one I would like to get addressed but we have some higher priorities right now. We're open to a PR on the geom package...

@gbroccolo apologies for the slow response here, I have been trying to think through a way forward. You bring up an excellent point here: the `geom` package does not support...

@gbroccolo looks like I messed up the protocol, try this one: http://slack.go-spatial.org I'm hoping we can figure out a vector to attack with the new data types so you don't...

@polastre yes I agree, its the worst kind of bug too (silent). @gbroccolo has been working on the extended geometry types so we can drop the Z value correctly. Let...

We have added a log when the postgis provider encounters an UnknownGeometryType (previously it was just a `continue`) to the `v0.12.x` if you would like to give it a try....

@iwpnd the change you submitted is really simple, so no issues there. I'm trying to figure out why I put the logic check in for zoom == 0. Looking back...

@Seltzer Answers to your questions in order: 1. Tegola does not evict files from the file cache (no TTL) so yes, it will keep creating tiles until they're explicitly purged...

@Seltzer I have not played with it personally, but the tegola s3 cache backend can be used against https://github.com/minio/minio. This might be a viable alternative to the filestore for your...

I like some of the ideas here (reading the type of the column instead of the ST_AsGeometryType). This is also related to #275

@pnorman you can work around this issue by setting the `geometry_type` for the provider layer. Additional details in the docs: https://tegola.io/documentation/configuration/#provider-layers