[Patch v1] now option handle-element-version for splitter
Hi all, the attached patch adds the option --handle-element-version with three possible values "keep", "fake", and "remove". With "remove" (the default) splitter works like r428, means, the version of OSM elements is not written to the output files, I also did not notice any changes regarding performance. With "keep" splitter writes the version that is found in the input file. With "fake" splitter sets the version to 1. I am not sure what to do when the input file(s) contain elements without (or invalid) version info and option keep is used. Another special case is the pbf format: Since r428 splitter always writes version 1 for nodes, this was a work-around for a problem in the JOSM pbf plugin. This is still done even with --handle-element-version=remove A last special case: with output=xml and --handle-element-version=keep or fake splitter will write api version 0.6 instead of 0.5 A binary based on r428 is available here: http://files.mkgmap.org.uk/download/291/splitter.jar Please let me know what you think about this change. Gerd <http://files.mkgmap.org.uk/download/291/splitter.jar>
I tried it and got an error: my splitter command is: java -Xmx1024m -Xms1024m -ea -jar \MKGMAP\splitter.jar --max-nodes=1400000 --handle-element-version=keep --mapid="12390000" --geonames-file=\MKGMAP\cities15000.zip --description=MI-greg --max-areas="255" --no-trim --status-freq="600" michigan-latest.osm.pbf The command shell output was: java.lang.NoClassDefFoundError: crosby/binary/file/BlockReaderAdapter at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Unknown Source) at java.lang.Class.privateGetMethodRecursive(Unknown Source) at java.lang.Class.getMethod0(Unknown Source) at java.lang.Class.getMethod(Unknown Source) at sun.launcher.LauncherHelper.validateMainClass(Unknown Source) at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source) Caused by: java.lang.ClassNotFoundException: crosby.binary.file.BlockReaderAdapter at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 7 more Error: A JNI error has occurred, please check your installation and try again Exception in thread "main" Greg On Mon, Feb 29, 2016 at 5:39 AM, Gerd Petermann < GPetermann_muenchen@hotmail.com> wrote:
Hi all,
the attached patch adds the option --handle-element-version
with three possible values "keep", "fake", and "remove".
With "remove" (the default) splitter works like r428,
means, the version of OSM elements is not written to the output files,
I also did not notice any changes regarding performance.
With "keep" splitter writes the version that is found in the input file.
With "fake" splitter sets the version to 1.
I am not sure what to do when the input file(s) contain elements
without (or invalid) version info and option keep is used.
Another special case is the pbf format:
Since r428 splitter always writes version 1 for nodes, this was a work-around
for a problem in the JOSM pbf plugin. This is still done even with --handle-element-version=remove
A last special case: with output=xml and
--handle-element-version=keep or fake splitter will write api version 0.6 instead of 0.5
A binary based on r428 is available here: http://files.mkgmap.org.uk/download/291/splitter.jar
Please let me know what you think about this change.
Gerd <http://files.mkgmap.org.uk/download/291/splitter.jar>
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Greg, I've only provided the jar file, you have to use a full splitter package from here http://www.mkgmap.org.uk/download/splitter.html and replace the splitter.jar with my version to test it. Gerd greg crago wrote
I tried it and got an error:
my splitter command is:
java -Xmx1024m -Xms1024m -ea -jar \MKGMAP\splitter.jar --max-nodes=1400000 --handle-element-version=keep --mapid="12390000" --geonames-file=\MKGMAP\cities15000.zip --description=MI-greg --max-areas="255" --no-trim --status-freq="600" michigan-latest.osm.pbf
The command shell output was:
java.lang.NoClassDefFoundError: crosby/binary/file/BlockReaderAdapter at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Unknown Source) at java.lang.Class.privateGetMethodRecursive(Unknown Source) at java.lang.Class.getMethod0(Unknown Source) at java.lang.Class.getMethod(Unknown Source) at sun.launcher.LauncherHelper.validateMainClass(Unknown Source) at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source) Caused by: java.lang.ClassNotFoundException: crosby.binary.file.BlockReaderAdapter at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 7 more Error: A JNI error has occurred, please check your installation and try again Exception in thread "main"
Greg
On Mon, Feb 29, 2016 at 5:39 AM, Gerd Petermann <
GPetermann_muenchen@
wrote:
Hi all,
the attached patch adds the option --handle-element-version
with three possible values "keep", "fake", and "remove".
With "remove" (the default) splitter works like r428,
means, the version of OSM elements is not written to the output files,
I also did not notice any changes regarding performance.
With "keep" splitter writes the version that is found in the input file.
With "fake" splitter sets the version to 1.
I am not sure what to do when the input file(s) contain elements
without (or invalid) version info and option keep is used.
Another special case is the pbf format:
Since r428 splitter always writes version 1 for nodes, this was a work-around
for a problem in the JOSM pbf plugin. This is still done even with --handle-element-version=remove
A last special case: with output=xml and
--handle-element-version=keep or fake splitter will write api version 0.6 instead of 0.5
A binary based on r428 is available here: http://files.mkgmap.org.uk/download/291/splitter.jar
Please let me know what you think about this change.
Gerd <http://files.mkgmap.org.uk/download/291/splitter.jar>;
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Patch-v1-now-option-handle-element-version-fo... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Feedback: It Works! Thank you. I can now use off-line .osm.pbf maps with JOSM to work on anyplace without having to be online line all the time. Greg On Tue, Mar 1, 2016 at 11:23 PM, Gerd Petermann < gpetermann_muenchen@hotmail.com> wrote:
Hi Greg,
I've only provided the jar file, you have to use a full splitter package from here http://www.mkgmap.org.uk/download/splitter.html and replace the splitter.jar with my version to test it.
Gerd
greg crago wrote
I tried it and got an error:
my splitter command is:
java -Xmx1024m -Xms1024m -ea -jar \MKGMAP\splitter.jar --max-nodes=1400000 --handle-element-version=keep --mapid="12390000" --geonames-file=\MKGMAP\cities15000.zip --description=MI-greg --max-areas="255" --no-trim --status-freq="600" michigan-latest.osm.pbf
The command shell output was:
java.lang.NoClassDefFoundError: crosby/binary/file/BlockReaderAdapter at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Unknown Source) at java.lang.Class.privateGetMethodRecursive(Unknown Source) at java.lang.Class.getMethod0(Unknown Source) at java.lang.Class.getMethod(Unknown Source) at sun.launcher.LauncherHelper.validateMainClass(Unknown Source) at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source) Caused by: java.lang.ClassNotFoundException: crosby.binary.file.BlockReaderAdapter at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 7 more Error: A JNI error has occurred, please check your installation and try again Exception in thread "main"
Greg
On Mon, Feb 29, 2016 at 5:39 AM, Gerd Petermann <
GPetermann_muenchen@
wrote:
Hi all,
the attached patch adds the option --handle-element-version
with three possible values "keep", "fake", and "remove".
With "remove" (the default) splitter works like r428,
means, the version of OSM elements is not written to the output files,
I also did not notice any changes regarding performance.
With "keep" splitter writes the version that is found in the input file.
With "fake" splitter sets the version to 1.
I am not sure what to do when the input file(s) contain elements
without (or invalid) version info and option keep is used.
Another special case is the pbf format:
Since r428 splitter always writes version 1 for nodes, this was a work-around
for a problem in the JOSM pbf plugin. This is still done even with --handle-element-version=remove
A last special case: with output=xml and
--handle-element-version=keep or fake splitter will write api version 0.6 instead of 0.5
A binary based on r428 is available here: http://files.mkgmap.org.uk/download/291/splitter.jar
Please let me know what you think about this change.
Gerd <http://files.mkgmap.org.uk/download/291/splitter.jar>
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Patch-v1-now-option-handle-element-version-fo... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Gerd Petermann -
Gerd Petermann
-
greg crago