Hi Klaus,
attached is r200 with my patch applied (the binary)
splitter.jar http://gis.19327.n5.nabble.com/file/n5731709/splitter.jar
Ciao,
Gerd
--
View this message in context:
http://gis.19327.n5.nabble.com/Still-problems-with-lakes-tp5725668p5731709.html
Sent from the Mkgmap Development
When running splitter (r178) I get a long header error. Whta does this mean?
Thanks! Log below.
java -jar -Xmx2012m splitter.jar --max-nodes=100
philippines.osm.pbf --output=xml --write-kml=split.kml
--output-dir=/home/maning/osm/routable_garmin/dev/split
cache=
description=
On Fri, Oct 19, 2012 at 04:22:23PM +0800, maning sambale wrote:
When running splitter (r178) I get a long header error. Whta does this mean?
Corrupted file or a bug in the parser.
Have you tried with some other program, such as osmosis --rb?
Marko
I confirm this is a corrupted file.
On Fri, Oct 19, 2012 at 4:50 PM, Marko Mäkelä marko.mak...@iki.fi wrote:
On Fri, Oct 19, 2012 at 04:22:23PM +0800, maning sambale wrote:
When running splitter (r178) I get a long header error. Whta does this mean?
Corrupted file or a bug in the parser.
On Fri, Oct 19, 2012 at 05:48:18PM +0800, maning sambale wrote:
Have you tried with some other program, such as osmosis --rb?
I like splitter because it automatically splits the data using the
--max-nodes switch.
I did not mean that you should replace splitter with Osmosis in your
workflow. I
Am 13.10.2012 23:51, schrieb Steve Ratcliffe:
Hi
It looks like you got these twisted around. CR is U+000D and LF is
U+000A.
Oops! well spotted, thanks!
..Steve
Hi,
thank's for the patch. From my point of view it can be committed.
Chris
