[mkgmap-dev] Problem with splitter

Hi, I noticed a problem splitting the geofabrik pbf 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] problem with splitter

Hi, I discovered a problem with splitter.jar when using a areas.list with more then 255 tiles. If there are e.g. 256 tiles in one areas.list then splitter processes only half of the tiles e.g. 128. If there are 255 or less tiles inside, all tiles were processed. Is this a bug or a feature? I

Re: [mkgmap-dev] Problem with splitter

Hi Matteo, can you please describe the problem and what it is that makes you believe that this is a splitter problem? Gerd Matteo Gottardi-2 wrote > > Hi, I noticed a problem splitting the geofabrik pbf extract of Italy > using the standard splitter-r200 options. > > The area is at http://osm

Re: [mkgmap-dev] Problem with splitter

Looks like a coastline-problem. Which parameter you use for mkgmap? //Martin Am 11.03.2012 um 22:10 schrieb GerdP: > Hi Matteo, > > can you please describe the problem and what it is that > makes you believe that this is a splitter problem? > > Gerd > > > Matteo Gottardi-2 wrote >> >> Hi, I

Re: [mkgmap-dev] Problem with splitter

2012/3/11 Martin : > Looks like a coastline-problem. > Which parameter you use for mkgmap? The options are: - BEGIN - code-page=1252 latin1 reduce-point-density=4 reduce-point-density-polygon=8 min-size-polygon=8 remove-short-arcs merge-lines add-pois-to-areas pois-to-areas-placement style

Re: [mkgmap-dev] Problem with splitter

Hi, yes you are right, this is a splitter problem which is already known. As you can see in your example, the lake is split in a way that requires it to be split more than once along the bounding rectangle. see : http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q3/012119.html and http://www.mkg

Re: [mkgmap-dev] Problem with splitter

2012/3/11 GerdP : > Hi Matteo, > > can you please describe the problem and what it is that > makes you believe that this is a splitter problem? Hi, I don't speak english very well, so maybe a screenshot can help :) If you look at http://www.gomatteo.net/out.jpeg you can see the generated map. I m

Re: [mkgmap-dev] Problem with splitter

Hi Wolfgang, I'll try to find a solution once the remaining problems in the performance branch are solved. Gerd > Date: Mon, 12 Mar 2012 00:14:42 +0100 > From: wolfgang.ham...@gmx.de > To: mkgmap-dev@lists.mkgmap.org.uk > Subject: Re: [mkgmap-dev] Problem with splitter >

Re: [mkgmap-dev] Problem with splitter

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? Gerd Matteo Gottardi-2 wrote > > Hi, I noticed a problem splitting the geofabrik pbf e

Re: [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 the exact same tiles, else you will not se

Re: [mkgmap-dev] Problem with splitter

Subject: Re: [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 co

Re: [mkgmap-dev] Problem with splitter

2012/3/12 GerdP : > 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 same as yours, only with a d

Re: [mkgmap-dev] Problem with splitter

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

Re: [mkgmap-dev] Problem with splitter

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

Re: [mkgmap-dev] Problem with splitter

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 writ

Re: [mkgmap-dev] Problem with splitter

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 eac

Re: [mkgmap-dev] Problem with splitter

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

Re: [mkgmap-dev] Problem with splitter

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 a

Re: [mkgmap-dev] Problem with splitter

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 t

Re: [mkgmap-dev] Problem with splitter

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 the

Re: [mkgmap-dev] Problem with splitter

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

Re: [mkgmap-dev] Problem with splitter

ck 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 > > Mayb

Re: [mkgmap-dev] Problem with splitter

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

Re: [mkgmap-dev] Problem with splitter

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 "touc

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 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 ti

Re: [mkgmap-dev] Problem with splitter

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 algorit

Re: [mkgmap-dev] Problem with splitter

may be > stripped together > into one single outside way. This may be useful if we think of the > administrative boundaries. > > I don't know how complicated this will get to be implemented in splitter > and mkgmap, > so these are just my thoughts on a possible solution

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.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 e

Re: [mkgmap-dev] Problem with splitter

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 al

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 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 overl

Re: [mkgmap-dev] Problem with splitter

element if it is touching more than one tile. See 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: >

Re: [mkgmap-dev] Problem with splitter

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 s

Re: [mkgmap-dev] Problem with splitter

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 thi

Re: [mkgmap-dev] Problem with splitter

2012/3/12 Wolfgang Hammel : > 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: * B9EE 108F 52C8 D5

[mkgmap-dev] Problem with splitter r393

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 uk.me.parabola.splitter.O

Re: [mkgmap-dev] Problem with splitter r393

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 ne

Re: [mkgmap-dev] Problem with splitter r393

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

Re: [mkgmap-dev] Problem with splitter r393

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

Re: [mkgmap-dev] Problem with splitter r393

Am Montag, 26. Mai 2014, 11:23:51 schrieb Gerd Petermann: Hi Gerd > I've added a check in r395. > > reg. osmupdate I suggest to contact Markus Weber: > markus.we...@gmx.com I don't understand, what you have done, but the error has gone with r395 ;-) I made two tests, one with a new extract, cr

Re: [mkgmap-dev] Problem with splitter r393

Hi Bernd, that sounds not good to me. The only wanted effect of the change is that splitter reports an I/O error instead of failing with an ArrayIndexOutOfBoundsException. Maybe you have a hardware problem? Gerd Bernd Weigelt wrote > Am Montag, 26. Mai 2014, 11:23:51 schrieb Gerd Petermann: >

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 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 didn

Re: [mkgmap-dev] Problem with splitter r393

igelt.be...@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? > > RA

Re: [mkgmap-dev] Problem with splitter r393

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: >

Re: [mkgmap-dev] Problem with splitter r393

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: ___

Re: [mkgmap-dev] Problem with splitter r393

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 Mo

Re: [mkgmap-dev] Problem with splitter r393

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 schr

[mkgmap-dev] problem with splitter and bounding polygon

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): pbf\2972

