I recently had a problem where my disk filled up while running splitter, but
splitter did not exit, continuing to run for over an hour before I looked at
it and killed the process. I assume it was waiting for something which could
never happen.
The log file ended with the following:
Exception in
7
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
On 26/03/16 08:53, Gerd Petermann wrote:
Hmm, seem that the build process hangs again...
Re-started and the r437 build is now available.
..Steve
Hi
I tried to find out why splitter uses the bounding box provided in the file.
The feature was added by Chris Miller with splitter release 102 with
this comment:
"Added support for the tag in OSM files. Also added a
--status-freq parameter to periodically display status information."
I
gmail.com>
Gesendet: Samstag, 26. März 2016 13:59
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
does not look different to me , on the australia latest file
Stephen
australia
On Sat, Mar 26, 2016 at 10:29 PM, Gerd Petermann
<g
Steve,
Why didn't you use the new option?
Gerd
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Steve
Sgalowski <steve.sgalow...@gmail.com>
Gesendet: Samstag, 26. März 2016 11:18
An: Development list for mkgmap
Betreff: Re:
mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von
> Steve Ratcliffe <st...@parabola.me.uk>
> Gesendet: Samstag, 26. März 2016 10:17
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct
> split
>
g, 26. März 2016 10:17
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
On 26/03/16 08:53, Gerd Petermann wrote:
> Hmm, seem that the build process hangs again...
Re-started and the r437 build i
On 26/03/16 08:53, Gerd Petermann wrote:
Hmm, seem that the build process hangs again...
Re-started and the r437 build is now available.
..Steve
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Patrik
Brunner <patrik.brun...@gmx.net>
Gesendet: Freitag, 25. März 2016 13:32
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
Good news, Gerd.
.. as long as it's not too much thoughts... ;-)
Just to give you a heads up re
n Patrik Brunner
<patrik.brunner@gmx.net>
Gesendet: Freitag, 25. März 2016 10:35
An:
mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
Gerd,
yes, it's a complicated world with these non-rectancular countries, can't
<mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Patrik
Brunner <patrik.brun...@gmx.net>
Gesendet: Freitag, 25. März 2016 13:32
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
Good news, Gerd.
.. as long as it's not too much t
trik.brun...@gmx.net>
*Gesendet:* Freitag, 25. März 2016 10:35
*An:* mkgmap-dev@lists.mkgmap.org.uk
*Betreff:* Re: [mkgmap-dev] Problem with splitter: Failed to find a
correct split
Gerd,
yes, it's a complicated world with these non-rectancular countries,
can't we change that ? ;-)
I di
5
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
Gerd,
yes, it's a complicated world with these non-rectancular countries, can't we
change that ? ;-)
I did some tests yesterday playing around with --no-trim and --p
Gesendet:* Freitag, 25. März 2016 00:13
*An:* mkgmap-dev@lists.mkgmap.org.uk
*Betreff:* Re: [mkgmap-dev] Problem with splitter: Failed to find a
correct split
Gerd,
I couldn't go to sleep without getting to the ground of this...
I performed the following tests on linux, always with my stand
-
> *Von:* mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von
> KeenOnKites <keenonki...@gmx.net>
> *Gesendet:* Freitag, 25. März 2016 00:13
> *An:* mkgmap-dev@lists.mkgmap.org.uk
> *Betreff:* Re: [mkgmap-dev] Problem with splitter: Failed to find a
> correct split
>
st.
Gerd
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von
KeenOnKites <keenonki...@gmx.net>
Gesendet: Freitag, 25. März 2016 00:13
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct sp
n:* mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im
Auftrag von KeenOnKites <keenonki...@gmx.net>
*Gesendet:* Donnerstag, 24. März 2016 22:16
*An:* mkgmap-dev@lists.mkgmap.org.uk
*Betreff:* Re: [mkgmap-dev] Problem with splitter: Failed to find a
correct split
Gerd,
-
*Von:* mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag
von KeenOnKites <keenonki...@gmx.net>
*Gesendet:* Donnerstag, 24. März 2016 22:16
*An:* mkgmap-dev@lists.mkgmap.org.uk
*Betreff:* Re: [mkgmap-dev] Problem with splitter: Failed to find a
correct split
Gerd,
* mkgmap-dev@lists.mkgmap.org.uk
*Betreff:* Re: [mkgmap-dev] Problem with splitter: Failed to find a
correct split
Gerd,
Sorry, your explanations came in during I was writing up the test
results ...
Think it's all clear so far.
As we're creating lot of different maps I'm just wondering if I
can
nnerstag, 24. März 2016 22:16
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
Gerd,
Sorry, your explanations came in during I was writing up the test results ...
Think it's all clear so far.
As we're creating lot of different m
*Von:* mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag
von Patrik Brunner <patrik.brun...@gmx.net>
*Gesendet:* Donnerstag, 24. März 2016 22:03
*An:* mkgmap-dev@lists.mkgmap.org.uk
*Betreff:* Re: [mkgmap-dev] Problem w
.@gmx.net>
Gesendet: Donnerstag, 24. März 2016 22:03
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
Gerd,
Yes, alaska.osm.pbf is small.
It works without --no-trim. And it also works with the polygon file that
belongs to alaska.o
z 2016 21:01
*An:* Development list for mkgmap
*Betreff:* Re: [mkgmap-dev] Problem with splitter: Failed to find a
correct split
Hi Patrik,
please provide the complete log from splitter and the densities-out.txt
Gerd
*Von:
<mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Gerd
Petermann <gpetermann_muenc...@hotmail.com>
Gesendet: Donnerstag, 24. März 2016 21:14
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split
Ahh, sorry, I just noticed t
that help?
Gerd
Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Gerd
Petermann <gpetermann_muenc...@hotmail.com>
Gesendet: Donnerstag, 24. März 2016 21:01
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Problem w
lopment list for mkgmap
Betreff: [mkgmap-dev] Problem with splitter: Failed to find a correct split
Hello together,
I'm running into a problem with the splitter (r435 aswell as r427) when
splitting the US_ALASKA file downloadable from Geofabrik.
The exception is:
Warning: No solution found f
Hello together,
I'm running into a problem with the splitter (r435 aswell as r427) when
splitting the US_ALASKA file downloadable from Geofabrik.
The exception is:
Warning: No solution found for partition
(49.7900390625,-179.9560546875) to (73.828125,180.0) with 6'702'717
nodes
oun...@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski
<po...@poczta.onet.pl>
Gesendet: Sonntag, 6. März 2016 15:49
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] problem with splitter and bounding polygon
Hi Gerd,
> We already have UnusedElementsRemoverHook.java which magically
>
Hi Gerd,
We already have UnusedElementsRemoverHook.java which magically
detects elements in the input file which will not appear in the
output file. If we change this filter to check against a poly
instead of a bbox it might be good enough.
I have already tested something like that, I have
Re: [mkgmap-dev] problem with splitter and bounding polygon
Hi Gerd,
> I don't yet have a solution, I just know that the current approach
> is not okay.
No easy solution. I think maybe the best would be to trim border tiles
according to bounding polygon. This could be suitable for irregular
Hi Gerd,
I don't yet have a solution, I just know that the current approach
is not okay.
No easy solution. I think maybe the best would be to trim border tiles
according to bounding polygon. This could be suitable for irregular
tiles too.
Other idea could be to estimate full content of a
März 2016 20:23
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] problem with splitter and bounding polygon
Hi Gerd,
I observe the same problem using standard extract of North America
http://download.geofabrik.de/north-america-latest.osm.pbf
I have packed my batches and splitter outpu
Hi Gerd,
I observe the same problem using standard extract of North America
http://download.geofabrik.de/north-america-latest.osm.pbf
I have packed my batches and splitter output (densities, areas) into an
archive:
http://files.mkgmap.org.uk/download/292/split-poly2.7z
I have used splitter
a.onet.pl>
Gesendet: Donnerstag, 3. März 2016 19:56
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] problem with splitter and bounding polygon
Hi Gerd,
I can't repeat the problem on smaller extracts. The problem is not so
important, I would leave it for now, unless it reappear on eas
Hi Gerd,
I can't repeat the problem on smaller extracts. The problem is not so
important, I would leave it for now, unless it reappear on easier to
track dataset.
--
Best regards,
Andrzej
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Von: mkgmap-dev-boun...@lists.mkgmap.org.uk
<mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski
<po...@poczta.onet.pl>
Gesendet: Mittwoch, 2. März 2016 08:17
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] problem with splitter and bounding poly
Hi Gerd,
thanks for your interest. That was split for 7GB custom pbf,
densities-out.txt was over 1GB. I will try to prepare some small subset
for test.
--
Best regards,
Andrzej
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Hi Andrzej,
I'll try to reproduce the problem. Please provide details regarding the
splitter options, the poly file,
and the densities-out.txt written by splitter.
Gerd
popej wrote
> Hi,
>
> I'm trying to compile a map of USA using North America extract form
> Geofabrik. I use splitter r427
El 01/03/16 a las 22:23, Andrzej Popowski escribió:
Hi,
I'm trying to compile a map of USA using North America extract form
Geofabrik. I use splitter r427 with bounding polygon, something like
that:
splitter --polygon-file=usa.poly ... north-america-latest.osm.pbf
The result is that I get
Hi,
I'm trying to compile a map of USA using North America extract form
Geofabrik. I use splitter r427 with bounding polygon, something like that:
splitter --polygon-file=usa.poly ... north-america-latest.osm.pbf
The result is that I get errors in mkgmap:
SEVERE (MapFailedException):
-dev@.org
Subject: Re: [mkgmap-dev] Problem in splitter (Africa)
gerd p would love more on the routing mate in my map but when i tried
before to upgrade the script file , it did not work may be i send the
script file i use , so you can help me convert it over to the new
scripting you do mate
Hi Stephen,
yes, you should have received an answer a now.
Gerd
Date: Tue, 6 Jan 2015 19:15:51 +1000
From: steve.sgalow...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem in splitter (Africa)
gerd P
did you get my direct e-mail to you sir
stephen
On Tue, Jan
: steve.sgalow...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem in splitter (Africa)
gerd P
did you get my direct e-mail to you sir
stephen
On Tue, Jan 6, 2015 at 10:18 AM, GerdP gpetermann_muenc...@hotmail.com
wrote:
Hi Stephen,
the log shows no problems. Why do
gerd P
did you get my direct e-mail to you sir
stephen
On Tue, Jan 6, 2015 at 10:18 AM, GerdP gpetermann_muenc...@hotmail.com
wrote:
Hi Stephen,
the log shows no problems. Why do you think that max-nodes=40 doesn't
work?
Do you see an error message in mkgmap?
If yes, please provide
wrote:
Hi Stephen,
yes, you should have received an answer a now.
Gerd
--
Date: Tue, 6 Jan 2015 19:15:51 +1000
From: steve.sgalow...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem in splitter (Africa)
gerd P
did you get my
Gerd
Date: Wed, 7 Jan 2015 16:57:41 +1000
From: steve.sgalow...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem in splitter (Africa)
gerd , have tried some of your ideas no not all worked for me however have
worked out and are combining my poi strings am re checking
;building=entrance
Please check the docu about the meaning:
http://www.mkgmap.org.uk/doc/options
Gerd
--
Date: Wed, 7 Jan 2015 16:57:41 +1000
From: steve.sgalow...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem in splitter (Africa
@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem in splitter (Africa)
gerd p would love more on the routing mate in my map but when i tried before to
upgrade the script file , it did not work may be i send the script file i use ,
so you can help me convert it over to the new scripting you do
gerd p
under stood mate , but why does it only happen to this one , but when i
change others max nodes it is all ok
i will send the style files i use ,
stephen
On Tue, Jan 6, 2015 at 10:18 AM, GerdP gpetermann_muenc...@hotmail.com
wrote:
Hi Stephen,
the log shows no problems. Why do you
Hi Stephen,
the log shows no problems. Why do you think that max-nodes=40 doesn't
work?
Do you see an error message in mkgmap?
If yes, please provide your style files so that I can reproduce the problem.
Maybe your style still adds one POI for each point of each highway?
Gerd
steve
i will send theat gerd , when i get back home
error msg was that , there is not enough room in a single file to hold all
must split file into smaller sizes
that is why i cut down max nodes per a file
stephen
On Tue, Jan 6, 2015 at 10:18 AM, GerdP gpetermann_muenc...@hotmail.com
wrote:
Hi
in some of the countries i do , if i dont make the node count small , the
map size exceedds , size limit of 3 gb
then unshure how , canada has done this ok
stephen
On Tue, Jan 6, 2015 at 5:24 AM, Gerd Petermann
gpetermann_muenc...@hotmail.com wrote:
Hi all,
I wonder what splitter should do
Hi all,
I wonder what splitter should do in this case:
Stephen uses paramter --max-nodes=8
and splitter reports
Highest node count in a single grid element is 557,084
It is obvious that at least one tile will have much more than the requested
80.000 nodes,
on the other hand, the file
Not sure what you mean. If you split a given country in a higher number
of tiles (lower max-nodes) final size will be the same or slightly
bigger, as there are more duplicated info due to overlap. Or you are
loosing some information in the process to reduce final file size.
El 05/01/15 a las
gerd and carlos
i am now running the splitter log file setup on my canada map
and see what it does , the end result on this map = 6.8 gb img file
wonder why some country can exceed and others not
stephen
On Tue, Jan 6, 2015 at 7:00 AM, Carlos Dávila cdavi...@orangecorreo.es
wrote:
Not sure
Hi Stephen,
last year mkgmap failed for a tile in Canada because of
a special case, see my post:
http://gis.19327.n5.nabble.com/ontario-canada-maps-tp5798080p5798490.html
At that time I changed mkgmap so that it doesn't
generate as many POI for these ways, and maybe later
we also changed the
i will run splitter log now on all my countries i need to update due to my
international work
and as done i will post accordingly
stephen
On Tue, Jan 6, 2015 at 7:14 AM, GerdP gpetermann_muenc...@hotmail.com
wrote:
Hi Stephen,
last year mkgmap failed for a tile in Canada because of
a
Final file size depends on the amount of data in the input, not on the
value of max-nodes. If you need a final img smaller than a given size
you have to reduce the area covered by the input file or reduce the
number of osm elements from the input that go into the map playing with
your style
Hi Gerd,
3) or stop with an error message that tells the user
that it is not possible to split with the used resolution
Seems to be the best solution. Let user decide how to proceed.
You could include some advices in final message, but the choice of
solution depends on user requirements,
found in the nodes.
Gerd
Date: Sun, 19 Oct 2014 15:58:02 +0200
From: keenonki...@gmx.net
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: [mkgmap-dev] Problem with splitter r412: invalid bbox area in pbf
file
Gents,
We run into a problem with the splitter about invalid bbox area in pbf
@lists.mkgmap.org.uk
Subject: [mkgmap-dev] Problem with splitter r412: invalid bbox area
in pbf file
Gents,
We run into a problem with the splitter about invalid bbox area in pbf
file throwing the following error:
java.lang.IllegalArgumentException: invalid bbox area in pbf file
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: [mkgmap-dev] Problem with splitter r412: invalid bbox area
in pbf file
Gents,
We run into a problem with the splitter about invalid bbox area in pbf
file throwing the following error:
java.lang.IllegalArgumentException: invalid bbox area in pbf file
Gents,
We run into a problem with the splitter about invalid bbox area in pbf
file throwing the following error:
java.lang.IllegalArgumentException: invalid bbox area in pbf file:
(49.808900356292725,-179.95320081710815) to
(73.79793405532837,180.00049352645874)
But this is sort of strange
Hi Patrik,
the error message is about the bounds tag in the input file.
I did not look at the file, but a value 180.0 is clearly not okay.
The other values are not about the bbox, but
about the min/max values of nodes.
I don't know why splitter and osmconvert report different values
here.
Hi
FYI:
splitter r393 dies with following error, if i try to split my DACH-extract,
all other extracts are not affected
java.lang.ArrayIndexOutOfBoundsException: -184650
at
uk.me.parabola.splitter.O5mMapParser.setStringRefPair(O5mMapParser.java:355)
at
Hi Bernd,
this looks like an error in the o5m file. Is osmconvert able to read it?
Gerd
From: weigelt.be...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Mon, 26 May 2014 10:20:11 +0200
Subject: [mkgmap-dev] Problem with splitter r393
Hi
FYI:
splitter r393 dies with following
Am Montag, 26. Mai 2014, 10:21:31 schrieb Gerd Petermann:
Wow, 80 seconds to get a hint ;-)
this looks like an error in the o5m file. Is osmconvert able to read it?
What shall i do?
convert from o5m to osm and back?
No problem
Bernd
--
amarok2 now playing:
Hi Bernd,
okay, so it is probably a special case :-(
Please post a link to the complete o5m file.
Gerd
From: weigelt.be...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Mon, 26 May 2014 10:28:33 +0200
Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 10:21
Hi Bernd,
and you may use 7zip to compress the o5m file first.
Gerd
From: weigelt.be...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Mon, 26 May 2014 10:28:33 +0200
Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 10:21:31 schrieb Gerd Petermann:
Wow
Am Montag, 26. Mai 2014, 10:31:46 schrieb Gerd Petermann:
Hi Gerd
okay, so it is probably a special case
Please post a link to the complete o5m file.
Sorry, my mistake
Didn't check the o5m file, only ask for that, what i should do ;-)
I have to test osmconvert 0.7T against the old and a new
Hi Bernd,
no problem. I'll try to improve the error handling for this case.
Gerd
From: weigelt.be...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Mon, 26 May 2014 11:03:36 +0200
Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 10:31:46 schrieb Gerd
Hi Bernd,
I've added a check in r395.
reg. osmupdate I suggest to contact Markus Weber:
markus.we...@gmx.com
Gerd
From: gpetermann_muenc...@hotmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Mon, 26 May 2014 11:06:18 +0200
Subject: Re: [mkgmap-dev] Problem with splitter r393
Hi Bernd
Am Montag, 26. Mai 2014, 04:27:13 schrieb GerdP:
Hi Gerd
Maybe you have a hardware problem?
RAM? HDD?
Don't think so, because then it should be more often, not only by this
extract. If my HDD has a problem, the error should be the same as this
morning, because i've renamed the file and
...@web.de
To: mkgmap-dev@lists.mkgmap.org.uk
Date: Mon, 26 May 2014 14:44:26 +0200
Subject: Re: [mkgmap-dev] Problem with splitter r393
Am Montag, 26. Mai 2014, 04:27:13 schrieb GerdP:
Hi Gerd
Maybe you have a hardware problem?
RAM? HDD?
Don't think so, because then it should be more
2012/3/12 Wolfgang Hammel wolfgang.ham...@gmx.de:
Hi,
yes you are right, this is a splitter problem which
is already known.
[]
Using --overlap=4000 solved the problem :)
--
* Matteo Gottardi | matg...@tin.it
* ICQ UIN 20381372
* Linux - the choice of a GNU generation
* GPG Fingerprint:
Hi Wolfgang, hi Richard,
thanks for all your input. I think I know now what is needed, so it is time
now
to try some coding. The biggest open problem that I see is that splitter can
be used
to split a large file like europe.osm.pbf on a small machine if you
specify e.g. max-areas=2.
Using this
further comments below...
Date: Sat, 17 Mar 2012 19:03:02 -0400
From: rhan...@bbn.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem with splitter
On 2012-03-17 14:31, Gerd Petermann wrote:
a) for each coord, way: find out all tiles that are touched,
save the infoin
On 2012-03-18 04:59, Gerd Petermann wrote:
Hi Richard,
generally I think an OSM element is touching a tile when it would
change the output of mkgmap if we simply remove it.
I agree with that definition.
So, splittter should not remove something that touches a tile
without adding something
Wolfgang.
thanks for you input. See below..
Date: Fri, 16 Mar 2012 00:11:58 +0100
From: wolfgang.hammel@
To: mkgmap-dev@.org
Subject: Re: [mkgmap-dev] Problem with splitter
Hi Gerd,
your description of splitter's algorithm is in accordance to what I
observed when I used some
On 2012-03-15 03:51, GerdP wrote:
Hi Wolfgang,
I've described splitters algorithm as it is now here:
http://gis.19327.n5.nabble.com/Problem-with-splitter-tp886p5561551.html
I am now working on a first approach that looks like this:
pass 1: calculate tile areas
pass 2:
a) for each
Hi Richard,
Date: Sat, 17 Mar 2012 13:43:17 -0400
From: rhan...@bbn.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem with splitter
On 2012-03-15 03:51, GerdP wrote:
Hi Wolfgang,
I've described splitters algorithm as it is now here:
http://gis.19327.n5
On 2012-03-17 14:31, Gerd Petermann wrote:
a) for each coord, way: find out all tiles that are touched,
save the infoin a map
What is the definition of touched?
A point normally lies in exactly one tile. Nevertheless a point can
be written to more tiles because of the overlap handling.
Hi Wolfgang.
thanks for you input. See below..
Date: Fri, 16 Mar 2012 00:11:58 +0100
From: wolfgang.ham...@gmx.de
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem with splitter
Hi Gerd,
your description of splitter's algorithm is in accordance to what I
Hi Wolfgang,
I've described splitters algorithm as it is now here:
http://gis.19327.n5.nabble.com/Problem-with-splitter-tp886p5561551.html
I am now working on a first approach that looks like this:
pass 1: calculate tile areas
pass 2:
a) for each coord, way: find out all tiles that are
Hi Gerd,
your description of splitter's algorithm is in accordance to what I
observed when I used some
simple test data.
But beside the mulitpolygon problem there is another issue that results
from the present
algorithm.
If you consider one single tile, splitter writes a certain node to that
Hi Gerd,
my first thought was also in the direction of option 2)
but yes you are right, the administrative boundaries and the coastlines
may blow up
the tiles a lot and that may probably also increase processing time in
mkgmap afterwards.
Option 3) would be the most precise one but I don't know
On Mon, Mar 12, GerdP wrote:
1) Enhance the logic in mkgmap that guesses how the missing ways completed
the multipolygon, e.g. by adding a backtracking algorithmn (this is already
suggested in the code).
2) Enhance splitter so that it writes all points and all ways of
multipolygon to each
Am 13.03.2012 06:59, schrieb GerdP:
3) Enhance splitter to write one extra output file that contains only the
1st and last point of each way that is part of a multipolygon, and create a
method in mkgmap that looks for this data when
it doesn't find the way in the normal input. We need only the
Hi Henning,
well, I think this can be done, but I see two problems:
1) Splitter would have to write the data in OSM format, means, it has to
invent some ways, nodes and the ids for them. I think we cannot simply
invent nodes for existing OSM ways.
2) I think the data structures in splitter don't
Hi Thorsten,
thanks for the qucick feedback.
Date: Tue, 13 Mar 2012 09:07:18 +0100
From: ku...@suse.de
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem with splitter
On Mon, Mar 12, GerdP wrote:
1) Enhance the logic in mkgmap that guesses how the missing ways
Hi Gerd,
On Tue, Mar 13, Gerd Petermann wrote:
I'm not that sure option 2 will really blow up the tile size and
CPU cost. Today, most people creating a map use a very huge number
for --overlap to avoid this kind of problems. And how many multipolygons
are really that big that they go
Maybe splitter could detect, if a tile is completely inside such a
polygon and then only add a rectangle with a negative ID (or parse for
highest used node/way-ID).
At all I think, that needed diskspace isn't a huge problem, if there is
no more guessing.
Henning
Am 13.03.2012 16:06, schrieb
if the tile area intersects with it This will find all good
candidates,
but maybe requires a lot more cpu time.
Gerd
Date: Tue, 13 Mar 2012 16:30:22 +0100
From: o...@aighes.de
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Problem with splitter
Maybe splitter could detect
extract of Italy
using the standard splitter-r200 options.
The area is at http://osm.org/go/0CmXpRz , and at
http://www.gomatteo.net/10.jpg you can see how it look in
QlandkarteGT.
The osm data seem ok, is a splitter problem?
___
mkgmap-dev
you can see how it look in
QlandkarteGT.
The osm data seem ok, is a splitter problem?
___
mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
--
View this message in context:
http://gis
: [mkgmap-dev] Problem with splitter
On Mon, Mar 12, GerdP wrote:
Hi Teo,
I tried to reproduce the problem with mkgmap trunk version r2248, but I get
different results, esp. I don't see this flooding.
I am using coastlines_europe-120128.osm.pbf, maybe your file is older?
You need
2012/3/12 GerdP gpetermann_muenc...@hotmail.com:
Hi Teo,
I tried to reproduce the problem with mkgmap trunk version r2248, but I get
different results, esp. I don't see this flooding.
I am using coastlines_europe-120128.osm.pbf, maybe your file is older?
Hi Gerd,
my coastlines file was the
Hi Matteo,
okay, I am able to reproduce the problem (also without the coastfile
parameter).
The log shows some warnings for relation 541757 (the Lago di Como) , so I
should be
able to understand what's happening and why it fails.
Gerd
Matteo Gottardi wrote
2012/3/12 GerdP
Hi Gerd,
when I had the problem some time ago, I did some rough checking on
splitters output.
What I know so far is, that splitter removes all the ways from a certain
tile that have no
node inside this tile.
The problem arises when a tile boundary divides a multipolyon that
consist of normally
Hi Wolfgang,
yes, that' s exactly what happens. I see three ways to solve this problem:
1) Enhance the logic in mkgmap that guesses how the missing ways completed
the multipolygon, e.g. by adding a backtracking algorithmn (this is already
suggested in the code).
2) Enhance splitter so that it
1 - 100 of 108 matches
Mail list logo
