Since the USA is such a large proportion of the whole planet file
(probably over 50%) I believe most people import the whole planet file
instead of trying to extract the US data.
As far as I remember (bz2 compressed files):
World 13 GB
USA 3 GB
Europe 6 GB
But the suggested way, to download the
On Mon, Dec 20, 2010 at 5:57 PM, Jon Burgess jburgess...@gmail.com wrote:
On Mon, 2010-12-20 at 17:39 -0500, Will Wilson wrote:
On Mon, Dec 20, 2010 at 5:26 PM, Jon Burgess jburgess...@gmail.com
wrote:
On Mon, 2010-12-20 at 17:07 -0500, Will Wilson wrote:
1) Trying to
I'm not sure if it is documented and the process is a compromise. The
simplest thing is to apply the world diffs and put up with the small
amount of extra data which appears for the rest of the world. It should
be possible to apply a bbox filter to the diffs too but there are some
edge cases
Hi,
On 12/21/10 17:24, Will Wilson wrote:
1. Download planet.osm; extract USA with bounding polygon, import
USA.osm, don't delete planet.osm.
No: Download planet.osm, import into osm2pgsql with the -b parameter
specifiying an US bbox, delete planet.osm.
2. (Repeat) Have a cron job
Yeah, I know. I'm using the SVN sources, and compiled with protobuf-c. As I
said, I was able to load individual pbf extracts no problem; it's just that
osm2pgsql dies immediately on the combined .pbf extract. That's why I'm
thinking that Osmosis' pbf output might be bugged. I'm happy to try
Hi All,
I sent this to the newbies list, but it might belong better here.
I'm trying to load OSM data for the USA into PostGres 9.0 with PostGIS.
Downloaded the .pbf extracts for the different US regions from Geofabrik,
combined them with Osmosis, and wrote the result to uncompressed XML like
On Mon, 2010-12-20 at 16:15 -0500, Will Wilson wrote:
Hi All,
I sent this to the newbies list, but it might belong better here.
I'm trying to load OSM data for the USA into PostGres 9.0 with
PostGIS. Downloaded the .pbf extracts for the different US regions
from Geofabrik, combined
Good call. Grepping now. Might take a while. :)
So two other things:
1) Trying to use osm2pgsql to import the merged .pbf file directly died with
a generic error immediately (as opposed to importing the merged XML, which
dies 10-15 minutes in). Maybe an error in Osmosis' pbf handling?
2) What's
Hi,
Will Wilson wrote:
Good call. Grepping now. Might take a while. :)
If Jon's suspicion is true (likely), download the full planet file
instead and run osm2pgsql with a bounding box option to restrict it to
the US.
1) Trying to use osm2pgsql to import the merged .pbf file directly died
On Mon, 2010-12-20 at 17:07 -0500, Will Wilson wrote:
Good call. Grepping now. Might take a while. :)
So two other things:
1) Trying to use osm2pgsql to import the merged .pbf file directly
died with a generic error immediately (as opposed to importing the
merged XML, which dies 10-15
On Mon, Dec 20, 2010 at 5:26 PM, Jon Burgess jburgess...@gmail.com wrote:
On Mon, 2010-12-20 at 17:07 -0500, Will Wilson wrote:
1) Trying to use osm2pgsql to import the merged .pbf file directly
died with a generic error immediately (as opposed to importing the
merged XML, which dies 10-15
On Mon, 2010-12-20 at 17:39 -0500, Will Wilson wrote:
On Mon, Dec 20, 2010 at 5:26 PM, Jon Burgess jburgess...@gmail.com
wrote:
On Mon, 2010-12-20 at 17:07 -0500, Will Wilson wrote:
1) Trying to use osm2pgsql to import the merged .pbf file
directly
died with
Also, does .pbf format support changesets yet?
No idea. Since most changesets are small the time and space savings of
PBF are generally less important.
Exactly. There is no changeset-PBF format at present for the reasons you stated.
Scott
___
13 matches
Mail list logo
