You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last version, using docker:latest
The hash of the image is sha256:d6d41e431ded9dafb61be1efd6e178c8b9f4243556f4f0425bd7a7f719010436
Docker image
latest
What operating system, osm2pgsql, and PostgreSQL/PostGIS versions are you using?
Rocky Linux 8 > docker-compose, latest version
PostGIS 3.3.3+dfsg-1.pgdg110+1 spatial database extension with PostgreSQL 15 bullseye
What did you do exactly?
Here is the instructions I executed in the Terminal of the host (I obfuscated the user and the password for security reasons).
Also, I have downloaded the osm.pbf file for the State of NY.
It to work ;o))
More seriously, to download the Parks in NYS.
What did happen instead?
I got an error on nested polygons:
2023-07-06 10:40:06,042:INFO:pgosm-flex:pgosm_flex:Calculating nested polygons
2023-07-06 10:40:06,042:INFO:pgosm-flex:db:Building nested polygons... (this can take a while)
2023-07-06 10:40:06,075:INFO:pgosm-flex:db:Nested polygon output:
ERROR: procedure osm.build_nested_admin_polygons() does not exist
LINE 1: CALL osm.build_nested_admin_polygons();
^
HINT: No procedure matches the given name and argument types. You might need to add explicit type casts.
I have a hunch (as the log says) that the procedure osm.build_nested_admin_polygons is just missing.
What did you do to try analyzing the problem?
Read the logs.
The text was updated successfully, but these errors were encountered:
Hi @asitemade4u - Thank you for reporting this! This is a bug, sorry!
This issue affects any layersets that do not define place=true to include the function definition. To work around with current versions, try adding --skip-nested to your docker exec command. That should bypass the failing query. At least, it works in my quick test!
Source of the issue
The logic here is responsible for skipping the function call when necessary, apparently it's not working. It appears like it's trying to check for and avoid this issue (see here and here) but somehow it's not working as expected.
On a closer look I think I got it a bit wrong in my prior comment.
This affects layersets that define place=false. Omitting the place layer from the .ini file appears to succeed without requiring the --skip-nested workaround. Looks like this logic is being evaluated improperly.
What version of PgOSM Flex are you using?
Last version, using
docker:latest
The hash of the image is
sha256:d6d41e431ded9dafb61be1efd6e178c8b9f4243556f4f0425bd7a7f719010436
Docker image
latest
What operating system, osm2pgsql, and PostgreSQL/PostGIS versions are you using?
What did you do exactly?
Here is the instructions I executed in the Terminal of the host (I obfuscated the user and the password for security reasons).
Also, I have downloaded the
osm.pbf
file for the State of NY.Lastly, here is the personalized layerset I am applying (
parks.ini
):What did you expect to happen?
It to work ;o))
More seriously, to download the Parks in NYS.
What did happen instead?
I got an error on nested polygons:
I have a hunch (as the log says) that the procedure
osm.build_nested_admin_polygons
is just missing.What did you do to try analyzing the problem?
Read the logs.
The text was updated successfully, but these errors were encountered: