Hi, I'm trying to generate a planet tileset up to z14, however it seems I can't even get past import-sql since I've run into various problems related to osm_building_block_gen1().
I initially used v3.12, where make import-sql fails with the following error:
psql:/sql/parallel/building.sql:100: ERROR: GEOSUnaryUnion: TopologyException: Input geom 1 is invalid: Self-intersection at or near point -8539739.7009410355 4727139.8920735931 at -8539739.7009410355 4727139.8920735931
CONTEXT: PL/pgSQL function osm_building_block_gen1() line 14 at FOR over SELECT rows
After that, I went back to 24b9328a5f47ad5273495ffc26fcff39c03794cd, because I figured there might have been some issue with #1044. Perhaps unsurprisingly, I got the following error:
psql:/sql/parallel/building.sql:82: ERROR: invalid memory alloc request size 3427966716
CONTEXT: PL/pgSQL function osm_building_block_gen1() line 6 at FOR over SELECT rows
I'm currently running 6ac544fc9610b57fb3041eebd725211ec154885c and it seems to be working fine so far (transportation isn't finished yet). However, I feel like I'm missing out on the latest features ;). Speaking of, what exactly are the benefits of building aggregation anyway? If it leads to smaller MVT data, I'd very much appreciate some hints on how to get this working.
(I tested two different pbfs, planet-201214 and planet-201130, I haven't made any changes except for removing some layers I don't need from openmaptiles.yaml. My system has a few E7-4890v2 and 1TB RAM)
Similar issue at https://github.com/openmaptiles/openmaptiles/issues/1022
I ran into the same issue, but was able to import the whole planet (without ST_MakeValid) by using Postgres 9.6, PostGIS 3.1 and GEOS 3.9.0. The updated PostGIS/GEOS combo can handle the topology exceptions, but you need to build a custom docker image.
Here's mine for reference: https://github.com/suur/docker-postgis
Brilliant! Importing the building layer just completed without issue using your GEOS 3.9 Postgres container (in about 15 hours - which is probably reasonable since other layers took longer).
So thanks a lot for your help! Hope the openmaptiles/postgis image will be updated before long.
Hope the openmaptiles/postgis image will be updated before long.
Checking in, seems nobody's updated anything yet...
Most helpful comment
Similar issue at https://github.com/openmaptiles/openmaptiles/issues/1022
I ran into the same issue, but was able to import the whole planet (without ST_MakeValid) by using Postgres 9.6, PostGIS 3.1 and GEOS 3.9.0. The updated PostGIS/GEOS combo can handle the topology exceptions, but you need to build a custom docker image.
Here's mine for reference: https://github.com/suur/docker-postgis