Package: osmosis
Version: 0.34+ds1-1
Severity: important
Tags: upstream

I ran into this problem while trying to filter out all cameras in
Norway.

When I use this processing rule on the extract available from
<URL: http://download.geofabrik.de/openstreetmap/europe/norway.osm.bz2 >

 % osmosis --read-xml norway.osm \
        --node-key-value \
        keyValueList="man_made.surveillance,highway.speed_camera" \
        --write-xml surveillance.osm

I get this backtrace:


SEVERE: Thread for task 1-read-xml failed
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Cannot represent 
2147633961 as an integer.
        at 
org.openstreetmap.osmosis.core.util.LongAsInt.longToInt(LongAsInt.java:33)
        at 
org.openstreetmap.osmosis.core.domain.v0_6.CommonEntityData.init(CommonEntityData.java:142)
        at 
org.openstreetmap.osmosis.core.domain.v0_6.CommonEntityData.<init>(CommonEntityData.java:74)
        at 
org.openstreetmap.osmosis.core.domain.v0_6.Entity.<init>(Entity.java:61)
        at org.openstreetmap.osmosis.core.domain.v0_6.Node.<init>(Node.java:71)
        at 
org.openstreetmap.osmosis.core.xml.v0_6.impl.NodeElementProcessor.begin(NodeElementProcessor.java:87)
        at 
org.openstreetmap.osmosis.core.xml.v0_6.impl.OsmHandler.startElement(OsmHandler.java:90)
        at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:504)
        at 
com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1320)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
        at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:812)
        at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:741)
        at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
        at 
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
        at 
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
        at javax.xml.parsers.SAXParser.parse(SAXParser.java:392)
        at javax.xml.parsers.SAXParser.parse(SAXParser.java:195)
        at 
org.openstreetmap.osmosis.core.xml.v0_6.XmlReader.run(XmlReader.java:108)
        at java.lang.Thread.run(Thread.java:636)
Feb 11, 2013 3:24:36 PM org.openstreetmap.osmosis.core.Osmosis main
SEVERE: Execution aborted.
org.openstreetmap.osmosis.core.OsmosisRuntimeException: One or more tasks 
failed.
        at 
org.openstreetmap.osmosis.core.pipeline.common.Pipeline.waitForCompletion(Pipeline.java:146)
        at org.openstreetmap.osmosis.core.Osmosis.run(Osmosis.java:85)
        at org.openstreetmap.osmosis.core.Osmosis.main(Osmosis.java:30)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:328)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:31)


I guess OSM started using IDs larger than the value range of integers,
and that this will bother any user trying to process recent data.
Thus severity important as it affect many but not all users.

-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages osmosis depends on:
ii  ant               1.8.0-4                Java based build tool like make
ii  libcommons-codec- 1.4-2                  encoder and decoders such as Base6
ii  libcommons-compre 1.0-1                  Java API for working with tar, zip
ii  libcommons-dbcp-j 1.4-1                  Database Connection Pooling Servic
ii  libjpf-java       1.5.1+dfsg-2           Java Plugin Framework: plug-in inf
ii  libmysql-java     5.1.10+dfsg-2          Java database (JDBC) driver for My
ii  libpg-java        8.4-701-1              Java database (JDBC) driver for Po
ii  libplexus-classwo 1.5.0-2                Class loading utilities for the Pl
ii  libpostgis-java   1.5.1-5                geographic objects support for Pos
ii  libspring-beans-2 2.5.6.SEC02-2+squeeze1 modular Java/J2EE application fram
ii  libspring-jdbc-2. 2.5.6.SEC02-2+squeeze1 modular Java/J2EE application fram
ii  libspring-tx-2.5- 2.5.6.SEC02-2+squeeze1 modular Java/J2EE application fram
ii  libwoodstox-java  1:3.9.2.dfsg-2         a high-performance XML processor
ii  openjdk-6-jre [ja 6b18-1.8.13-0+squeeze2 OpenJDK Java runtime, using Hotspo

osmosis recommends no packages.

osmosis suggests no packages.

-- no debconf information

_______________________________________________
Pkg-osm-maint mailing list
Pkg-osm-maint@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-osm-maint

Reply via email to