Alexander Rolek

@ear7h I think this is being addressed in @gdey's port to the `geom` package, which is nearing complete.

@digitaltopo not yet, though a shim could be developed much like we did for AWS Lambda. Would you be interested in working on this?

@pnorman you have done a great job identifying various ways the current implementation is brittle. @ear7h is going to take on developing a more robust way to handle SQL substitution...

@pnorman I think you can set the `geometry_type` on the provider layer to avoid tegola trying to infer the geometry type on startup. Additional details: https://tegola.io/documentation/configuration/#provider-layers

@donnyv that sounds like a decoding error so I suspect it has to do with the WKB data in the geopackage. For reference the Gpkg Geometry Encoding spec can be...

@donnyv it appears you have 2 data providers though, the parcels and the PhotoPoints. can you provide the query for the other dataset?

@donnyv that link is not downloading for me. Is this by chance the same data? https://data-1-sussex.opendata.arcgis.com/datasets/sussex-county-tax-parcel-features/data?geometry=-76.086%2C40.947%2C-73.274%2C41.309

I was able to pull the data from the link I posted down as a GeoDatabase -> QGIS -> Save layer as GeoPackage, the run tegola against it fine. I...

Ok I think I have tracked down your issue. It appears that the geometry is encoded as a MULTISURFACE type, rather than a MULTIPOLYGON. You can see this in the...

@donnyv this is actually the first time I have encountered this issue. The WKB specification does not have these extended types. PostGIS also has an extended version of WKB called...