[OSM-talk] Osmosis and large bounding polygons

Brett Henderson brett at bretth.com
Tue Jan 8 14:10:10 GMT 2008


Hmm, this reply is probably way too late to be useful ... but I'll hit 
send anyway ;-)

Wow, the Australian polygon is 2.32MB which I thought was huge.  From 
memory I think Australia worked okay (although it took something like 10 
minutes to parse into an java Area class), but there was very little 
data in Australia at the time I tried and the planet was considerably 
smaller so that may have been the difference.

The BitSet id tracker is definitely the one to use for extracting a 
single large area, in particular because the US contains a large 
percentage of the total database.

I don't have much to add over what others have already suggested.  A 
3.4MB polygon contains an enormous number of points, reducing the number 
of points would be the first thing to try.

Milenko wrote:
> Sorry to reply to my own message, but the usa polygon from maproom is 
> 3.4MB, not 10.
>  
> -Jeremy
>
>     ----- Original Message -----
>     *From:* Milenko <mailto:milenko at king-nerd.com>
>     *Cc:* talk at openstreetmap.org <mailto:talk at openstreetmap.org>
>     *Sent:* Monday, January 07, 2008 8:27 PM
>     *Subject:* Re: [OSM-talk] Osmosis and large bounding polygons
>
>     The polygon file is quite large - around 10MB if I remember
>     correctly.  Most of the states are only 100KB or so, so it is much
>     much larger than any of the states.
>      
>     Is there any easy way to edit these polygon files?  They're
>     basically just a list of lat and lon values I think, but it'll
>     take forever to edit one of that size by hand.
>      
>     I'll try it without the larger heap size as well, but if I
>     remember correctly java was using around 300MB or so of RAM while
>     it was running.  I'll double-check it though.
>      
>     -Jeremy
>
>         ----- Original Message -----
>         *From:* Karl Newman <mailto:siliconfiend at gmail.com>
>         *To:* Jeremy Adams <mailto:milenko at king-nerd.com>
>         *Cc:* talk at openstreetmap.org <mailto:talk at openstreetmap.org>
>         *Sent:* Monday, January 07, 2008 7:42 PM
>         *Subject:* Re: [OSM-talk] Osmosis and large bounding polygons
>
>         On Jan 7, 2008 3:33 PM, Jeremy Adams <milenko at king-nerd.com
>         <mailto:milenko at king-nerd.com>> wrote:
>
>             Does anyone have any experience with osmosis and
>             extracting large polygons?  I'm trying to get the united
>             states exported using the files from the maproom.  I can
>             extract a single state in about an hour and a half, but
>             getting the whole country takes exponentially longer than
>             that.  As of right now, it's been running for about three
>             hours and the output .osm file is only about 300MB and
>             that's uncompressed.
>
>             By command-line is as follows:
>
>             java -Xmx1024m -jar osmosis.jar --rx EnableDateParsing=no
>             file="/home/jadams/planet-latest.osm" --bp
>             file="bin/polygons/united_states2pts.txt"
>             idTrackerType=BitSet --wx file=" usa.osm"
>
>             I've tried with and without enabledateparsing and
>             idtrackertype and it's not really any faster.
>
>             Is this expected performance, or do I have something wrong
>             somewhere?
>
>             -Jeremy
>
>





More information about the talk mailing list