Skip to main content
Geographic Information Systems

Return to Answer

edited body
Source Link
arni990
arni990
  • 11
  • 3

I had a similar problem importing romaniaRomania and hungaryHungary sql files bunbut not in the case of usUS imports. The problem was that some segments were not inserted because of an encoding problem. Solved this by changing the client encoding to UTF8 in the psql console. The code I used looks like this:

mydatabase-# \encoding UTF8
mydatabase-# \i d:/countryname_2po_4pgr.sql

I had a similar problem importing romania and hungary sql files bun not in the case of us imports. The problem was that some segments were not inserted because of an encoding problem. Solved this by changing the client encoding to UTF8 in the psql console. The code I used looks like this:

mydatabase-# \encoding UTF8
mydatabase-# \i d:/countryname_2po_4pgr.sql

I had a similar problem importing Romania and Hungary sql files but not in the case of US imports. The problem was that some segments were not inserted because of an encoding problem. Solved this by changing the client encoding to UTF8 in the psql console. The code I used looks like this:

mydatabase-# \encoding UTF8
mydatabase-# \i d:/countryname_2po_4pgr.sql
Source Link
arni990
arni990
  • 11
  • 3

I had a similar problem importing romania and hungary sql files bun not in the case of us imports. The problem was that some segments were not inserted because of an encoding problem. Solved this by changing the client encoding to UTF8 in the psql console. The code I used looks like this:

mydatabase-# \encoding UTF8
mydatabase-# \i d:/countryname_2po_4pgr.sql