Version mkgmap-r3093 was committed by steve on Sat, 08 Mar 2014
Fix a possible assertion when building the street index.
All cases where sorted names are compared with equals() need to be
changed to use Collator.compare() with the SrtCollator from Sort.
This patch fixes just a few cases to fix
What have you done to solve this Bernd, should I just wait for another extract
tomorrow?
I have seen this error last week, too.
I had to recreate my dach extract.
Bernd
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Gerd,
I always mix the osm data with address nodes for Vlaanderen and the Netherlands
with osmconvert.
This part of my batch file looks like this:
:osmconvert
%DIR%\Tools\osmconvert --drop-version %DIR%\%date%\Splitter\%extract%
%DIR%\resources\adres.o5m %DIR%\resources\vlaanderen-adres.o5m
BTW Here are the links to the files in case you need them:
https://www.dropbox.com/sh/d3ssenipw2vx6qs/ucrj2cNiFM/adres.o5m
https://www.dropbox.com/sh/d3ssenipw2vx6qs/bgWpOCpfwK/vlaanderen-adres.o5m
https://www.dropbox.com/sh/d3ssenipw2vx6qs/zqzksFWZcp/bnl_01.poly
Hi Minko,
ligfietser wrote
Now if I skip the first step and split it without merging the address
nodes it goes well without problems. Could it be that the splitter creates
fake ID's that overlap my address data nodes?
Or is there an overlap in osm id's with the fake address nodes?
I have no
I see this very often as well, when I use osmupdate on an earlier download. The
only solution I have found is to download a new pbf, then it works again. I
suspect therefore that osmupdate or one of the underlying tools is corrupting
the data.
Colin
On 8 March 2014 10:44:16 CET, Minko
Colin,
thanks for the hint.
No matter what other tools do: infinite loop in splitter is the worst case
as a reaction on errors ;-)
Gerd
Colin Smale wrote
I see this very often as well, when I use osmupdate on an earlier
download. The only solution I have found is to download a new pbf, then
Gerd,
If I skip merging the Vlaanderen address data then splitting goes well.
I have uploaded my 'corrupt' Benelux data which goes wrong (incl the Vlaanderen
addresses) here:
http://mijndev.openstreetmap.nl/~ligfietser/test/benelux.o5m
___
mkgmap-dev
Hi Minko,
is there a reason for merging the files before splitting? Did you try to
just pass all the files to splitter? I'm doing so with osm and
srtm-data. Don't know, if this helps in this case, but in general I
think it should be much faster.
Henning
Hi Henning,
I didnt know that you could feed multiple files to the splitter?
How do you do this?
Hi Minko,
is there a reason for merging the files before splitting? Did you try
to
just pass all the files to splitter? I'm doing so with osm and
srtm-data. Don't know, if this helps in this
Hi Minko,
thanks, I can reproduce the problem with this file.
Looking for a fix now.
Gerd
ligfietser wrote
Gerd,
If I skip merging the Vlaanderen address data then splitting goes well.
I have uploaded my 'corrupt' Benelux data which goes wrong (incl the
Vlaanderen addresses) here:
Hi Minko,
I've committed r320 to fix the loop problem.
You can specify multiplie input files, but you have to make
sure that each file contains ids which are higher than all
previous ones. I think this is the case with your address files.
The reason for the loop was a way in a mp-relation
for
Gerd wrote:
The reason for the loop was a way in a mp-relation
for which no nodes were found.
I guess this is caused by using osmconvert without the parameters
--complete-ways --complex-ways
If I use --complete-ways or --complex-ways with osmconvert, I didnt get any
output at all so I
Hi Minko,
the order of input files would be
java ... splitter.jar [options] europe.o5m adres.o5m vlaanderen-adres.o5m
Your approach with osmconvert is probably faster because you have to use
osmconvert anyway to convert to o5m.
Gerd
ligfietser wrote
Hi Gerd,
Thanks for the fix, I will
Gerd wrote:
the order of input files would be
java ... splitter.jar [options] europe.o5m adres.o5m
vlaanderen-adres.o5m
Yes I did that too.
Anyway, with r320 it seems to work, mkgmap is running now thanks!
___
mkgmap-dev mailing list
Hi Minko,
fine:-)
I think the only good reason to use splitter with an input file like
europe.o5m or planet.o5m in combination with a poly file
that extracts a small part is that it is able to keep ferry lines complete.
osmconvert --complete-ways --complex-ways -B=bnl_01.poly europe.o5m
Hi Gerd,
For both trunk and branch, I see a big detour depending on
the start point, so something is weird with road 6.
I'm afraid it could be quite difficult to get good routing in Poland
with default style. especially in BaseCamp. That's because our road
network miss highways and Garmin
Hi all,
I've contacted Markus Weber, the author of osmconvert and osmfilter.
It seems that the problem with complex-ways occurs only
in the Windows version, maybe because something goes wrong with
files 4GB. Markus doesn't have access to a Win64 system.
I use a mingw-64 installation to compile
18 matches
Mail list logo
