On Mon, Dec 20, 2010 at 5:26 PM, Jon Burgess <[email protected]> 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 minutes in). Maybe an error in Osmosis' > > pbf handling? > > Is the error message the same? > > Nope, just: Reading in file: /home/will/OSM/workdir/USA.osm.pbf Unable to open /home/will/OSM/workdir/USA.osm.pbf Error occurred, cleaning up > > 2) What's the expected behavior for Osmosis when merging contiguous > > but non-overlapping extracts? Would I have gotten the same problem if > > I'd started with .osm.bz2 ? > > 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. On Mon, Dec 20, 2010 at 5:20 PM, Frederik Ramm <[email protected]> wrote: > > 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. Yeah, my initial plan was to do what the two of you suggest, and just use planet.osm with a bounding box; but there's next-to-zero documentation that I could find on keeping a subset of planet.osm (with bbox or bpolygon) updated with daily or hourly diffs. Any reading suggestions? Also, does .pbf format support changesets yet? Yes, Osmosis does not have a de-duplication option. Furthermore, since > Geofabrik extracts are all done with clipIncompleteEntities=true, any simple > de-duplication would you leave with either one or the other half of a > split-boundary-crossing way. > Ahh, well that's very good information to have. Looks like I'll have to find another way. Thanks a lot, ~W
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