Re: [mkgmap-dev] problem with splitter and bounding polygon

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 e

Re: [mkgmap-dev] problem with splitter and bounding polygon

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

Re: [mkgmap-dev] problem with splitter and bounding polygon

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 http://www.mk

Re: [mkgmap-dev] problem with splitter and bounding polygon

Von: mkgmap-dev-boun...@lists.mkgmap.org.uk im Auftrag von Andrzej Popowski Gesendet: Mittwoch, 2. März 2016 08:17 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] problem with splitter and bounding polygon Hi Gerd, thanks for your interest. That was split for 7GB custom pbf

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 easier to track dataset. -- Best regards, Andrzej ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk ht

Re: [mkgmap-dev] problem with splitter and bounding polygon

p-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 easier to track dataset. -- Best regard

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 output (densities, areas) into an archive: http://files.mkgmap.org.uk/download/292/split-poly2.7z I have used splitter r4

Re: [mkgmap-dev] problem with splitter and bounding polygon

kgmap-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 output (densities, areas) into an archive: http://files.mkgmap.org.uk/dow

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 tiles too. Other idea could be to estimate full content of a t

Re: [mkgmap-dev] problem with splitter and bounding polygon

se borders should work. Gerd Von: mkgmap-dev-boun...@lists.mkgmap.org.uk im Auftrag von Andrzej Popowski Gesendet: Sonntag, 6. März 2016 02:00 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] problem with splitter and bounding polygon Hi

Re: [mkgmap-dev] problem with splitter and bounding polygon

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 ext

Re: [mkgmap-dev] problem with splitter and bounding polygon

owski 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 > detects elements in the input file which will not appear in the &g

[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 for partition (49.7900390625,-179.9560546875) to (73.828125,180.0) with 6'702'717 nodes uk

[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: (49.808900356292725,-179.95320081710815) to (73.79793405532837,180.00049352645874) But this is sort of strange a

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 im Auftrag von KeenOnKites Gesendet: Donnerstag, 24. März 2016 20:25 An: Development list for mkgmap Betreff: [mkgmap-dev] Problem with splitter: Failed

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

that help? Gerd Von: mkgmap-dev im Auftrag von Gerd Petermann Gesendet: Donnerstag, 24. März 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

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

ap-dev im Auftrag von Gerd Petermann 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 that the file alaska.osm.pbf is small. The problem is here is that the bo

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

20:25 *An:* Development 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:

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

p-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.osm.pbf (also downloaded from Geofabrik) which, according to document

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

a few minutes ago. Gerd *Von:* mkgmap-dev im Auftrag von Patrik Brunner *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

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

: 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/should drop the option --

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

which some people prefer, esp. on the PC. Gerd *Von:* mkgmap-dev im Auftrag von KeenOnKites *Gesendet:* Donnerstag, 24. März 2016 22:16 *An:* mkgmap-dev@lists.mkgmap.org.uk *Betreff:* Re: [mkgmap-dev] Problem with spl

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

*Von:* mkgmap-dev im Auftrag von KeenOnKites *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, Sorry,

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

PC. Gerd *Von:* mkgmap-dev im Auftrag von KeenOnKites *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

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

others first. Gerd Von: mkgmap-dev im Auftrag von KeenOnKites 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

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

3) add code to check how the collected data matches the given bounds, > > use whatever is smaller. This might also be triggered by an option if > needed. > > > I'd like to get some feedback from others first. > > > Gerd > > > --------------

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

5. 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 standard --no-trim present:

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

nKites <mailto:keenonki...@gmx.net> Gesendet: Freitag, 25. März 2016 00:13 An: mkgmap-dev@lists.mkgmap.org.uk<mailto: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

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

, 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 did some tests yesterday playing around with

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

_ Von: mkgmap-dev im Auftrag von Patrik Brunner 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: [mkgmap-dev] Problem with splitter: Failed to find a correct split

use --ignore-osm-bounds as option name) Gerd Von: mkgmap-dev im Auftrag von Patrik Brunner 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 lo

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

Hmm, seem that the build process hangs again... Gerd Von: mkgmap-dev im Auftrag von Patrik Brunner Gesendet: Samstag, 26. März 2016 08:43 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split Many

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 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkg

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

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 ___ mkgmap-dev mailing li

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

> Von: mkgmap-dev im Auftrag von > Steve Ratcliffe > 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 > > On 26/03/16 08:53, Gerd Petermann wrote: >

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

Steve, Why didn't you use the new option? Gerd Von: mkgmap-dev im Auftrag von Steve Sgalowski Gesendet: Samstag, 26. März 2016 11:18 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split thi

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

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 mailto:gpetermann_muenc...@hotmail.com>> wrote: Steve, Why didn't you

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

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 sea

Re: [mkgmap-dev] Problem with splitter: Failed to find a correct split

it be that the process is "unhappy" with two or more commits within a short time ? Gerd Von: mkgmap-dev im Auftrag von Steve Ratcliffe Gesendet: Samstag, 26. März 2016 10:17 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Problem with

Re: [mkgmap-dev] Problem with splitter r412: invalid bbox area in pbf file

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. I'l

Re: [mkgmap-dev] Problem with splitter r412: invalid bbox area in pbf file

min/max values 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

Re: [mkgmap-dev] Problem with splitter r412: invalid bbox area in pbf file

ct 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 > file throwing t

Re: [mkgmap-dev] Problem with splitter r412: invalid bbox area in pbf file

d > 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 &