Open PanierAvide opened 4 years ago
Yes, I experienced that too. And many more similar issues while using large osm file. It fails because is encoding for TAB. And code is actually using TAB as a field separator in SQL for inserts. So, this extra TAB should either be escaped properly or just cleaned as a pre-processing step, for example
grep --in-place -e 's/	/ /g' your_file.osm
to replace it with SPACE.
That process, of finding small issues like that and trying to fix them and rerun again, would be easier to use if instead of executing whole process in one run I could restart from the point where I was left. For example, if I have already ingested nodes, I would prefer next time start from osm_ways. Even better, if I could get SQL statements generated for inserting data, instead of loading data right away.
How to fix this issue in Mac and Windows environment. I am getting this issue for most of the data now a days..
Bump
Hello,
First, thanks for all the work done around osm2pgrouting, which is an amazing tool. I'm having some errors when a tag value contains the
	
character (seems to be tabulation). When a way contain such tag, it creates an error on PostgreSQL side (extra data after last expected column), and way isn't inserted in database. I suspect that this character is interpreted as a raw tabulation when SQL command is sent to PostgreSQL, making it like the column separator.Best regards.
Bug context
Example OSM file
Error
Full log