Issue importing data and serving tiles about incubator-baremaps HOT 2 CLOSED

[WARN ] 2021-01-28 11:20:12.881 [ForkJoinPool.commonPool-worker-83] GeometryHandler - Unable to build the geometry for relation 1713904

The warnings displayed during the import are due to a few complex relations in OpenStreetMap that are not easily translatable into valid geometries with the JTS Polygonizer. The Poligonizer throws a NullPointerException) which does not stop the import procedure, hence the choice of displaying a warning. The affected relations get saved in the database with a geometry set to null and I hope that the log (which contains the ids) will help at fixing these corner cases in the future. ;)

[ERROR] 2021-01-28 11:47:05.277 [armeria-common-worker-epoll-2-6] TileService - org.postgresql.util.PSQLException: ERROR: relation "osm_ways_z12" does not exist
Position: 320

Here, osm_ways_z12 corresponds to a materialized view used by openstreetmap-vecto to simplify geometries at a lower zoom levels (_z12) in order to improve performences. You can take a look at the import script and at the materialized view file to create the missing views and indexes.

Any data stored in postgis can be served with baremaps, so I guess that it should be possible to use imposm3 or osm2psql. Our goal with Baremaps is to create an cohesive pipeline from one end (import) to the other (export), so that it can easily be used on a desktop and then deployed on the cloud.

Our roadmap also includes the creation of a world map, so any feedback or bug fix is welcome. For now, our main limitation is infrastructure cost, i.e., a database for the whole world probably weight around 3-4TB.

from incubator-baremaps.

I didn't realize there was a separate import script. After I ran various lines manually, I am able to reproduce the map on the demo page. Thanks!

from incubator-baremaps.