search

pnorman / ogr2osm

pnorman's version of UVM's Rewrite of ogr2osm
Other
78 stars 46 forks source link

python killed #36

Closed sophia-xll closed 3 years ago

sophia-xll commented 7 years ago

I use 256G memory and 21T free disk space to run 9G a.gdb. After 9 hours running ,It occurs "killed".

How could this happen?What can i do to fix this? Thanks for any help.

jvelazquez90 commented 5 years ago

Hello Sophia, could you solve the problem of python killed? I have a file of streets of Argentina that weighs more than 1 GB in format shape   and when trying to convert it to osm I get that message. Transform shape to osm works for me with smaller extracts but I would need I can do it by country.

toton6868 commented 5 years ago

I have a similar problem. I have a 1.7 GB Road network. Using a 16GB Ram and 80GB storage (AWS m4.xLarge) to convert from shapefile to osm. Successfully done in MacBook Pro but when trying to automate in server it got killed. @pnorman can you look after this?

Firefishy commented 5 years ago

Likely best workaround is to split the shapefile with a tool like ogr2ogr. Example here: https://gis.stackexchange.com/questions/176622/split-shp-file-using-ogr2ogr

roelderickx commented 3 years ago

I agree with @Firefishy regarding the issues described by @jvelazquez90 and @toton6868. In both cases it sounds as if memory runs out and not enough swapspace is available to continue. However, I think @sophia-xll was affected by #38 which is fixed in the latest version. Ogr2osm shouldn't run for 9 hours, even on slow hardware using swapspace.