When I run the resulting planet through Splitter (a Mkgmap companion application) the result is only 95 tiles that are incomplete (~1.8 GB) while I expect about 1800 tiles (~30 GB).
Using a planet created by osmupdate the first splitted tile contains: 657.265 nodes, 62.385 ways, 571 relations.
Using the latest official planet the first splitted tile contains 1.292.878 nodes, 120.402 ways, 2.531 relations.
Apparently osmupdate does not create a valid enough planet that Splitter can handle properly.
Therefore I would like to use Osmosis again as I have without problems before the freeze in normal changeset publications on April 1st. So the question is: does anyone know how to use Osmosis in combination with the redaction changesets?
Below is the Splitter command:
java -Xmx3000m -ea -jar ~/garmin/utils/splitter/splitter.jar
A few days ago another user had problems with the planet “120508”. We found out that his version was corrupted. Please check this file, e.g. via
./osmconvert ~/planet.openstreetmap.org/planet-120508.osm.pbf --out-statistics
Please ensure to have the newest versions of osmconvert and osmupdate.
I downloaded the osmconvert and osmupdate utilities on the 4th of June, those are the latest versions? The 32bit Linux version of Osmupdate/convert are used on 64bit Linux (there is no 64bit version available), this should not cause problems?
The planet 120508 is fine for splitter. I also have the same problem for the 120401 planet which splitter handles normally. Whatever source planet file I’m using, it is the result from osmupdate that does not parse well with Splitter.