Frédéric Rodrigo

Could you get the postgres log with the sql error ``` docker logs openmaptiles_postgres_1 ```

It is a general issue with all secondary tables in OMT. The type on geometries are inferred form initial data and not by the by the wished type. I think...

The issue is not related to table created by OMT, but with imposm generalized table. On OMT, `CREATE TABLE foo AS SELECT` create geometry column of type `geometry`, allowing any...

With Andorra as extract ``` openmaptiles=# \d osm_landuse_polygon Table "public.osm_landuse_polygon" Column | Type | Modifiers ----------+-------------------------+------------------------------------------------------------------ id | integer | not null default nextval('osm_landuse_polygon_id_seq'::regclass) osm_id | bigint | not null...

I made PR on imposm to fix this https://github.com/omniscale/imposm3/issues/262 https://github.com/omniscale/imposm3/pull/263 But even if the fix is merged and a release is done, OSM is still using a very old version...

This PR is only on z14.

Yes. English version here : https://medium.com/@frederic.rodrigo/optimization-of-openstreetmap-background-vector-tile-production-for-an-on-request-service-makina-5f6dba98a232 On Z13 only large building are already on tiles. This approach does not match this existing zoom level. https://github.com/openmaptiles/openmaptiles/blob/master/layers/building/mapping.yaml#L3 My test does not have...

Nevertheless, my other PRs are more elementaries and should be instructed to simply the buildings layer.

@daliborjanak @klokan About the osm_id I make a prof of concept and I am able to do it. Nevertheless, currently the feature_id of the building layer is not set to...

@klokan but do you not prefer first we switch the feature_id of building layer to osm_id alone in a PR?