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

Gerd, I found the built version and tested it against the same testfile I had problems with a few days ago. All the problemcases I had (building Alaska without contour data, building with contour data) run through without any problems and the built map of Alaska looks so far ok. I'll do

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

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

Well, the difference is small, but I have no idea what problem you had in the first place, as the split worked fine in both cases. Gerd Von: mkgmap-dev im Auftrag von Steve Sgalowski

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:

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

trying r437 now will advise gerd Stephen g Australia This email has been sent from a virus-free computer protected by Avast. www.avast.com <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Mar 26,

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

Hi Steve, could 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

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

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:

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

Many thanks, Gerd. If there is a compiled Version, i can test it this evening Patrik Am 26.03.2016 8:38 vorm. schrieb Gerd Petermann : Hi all, I tried to find out why splitter uses the bounding box provided in the file. The feature was added

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

Hi all, 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."

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 regarding the 'source' of the problem: according to GeoFabrik the wrong bounds tag seems to be caused by osmium-history-splitter used to split the world file. Cheers Patrik On 25.03.2016 11:00, Gerd

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

Hi Patrik, reg. performance for option 3: I don't expect any extra costs for this, splitter already collects all the data and applies the bbox after that. So, it always creates a (virtual) grid for the whole planet. With normal resolutions this never was a bottle neck. reg. implementation:

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 --polygon-files with Luxembourge (small enough to do quick tests), the result is not that much different if I'm skipping

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

I have the same problem , with splitter for australia , or australia-oceania even when i have search limit at 60,000 or 90,000 or in between these Figures I stil get the same response in splitter log file . Stephen On Fri, Mar 25, 2016 at 4:33 PM, Gerd Petermann <

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

Hi Patrik, good question. I also wondered if splitter can be changed to ignore wrong bounds tags. My thoughts: In your case the bbox is far too large, means it claims to contain data that is not there. The normal case is vice versa: The file contains some nodes outside of the bbox, maybe

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: * original osm.pbf file downloaded from geofabrik (with the problematic bounds tag in it) -> FAILURE * converted with the help of

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

Gerd, I did dig a bit deeper... also as it rang a bell: we had quite a similar problem with the wrong bounding box in Alaska already October 2014. It was an illegal value of maxlon="180.0005" causing splitter to bail out When I convert the osm.pbf file with the help of osmconvert to osm and

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

Gerd, I'll play a bit more with this option and check what suits me best. Again thanks for the incredibly quick answer to my problem/question. Cheers Patrik On 24.03.2016 22:20, Gerd Petermann wrote: Hi Patrik, I think the wanted effect of the no-trim option is a rectangular map, which

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

Hi Patrik, I think the wanted effect of the no-trim option is a rectangular map, which some people prefer, esp. on the PC. Gerd Von: mkgmap-dev im Auftrag von KeenOnKites Gesendet: Donnerstag,

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 --no-trim for all map building or if I would suddenly run into other/new problems...

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

Hi Patrik, I don't need the files, I downloaded the alaska file and tried some variants. See also my last post, send a few minutes ago. Gerd Von: mkgmap-dev im Auftrag von Patrik Brunner

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 documentation, anyway would disable --no-trim option. Do you still need the resulting densities-out of

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

Hi Patrik, yes, the problem is the wrong bounding box in the downloaded file. I don't know why it says that it spans to 180, because there is no node between -129 and 180. Because of that and the option --no-trim splitter would have to write huge empty tiles, that's why it stops. I think

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 bounding box spans from -180 to 180, but this box is most empty. I have to run splitter now to find the details. It works without --no-trim, probably also with an appropriate polygon file. Does

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