[gdal-dev] OSM Driver and World Planet file (pbf format)

Smith, Michael ERDC-CRREL-NH Michael.Smith at usace.army.mil
Mon Jul 23 06:16:37 PDT 2012


It stopped cleanly (no segfault) at 70%. OS is RHEL 6.2 64 bit. Import
time was about 340 min.

Command was 

ogr2ogr -progress -f oci oci:user/pass at tns:tmp planet-latest.osm.pbf -lco
dim=2 -lco srid=4326 -lco geometry_name=geometry -lco launder=yes

I'm rerunning now with the debug log to a file.


Michael Smith

Remote Sensing/GIS Center
US Army Corps of Engineers

On 7/23/12  7:05 AM, "Even Rouault" <even.rouault at mines-paris.org> wrote:

>Le lundi 23 juillet 2012 12:56:12, Smith, Michael ERDC-RDE-CRREL-NH a
>écrit :
>> I'm finding that the new OSM Driver (I tested again with r24699) has a
>> problem when working with the whole planet file. When I tried with the
>> Northeast subset, I got multipolygons and multilinestring entries. When
>> reading the whole planet file, I did not. It gets to 70% and then ends
>> (but without an error message). I also got fewer polygons than I was
>> expecting. It seems like the reading got interrupted by some non
>> error.
>> I was writing to Oracle for this importing but got the same results
>> to sqlite. It seems that smaller extracts work fine but the are some
>> reading issues with the whole planet file (in pbf format). I can try
>> the .osm format.
>I didn't try yet with whole planet files. Takes too much time :-)
>Which command line did you use exactly ?
>Did it stop cleanly or with a segfault ? In the latter case, (assuming
>you are 
>on Linux), running under gdb might be useful.
>What is your OS, 32/64 bit ? Perhaps, you could add --debug on. I'd
>redirecting standard error file to a file because the log file can be
>gdal-dev mailing list
>gdal-dev at lists.osgeo.org

More information about the gdal-dev mailing list