[mkgmap-dev] last release

the last release is not yet uploaded on the site 3673 dated 23 march Stephen This email has been sent from a virus-free computer protected by Avast. www.avast.com

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

Re: [mkgmap-dev] osm combiner error

I have run with java 8 without problem until now. However, I'm running a windows 10 machine, not a mac. Alexandre 2016-03-24 5:05 GMT-03:00 Gerd Petermann : > Hi Paco, > > we compile with Java 1.7 but you can (and probably should) use the 1.8 JRE > to run it. >

Re: [mkgmap-dev] osm combiner error

Hi Paco, we compile with Java 1.7 but you can (and probably should) use the 1.8 JRE to run it. @Steve: Do you have an idea when we should move the build to 1.8 ? Gerd Von: mkgmap-dev im Auftrag von

Re: [mkgmap-dev] osm combiner error

Hi all, By the way, are splitter/mkgmap compatible with java8 now ? Thanks, Paco - Mail original - De: "Steve Ratcliffe" À: "Development list for mkgmap" Envoyé: Mardi 22 Mars 2016 17:14:45 Objet: Re: [mkgmap-dev] osm combiner