-
-
Notifications
You must be signed in to change notification settings - Fork 472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in reprocessing of ways in relation, if osmc_symbols-tag of the relation contains the word 'backslash' #2128
Comments
What are the tags on the object? If the same data in a PBF and XML gets different results, there's a bug. The fact that you're getting an error is not a bug - you're supplying a string literal for a text[] value. There's nothing wrong with doing that and doing the conversion yourself - in fact you must do it because there isn't a built-in conversion but your code is responsible for getting the string literal right, including escaping. |
I found more out about it. But first a correction of the output of osm2pgsql which got lost during copy and past: My first workaround was:
What was also working:
So I was converting the whole file and searched for 'green:white:green:' and found this relation https://www.openstreetmap.org/relation/1830701#map=14/50.1851/12.2991. That is far away from my boundingbox:
The error happens, if I convert the complete file sachsen-latest.osm.pbf to OSM-XML. |
As @pnorman mentioned the problem is in your Lua script. You make no attempt to escape/format the value correctly. The reason why this fails here and not somewhere else is probably the backslash in the tag (which also needs to be corrected in the OSM data, but that's beside the point here). Because you are using |
It sounds like the PBF vs XML bug was from the areas being covered being different, not anything to do with osm2pgsql. In that case, there is no bug on the osm2pgsql side and you will need to fix your code. |
I have added some warning words to the manual about the use of |
Thanks for your help and explanations! Here is my adjusted configuration
|
Output
2024-02-01 10:11:59 osm2pgsql version 1.10.0 (1.10.0-26-g229d832b)
2024-02-01 10:12:00 Database version: 13.5 (Debian 13.5-1.pgdg110+1)
2024-02-01 10:12:00 PostGIS version: 3.1
2024-02-01 10:12:00 Storing properties to table '"public"."osm2pgsql_properties"'.
osm2pgsql version: 1.10.0
2024-02-01 10:12:08 Reading input files done in 8s.
2024-02-01 10:12:08 Processed 21789924 nodes in 0s - 21790k/s
2024-02-01 10:12:08 Processed 3460747 ways in 7s - 494k/s
2024-02-01 10:12:08 Processed 49537 relations in 1s - 50k/s
2024-02-01 10:12:08 Reprocess marked ways (stage 2)...
2024-02-01 10:12:08 Creating id index on table 'traffic'...
2024-02-01 10:12:09 Creating id indexes took 0s
2024-02-01 10:12:09 There are 77950 ways to reprocess...
2024-02-01 10:12:10 ERROR: DB copy thread failed: Ending COPY mode for 'traffic' failed: ERROR: malformed array literal: "{green:white:green:}"
DETAIL: Unexpected end of input.
CONTEXT: COPY traffic, line 25130, column osmc_symbols: "{green:white:green:}"
What version of osm2pgsql are you using?
osm2pgsql version: 1.10.0
What operating system and PostgreSQL/PostGIS version are you using?
Ubuntu 2022.04
Tell us something about your system
16 RAM, 16 CPUs, laptop
What did you do exactly?
Importing Hiking relation using the following configuration (minimal example)
What did you do to try analyzing the problem?
Importing an OSM-PBF-files fails, OSM-XML is a workaround. Error always happens, if an osmc_symbols: "green:white:green:backslash" is present in the OSM-Data.
The text was updated successfully, but these errors were encountered: