<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I was having a similar complaint (which
i kept to myself at the time) when using <b>ogr2ogr</b>. In my
case, converting GDB file to PG database. <br>
<br>
First i used some flags, -a_srs -lco -nln, but these turned out to
be a massive waste of time (several orders of magnitude). So
instead i kept to the defaults and made desired changes manually
after the fact, in the DB.<br>
<br>
Maybe there should be some stern warnings in the documentation
when "luxury" options are computationally expensive? Then users
would be less likely to judge ogr2ogr as a poor performer.<br>
<pre class="moz-signature" cols="72">Martin Feuchtwanger <a class="moz-txt-link-abbreviated" href="mailto:feumar@shaw.ca">feumar@shaw.ca</a> 604-254-0361
Vancouver, BC V5N 1J6
<a class="moz-txt-link-freetext" href="http://members.shaw.ca/geomatics.developer">http://members.shaw.ca/geomatics.developer</a>
</pre>
On 27/05/2013 7:47 AM, Jukka Rahkonen wrote:<br>
</div>
<blockquote cite="mid:loom.20130527T163158-922@post.gmane.org"
type="cite">
<pre wrap="">I have measured a huge speed difference by running the same conversion from
OSM data file into PostGIS either with or without using the -skipfailures
parameter.
Without -skipfailures conversion takes about two minutes but if I add the
parameter it takes at least two hours. The command I used is this
ogr2ogr -f PostgreSQL PG:"dbname='gis' host='server' port='4326' user='user'
password='passwd'" finland.osm.pbf -gt 20000 -progress
--config OSM_COMPRESS_NODES YES -lco DIM=2 -lco geometry_name=geoloc
-lco fid=fid -skipfailures --config PG_USE_COPY YES
I wonder if it really needs to be so slow. My guess is that -skipfailures
somehow invalidates my -gt 20000 parameter.
-Jukka Rahkonen-</pre>
</blockquote>
<br>
</body>
</html>