<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi all,</p>
<p><br>
</p>
<p>the attached patch adds the option --handle-element-version</p>
<p>with three possible values "keep", "fake", and "remove".<br>
</p>
<p>With "remove" (the default) splitter works like r428,</p>
<p>means, the version of OSM elements is not written to the output files,</p>
<p>I also did not notice any changes regarding performance.<br>
</p>
<p><br>
</p>
<p>With "keep" splitter writes the version that is found in the input file.</p>
<p>With "fake" splitter sets the version to 1.<br>
</p>
<p><br>
</p>
<p>I am not sure what to do when the input file(s) contain elements <br>
</p>
<p>without (or invalid) version info and option keep is used.</p>
<p><br>
</p>
<p>Another special case is the pbf format:</p>
<p>Since r428 splitter always writes version 1 for nodes, this was a work-around</p>
<p>for a problem in the JOSM pbf plugin. This is still done even with --handle-element-version=remove</p>
<p><br>
</p>
<p>A last special case: with output=xml and <br>
</p>
<p>--handle-element-version=keep or fake splitter will write api version 0.6 instead of 0.5</p>
<p><br>
</p>
A binary based on r428 is available here:<br>
<a id="LPlnk915718" href="http://files.mkgmap.org.uk/download/291/splitter.jar">http://files.mkgmap.org.uk/download/291/splitter.jar</a><br>
<br>
Please let me know what you think about this change.<br>
<br>
Gerd<br>
<a id="LPlnk915718" href="http://files.mkgmap.org.uk/download/291/splitter.jar"></a></div>
</body>
</html>