[OSM-dev] osm2pgsql failing with low cache size

[Paul Norman]

> From: Frederik Ramm [mailto:frederik at remote.org]
> Subject: Re: [OSM-dev] osm2pgsql failing with low cache size
> 
> Hi,
> 
> On 06/20/2012 02:31 AM, Michael Corey wrote:
> > I'm running this on an EC2 micro instance, which supposedly has up to
> > 613 MB of RAM. That's not a lot, but the XML I'm trying to import is
> > only 23 ways made up of 191 nodes. This will grow, but not by orders
> > of magnitude.
> 
> I don't think you have a memory problem.
> 
> > Reading in file: ./data/latest.xml
> > StartElement: Unknown element name: note Unknown node type 3
> > EndElement: Unknown element name: note
> > StartElement: Unknown element name: meta
> > EndElement: Unknown element name: meta Segmentation fault (core
> > dumped)
> 
> Can you sanitize your XML by running it through Osmosis (--read-xml
> latest.xml --write-xml foo.xml) and then try osm2psql again on the
> resulting file? Just to be safe that there's nothing strange in there
> that breaks it.

It looks like he might be using a dump from Overpass which does not generate
XML compatible with all the tools. It also (even in XAPI compatibility mode)
doesn't generate XAPI compatible output.

>From what I've seen, Osmosis has stricter validation of .osm files than
other tools.