Re: [OSM-dev] Bin-test failed (different test)
On Mon, Oct 4, 2010 at 1:56 AM, Scott Crosby scro...@cs.rice.edu wrote: On Thu, Sep 30, 2010 at 7:41 PM, Brett Henderson br...@bretth.com wrote: On Fri, Oct 1, 2010 at 12:23 AM, Curt Nowak no...@bwl.uni-hildesheim.dewrote: Hello dev, I also tested osmosis 0.37-SNAPSHOT with the bin-support for various countries downloaded at Geofabrik. In contrast to the -xml tasks I *sometimes* ran into an exception using the -bin tasks in combination with the --used-node task. What's up with that? Why is there suddenly a negative user id involved that is not present in the .osm file of Slovenia? Btw: This does *not* happen for all tested input files. E.g. Andorra worked fine. For users that aren't public, a user called NONE is used within the Osmosis pipeline. It has an id of -1. But that is typically not written to data files. The bin tasks may need to update their handling of private users ... I think I know the cause: When metadata is stripped during writing. No UID is stored. If that file is later read the binary reader has to plug in some UID for downstream osmosis and OsmUser.NONE is used. If the output of this processing is written to a binary file, without metadata stripping, the code will preserve the UID=-1 to the file. Now, when that file is read again, the reader passes the UID=-1 to downstream osmosis, which doesn't like it. The root cause is osmosis assumes and requires that all entities have metadata, and I offer a feature that allows it to be stripped for a15% gain in filesize and processing speed. Brett, how do you suggest I handle the case of stripped metadata to downstream osmosis? FIXES: 1. I suspect that somewhere in Frederik's pipeline is an omitmetadata=true, but downstream processing reads a file written with that flag set, and writes a file without that flag. 2. Error out when writing a binary file that contains UID0, to catch mistakes of type 1.Those situations are sorta silly as space is wasted storing useless metadata. 3. Transparently map UID0 in the file to OsmUser.NONE when reading. 4. Make osmosis not care if UID's are negative. My preference is fix #4, but warn if negative UID's are being written, to detect use errors with of the discussed in fixes #2 and #1. Are you aware that a user is not always available? Some entities in the planet will not have a user id available, it is optional. This is because some data has been edited by users without their public flag set. So we have to deal with missing user data in all cases, not just in the case where you've dropped metadata. If you are writing -1 to a file when OsmUser.NONE is received, then all planet derived data files will include this type of data. OSM in general doesn't allow negative UIDs so in general they should never exist. I set the Osmosis.NONE user to -1 which indicates the special case where no user is available. I added the negative check to Osmosis as a check to verify this. In your case it sounds like you should be checking for the -1 in your data files (if that's how you wish to represent OsmUser.NONE) and using OsmUser.NONE instead of trying to instantiate a new OsmUser (ie. Option 3). Cheers, Brett ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed (different test)
On Thu, Sep 30, 2010 at 7:41 PM, Brett Henderson br...@bretth.com wrote: On Fri, Oct 1, 2010 at 12:23 AM, Curt Nowak no...@bwl.uni-hildesheim.dewrote: Hello dev, I also tested osmosis 0.37-SNAPSHOT with the bin-support for various countries downloaded at Geofabrik. In contrast to the -xml tasks I *sometimes* ran into an exception using the -bin tasks in combination with the --used-node task. What's up with that? Why is there suddenly a negative user id involved that is not present in the .osm file of Slovenia? Btw: This does *not* happen for all tested input files. E.g. Andorra worked fine. For users that aren't public, a user called NONE is used within the Osmosis pipeline. It has an id of -1. But that is typically not written to data files. The bin tasks may need to update their handling of private users ... I think I know the cause: When metadata is stripped during writing. No UID is stored. If that file is later read the binary reader has to plug in some UID for downstream osmosis and OsmUser.NONE is used. If the output of this processing is written to a binary file, without metadata stripping, the code will preserve the UID=-1 to the file. Now, when that file is read again, the reader passes the UID=-1 to downstream osmosis, which doesn't like it. The root cause is osmosis assumes and requires that all entities have metadata, and I offer a feature that allows it to be stripped for a15% gain in filesize and processing speed. Brett, how do you suggest I handle the case of stripped metadata to downstream osmosis? FIXES: 1. I suspect that somewhere in Frederik's pipeline is an omitmetadata=true, but downstream processing reads a file written with that flag set, and writes a file without that flag. 2. Error out when writing a binary file that contains UID0, to catch mistakes of type 1.Those situations are sorta silly as space is wasted storing useless metadata. 3. Transparently map UID0 in the file to OsmUser.NONE when reading. 4. Make osmosis not care if UID's are negative. My preference is fix #4, but warn if negative UID's are being written, to detect use errors with of the discussed in fixes #2 and #1. Scott ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed (different test)
Am 03.10.2010 17:56, schrieb Scott Crosby: When metadata is stripped during writing. No UID is stored. If that file is later read the binary reader has to plug in some UID for downstream osmosis and OsmUser.NONE is used. If the output of this processing is written to a binary file, without metadata stripping, the code will preserve the UID=-1 to the file. Now, when that file is read again, the reader passes the UID=-1 to downstream osmosis, which doesn't like it. The solution sounds easy: When --write-bin is used without metadata-stripping on, reject writing an entity with OsmUser.NONE but i guess this will likely break reading a regular planet which has anonymous editor in it. Peter ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed (different test)
Hello dev, I also tested osmosis 0.37-SNAPSHOT with the bin-support for various countries downloaded at Geofabrik. In contrast to the -xml tasks I *sometimes* ran into an exception using the -bin tasks in combination with the --used-node task. For my example I used slovenia.osm.pbf (29-Sep-2010 03:41) downloaded at Geofabrik. Here's a simplified yet working example of the two commands I ran consecutively: osmosis.bat --read-bin slovenia.osm.pbf outPipe.0=fileReadPipe --used-node-0.6 inPipe.0=fileReadPipe outPipe.0=usedNodePipe --write-bin inPipe.0=usedNodePipe slovenia_filtered.osm.pbf osmosis.bat -verbose --read-bin slovenia_filtered.osm.pbf outPipe.0=fileReadPipe --write-bin inPipe.0=fileReadPipe slovenia_filtered2.osm.pbf (Complete error message at the end of this mail) Note, that running the following two commands does *not* throw an exception (the difference is the -xml version of writing and reading): osmosis.bat --read-bin slovenia.osm.pbf outPipe.0=fileReadPipe --used-node-0.6 inPipe.0=fileReadPipe outPipe.0=usedNodePipe --write-xml inPipe.0=usedNodePipe slovenia_filtered.osm osmosis.bat --read-xml slovenia_filtered.osm outPipe.0=fileReadPipe --write-bin inPipe.0=fileReadPipe slovenia_gefiltert_no_residential.osm.pbf What's up with that? Why is there suddenly a negative user id involved that is not present in the .osm file of Slovenia? Btw: This does *not* happen for all tested input files. E.g. Andorra worked fine. Curt C:\Programme\OSM\Kartenc:\Programme\OSM\osmosis\osmosis-0.37\bin\osmosis.bat -verbose --read-bin slovenia_filtered.osm.pbf outPipe.0=fileReadPipe --write-bin inPipe.0=fileReadPipe slovenia_filtered2.osm.pbf 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.Osmosis run INFO: Osmosis Version 0.37-SNAPSHOT-r23376 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Searching for JPF plugins. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Registering the core plugin. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Registering the extension plugins. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.Osmosis run INFO: Preparing pipeline. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.Pipeline prepare FEIN: Building tasks. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.Pipeline buildTasks FEIN: Created task 1-read-bin 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.Pipeline buildTasks FEIN: Created task 2-write-bin 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.Pipeline prepare FEIN: Connecting tasks. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.PipeTasks putTask FEIN: Task 1-read-bin produced pipe fileReadPipe 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.Pipeline connectTasks FEIN: Connected task 1-read-bin 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.PipeTasks retrieveTask FEIN: Task 2-write-bin consumed pipe fileReadPipe 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.Pipeline connectTasks FEIN: Connected task 2-write-bin 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.Osmosis run INFO: Launching pipeline execution. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager execute FEIN: Launching task 1-read-bin in a new thread. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.PassiveTaskManager execute FEIN: Task 2-write-bin is passive, no execution required. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.Osmosis run INFO: Pipeline executing, waiting for completion. 30.09.2010 16:18:06 org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager waitForCompletion FEIN: Waiting for task 1-read-bin to complete. 30.09.2010 16:18:11 org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager waitForCompletion SCHWERWIEGEND: Thread for task 1-read-bin failed org.openstreetmap.osmosis.core.OsmosisRuntimeException: A user id of -1 is not permitted. at org.openstreetmap.osmosis.core.domain.v0_6.OsmUser.init(OsmUser.java:53) at crosby.binary.osmosis.OsmosisBinaryParser.getUser(OsmosisBinaryParser.java:43) at crosby.binary.osmosis.OsmosisBinaryParser.parseWays(OsmosisBinaryParser.java:160) at crosby.binary.BinaryParser.parse(BinaryParser.java:104) at crosby.binary.BinaryParser.handleBlock(BinaryParser.java:51) at crosby.binary.file.FileBlock.process(FileBlock.java:111) at crosby.binary.file.BlockInputStream.process(BlockInputStream.java:15) at crosby.binary.osmosis.OsmosisReader.run(OsmosisReader.java:36) at java.lang.Thread.run(Unknown Source) 30.09.2010 16:18:11 org.openstreetmap.osmosis.core.pipeline.common.PassiveTaskManager waitForCompletion FEIN: Task 2-write-bin is passive, no completion wait required. 30.09.2010 16:18:11
Re: [OSM-dev] Bin-test failed
On Thu, Sep 30, 2010 at 11:09 AM, Christian H. Bruhn br...@arcor.de wrote: Hello Scott, Tuesday, September 28, 2010, 9:09:16 PM, you wrote: Is your problem repeatable? Yes. If it is repeatable, one explanation is that a 'too big' block was generated, and somehow the warning was missed. That can be tested by running a smaller batchlimit. Can you try a '--write-bin file=FOO batchlimit=2000' on the initial conversion from *.osm to *.osm.pbf and the later --read-xml-change tests and see if the problem goes away? If so, please report the result to help me fine-tune the block size and batch limit settings. When I use 'batchlimit=200' I get the same results. I even tried osmosis-0.37-SNAPSHOT-r23376. I have no explanation for the failure, especially if you tested batchlimit=200 and there were no warnings printed. Maybe it's a Java-problem. I noticed that I didn't use the latest update. I will update and test again. Thank you. Hopefully this will fix it. If not, can you try building the initial planet.osm.pbf on a windows and unix machine and comparereport md5sums? Scott ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed (different test)
On Fri, Oct 1, 2010 at 12:23 AM, Curt Nowak no...@bwl.uni-hildesheim.dewrote: Hello dev, I also tested osmosis 0.37-SNAPSHOT with the bin-support for various countries downloaded at Geofabrik. In contrast to the -xml tasks I *sometimes* ran into an exception using the -bin tasks in combination with the --used-node task. For my example I used slovenia.osm.pbf (29-Sep-2010 03:41) downloaded at Geofabrik. Here's a simplified yet working example of the two commands I ran consecutively: osmosis.bat --read-bin slovenia.osm.pbf outPipe.0=fileReadPipe --used-node-0.6 inPipe.0=fileReadPipe outPipe.0=usedNodePipe --write-bin inPipe.0=usedNodePipe slovenia_filtered.osm.pbf osmosis.bat -verbose --read-bin slovenia_filtered.osm.pbf outPipe.0=fileReadPipe --write-bin inPipe.0=fileReadPipe slovenia_filtered2.osm.pbf (Complete error message at the end of this mail) Note, that running the following two commands does *not* throw an exception (the difference is the -xml version of writing and reading): osmosis.bat --read-bin slovenia.osm.pbf outPipe.0=fileReadPipe --used-node-0.6 inPipe.0=fileReadPipe outPipe.0=usedNodePipe --write-xml inPipe.0=usedNodePipe slovenia_filtered.osm osmosis.bat --read-xml slovenia_filtered.osm outPipe.0=fileReadPipe --write-bin inPipe.0=fileReadPipe slovenia_gefiltert_no_residential.osm.pbf What's up with that? Why is there suddenly a negative user id involved that is not present in the .osm file of Slovenia? Btw: This does *not* happen for all tested input files. E.g. Andorra worked fine. For users that aren't public, a user called NONE is used within the Osmosis pipeline. It has an id of -1. But that is typically not written to data files. The bin tasks may need to update their handling of private users ... Brett ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed
On Sat, Sep 25, 2010 at 2:51 AM, Christian H. Bruhn br...@arcor.de wrote: Friday, September 24, 2010, 6:06:59 PM, Scott Crosby wrote: Is there an error message thrown? If so, please paste it. No error message, everything seems to be OK. If the error message is something about a possibly corrupt file. I'm aware of the issue. To detect bad files and fail gracefully, I put in some size limits that I later found might be too small. The patch with the increased limits is waiting for me to push out a new jar. I've just tested it with the planet-100922.osm.bz2 (MD5 checked) and 20100922-20100923.osc.gz. All osmosis tasks run with the -v option under Windows 7 Prof. 64 Bit with osmosis-snapshot 0.37 from 23.09.2010. I'm not replicating the problem. I'm running under my working tree. The only relevant differences are increased maximum blocksize limits. Here is what I ran (under ubuntu linux. pbzip2 is a parallel bzip2 decompressor, which is then buffered with mbuffer.): ## I converted the planet twice, once for faster writing, one not. pbzip2 -d foo/planet-100922.osm.bz2.1 | ~/source/Map2/osmosis/package/bin/osmosis --read-xml file=- --lp --b bufferCapacity=12000 --write-bin file=planet.osm.pbf compress=none pbzip2 -d foo/planet-100922.osm.bz2.1 | ~/source/Map2/osmosis/package/bin/osmosis --read-xml file=- --lp --b bufferCapacity=16000 --write-bin file=planet-default.osm.pbf ## Resulting sizes are as expected ## I then tried merging changesets. ~/source/Map2/osmosis/package/bin/osmosis --read-xml-change file=20100922-20100923.osc.gz --read-bin file=planet.osm.pbf --b bufferCapacity=12000 --apply-change --lp --b bufferCapacity=12000 --write-bin file=out.osm.pbf ~/source/Map2/osmosis/package/bin/osmosis --read-xml-change file=20100922-20100923.osc.gz --read-bin file=planet-default.osm.pbf --b bufferCapacity=12000 --apply-change --lp --b bufferCapacity=12000 --write-bin file=out-default.osm.pbf pbzip2 -d foo/planet-100922.osm.bz2.1 | ~/source/Map2/osmosis/package/bin/osmosis --read-xml-change file=20100922-20100923.osc.gz --read-xml file=- --lp --b bufferCapacity=12000 --apply-change --lp --b bufferCapacity=12000 --write-bin file=planet-xmlin.osm.pbf ## All three run to completion, returning identical output files of about the expected sizes: 8835376 -rw-r--r-- 1 scrosby scrosby 9047420819 Sep 28 11:00 out-default.osm.pbf 8835376 -rw-r--r-- 1 scrosby scrosby 9047420819 Sep 28 10:14 out.osm.pbf 8835376 -rw-r--r-- 1 scrosby scrosby 9047420819 Sep 28 12:06 planet-xmlin.osm.pbf 8824112 -rw-r--r-- 1 scrosby scrosby 9035884739 Sep 28 10:37 planet-default.osm.pbf 18576056 -rw-r--r-- 1 scrosby scrosby 19021875191 Sep 28 10:12 planet.osm.pbf Is your problem repeatable? If it is repeatable, one explanation is that a 'too big' block was generated, and somehow the warning was missed. That can be tested by running a smaller batchlimit. Can you try a '--write-bin file=FOO batchlimit=2000' on the initial conversion from *.osm to *.osm.pbf and the later --read-xml-change tests and see if the problem goes away? If so, please report the result to help me fine-tune the block size and batch limit settings. Scott ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed
On Sat, Sep 25, 2010 at 2:51 AM, Christian H. Bruhn br...@arcor.de wrote: Friday, September 24, 2010, 6:06:59 PM, Scott Crosby wrote: Is there an error message thrown? If so, please paste it. No error message, everything seems to be OK. If the error message is something about a possibly corrupt file. I'm aware of the issue. To detect bad files and fail gracefully, I put in some size limits that I later found might be too small. The patch with the increased limits is waiting for me to push out a new jar. I've just tested it with the planet-100922.osm.bz2 (MD5 checked) and 20100922-20100923.osc.gz. All osmosis tasks run with the -v option under Windows 7 Prof. 64 Bit with osmosis-snapshot 0.37 from 23.09.2010. I unpacked the bz2 and get the pure xml-File (180.299.278.449 bytes). I converted it with read-xml and write-bin (9.035.884.739 bytes). File size seems to be OK. Thanks for the bug report. I'll try to get replicate it, but it may be a week or two. I've had something occur that's forcing me to stay off of the computer. Scott ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed
Friday, September 24, 2010, 6:06:59 PM, Scott Crosby wrote: Is there an error message thrown? If so, please paste it. No error message, everything seems to be OK. If the error message is something about a possibly corrupt file. I'm aware of the issue. To detect bad files and fail gracefully, I put in some size limits that I later found might be too small. The patch with the increased limits is waiting for me to push out a new jar. I've just tested it with the planet-100922.osm.bz2 (MD5 checked) and 20100922-20100923.osc.gz. All osmosis tasks run with the -v option under Windows 7 Prof. 64 Bit with osmosis-snapshot 0.37 from 23.09.2010. I unpacked the bz2 and get the pure xml-File (180.299.278.449 bytes). I converted it with read-xml and write-bin (9.035.884.739 bytes). File size seems to be OK. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.Osmosis run INFO: Osmosis Version 0.37-SNAPSHOT 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Searching for JPF plugins. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Registering the core plugin. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Registering the extension plugins. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.Osmosis run INFO: Preparing pipeline. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.Pipeline prepare FEIN: Building tasks. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.Pipeline buildTasks FEIN: Created task 1-read-xml 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.Pipeline buildTasks FEIN: Created task 2-write-bin 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.Pipeline prepare FEIN: Connecting tasks. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.PipeTasks putTask FEIN: Task 1-read-xml produced unnamed pipe stored at level 1 in the default pipe stack. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.Pipeline connectTasks FEIN: Connected task 1-read-xml 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.PipeTasks retrieveTask FEIN: Task 2-write-bin consumed unnamed pipe stored at level 1 in the default pipe stack. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.Pipeline connectTasks FEIN: Connected task 2-write-bin 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.Osmosis run INFO: Launching pipeline execution. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager execute FEIN: Launching task 1-read-xml in a new thread. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.PassiveTaskManager execute FEIN: Task 2-write-bin is passive, no execution required. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.Osmosis run INFO: Pipeline executing, waiting for completion. 24.09.2010 22:51:07 org.openstreetmap.osmosis.core.pipeline.common.ActiveTaskManager waitForCompletion FEIN: Waiting for task 1-read-xml to complete. 25.09.2010 00:45:26 org.openstreetmap.osmosis.core.pipeline.common.PassiveTaskManager waitForCompletion FEIN: Task 2-write-bin is passive, no completion wait required. 25.09.2010 00:45:26 org.openstreetmap.osmosis.core.Osmosis run INFO: Pipeline complete. 25.09.2010 00:45:26 org.openstreetmap.osmosis.core.Osmosis run INFO: Total execution time: 6859581 milliseconds. Then I made four tests: 1. --read-xml-change --read-bin --apply-change --write-bin 25.09.2010 00:45:28 org.openstreetmap.osmosis.core.Osmosis run INFO: Osmosis Version 0.37-SNAPSHOT 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Searching for JPF plugins. 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Registering the core plugin. 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.TaskRegistrar loadJPFPlugins FEIN: Registering the extension plugins. 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.Osmosis run INFO: Preparing pipeline. 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.pipeline.common.Pipeline prepare FEIN: Building tasks. 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.pipeline.common.Pipeline buildTasks FEIN: Created task 1-read-xml-change 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.pipeline.common.Pipeline buildTasks FEIN: Created task 2-read-bin 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.pipeline.common.Pipeline buildTasks FEIN: Created task 3-apply-change 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.pipeline.common.Pipeline buildTasks FEIN: Created task 4-write-bin 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.pipeline.common.Pipeline prepare FEIN: Connecting tasks. 25.09.2010 00:45:29 org.openstreetmap.osmosis.core.pipeline.common.PipeTasks putTask FEIN: Task 1-read-xml-change produced unnamed pipe stored at
Re: [OSM-dev] Bin-test failed
Hello Peter, Thursday, September 23, 2010, 10:07:03 PM, you wrote: Am 23.09.2010 19:35, schrieb Christian H. Bruhn: seems to work properly (for only 60 seconds) but only produces a pbf-file with 128 MB? Does it work when you write to an xml file? Hm, no. It stops after uncompressed 2.7 GB. So it seems no be a bin-bug. I will try with a different planet-file. Christian ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed
On Fri, Sep 24, 2010 at 2:11 AM, Christian H. Bruhn br...@arcor.de wrote: Hello Peter, Thursday, September 23, 2010, 10:07:03 PM, you wrote: Am 23.09.2010 19:35, schrieb Christian H. Bruhn: seems to work properly (for only 60 seconds) but only produces a pbf-file with 128 MB? Does it work when you write to an xml file? Hm, no. It stops after uncompressed 2.7 GB. So it seems no be a bin-bug. Is there an error message thrown? If so, please paste it. If the error message is something about a possibly corrupt file. I'm aware of the issue. To detect bad files and fail gracefully, I put in some size limits that I later found might be too small. The patch with the increased limits is waiting for me to push out a new jar. Scott ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Bin-test failed
Hi! I tested osmosis 0.37-SNAPSHOT with the bin-support. Why does the command osmosis.bat --read-xml-change c:\osm\Planet\20100909-20100910.osc.gz --read-bin c:\osm\Planet\planet.osm.pbf --apply-change --write-bin c:\osm\planet\planet2.osm.pbf seems to work properly (for only 60 seconds) but only produces a pbf-file with 128 MB? Christian ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Bin-test failed
Am 23.09.2010 19:35, schrieb Christian H. Bruhn: seems to work properly (for only 60 seconds) but only produces a pbf-file with 128 MB? Does it work when you write to an xml file? Peter ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
