Re: [mkgmap-dev] Move to Java 1.8

2016-07-31 Thread Gerd Petermann
Hi Uli, do you have an example for me? Gerd Von: mkgmap-dev im Auftrag von UliBaer Gesendet: Sonntag, 31. Juli 2016 22:10:56 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Move to Java

Re: [mkgmap-dev] Move to Java 1.8

2016-07-31 Thread Gerd Petermann
Hi Steve, I think there is no reason to wait, so go ahead. Not sure what to do with the libraries, I noticed that fastutil was changed heavily, so I'd first try to find out if those changes have a positive impact or not. Gerd Von: mkgmap-dev

Re: [mkgmap-dev] Re-using a splitter result

2016-07-31 Thread Andrzej Popowski
Hi Bernhard, I use simple awk script to renumber template.args. Something like: { if ($1 == "mapname:") { print $1 " " $2 + 2048 } else { print $0 } } -- Best regards, Andrzej ___ mkgmap-dev mailing list

Re: [mkgmap-dev] Move to Java 1.8

2016-07-31 Thread Steve Ratcliffe
Hi Gerd @Steve : I think we don't need a warning message for users with an older JRE, but I don't know if you need time to change the build environment? Can change whenever you want. It is already built and tested on jdk8 (and openjdk8), just need to change the default over and then remove

Re: [mkgmap-dev] Move to Java 1.8

2016-07-31 Thread Sebastiaan Couwenberg
On 07/31/2016 10:13 PM, Felix Hartmann wrote: > I think most users switched a long time ago... All except Linux users where distributions have not switched the default to Java 8 yet, as can be seen in the JOSM statistics. Debian stable still has JDK 7 as default, but has JDK 8 available in

Re: [mkgmap-dev] Move to Java 1.8

2016-07-31 Thread Felix Hartmann
I think most users switched a long time ago... On 31 July 2016 at 22:10, UliBaer wrote: > I already use Java 8 nearly since the beginning and have checked out the > workspace for splitter and mkgmap into eclipse Neon without problems. My > local project is modified to produce

Re: [mkgmap-dev] Re-using a splitter result

2016-07-31 Thread Carlos Dávila
El 31/07/16 a las 21:43, Bernhard Hiller escribió: From one data extract (comprising Germany, Austria, Switzerland, Czechia, Belgium, Netherlands), I create 3 maps: - a routable map for car with id 4312 - a routable map for bicycle with id 4311 - a shared map with points of interest, areas, and

Re: [mkgmap-dev] Move to Java 1.8

2016-07-31 Thread UliBaer
I already use Java 8 nearly since the beginning and have checked out the workspace for splitter and mkgmap into eclipse Neon without problems. My local project is modified to produce Java 8 output. With this change it would be possible to replace a lot of list operations with the new streaming

Re: [mkgmap-dev] Re-using a splitter result

2016-07-31 Thread Gerd Petermann
Sure, splitter creates a file template.args which contains a map name and a file name for each OSM input file. All you have to do it to write a small script to create three versions of this file. Another option could be to use --polygon-desc-file: --polygon-desc-file An osm file (.o5m,

[mkgmap-dev] Re-using a splitter result

2016-07-31 Thread Bernhard Hiller
From one data extract (comprising Germany, Austria, Switzerland, Czechia, Belgium, Netherlands), I create 3 maps: - a routable map for car with id 4312 - a routable map for bicycle with id 4311 - a shared map with points of interest, areas, and some lines (river, railway, etc) with id 4310 Due

Re: [mkgmap-dev] Move to Java 1.8

2016-07-31 Thread Sebastiaan Couwenberg
On 07/31/2016 07:03 PM, Gerd Petermann wrote: > JOSM already requires 1.8. JOSM is not entirely there yet. The next JOSM tested snapshot will be the first to require Java 8, the current tested snapshot still uses Java 7. https://josm.openstreetmap.de/ticket/11390 Kind Regards, Bas -- GPG

[mkgmap-dev] Move to Java 1.8

2016-07-31 Thread Gerd Petermann
Hi all, Java 1.7 is no longer maintained, so I guess that most users are already using Java 1.8 I'd like to change the build of splitter and mkgmap to use 1.8 instead of 1.7 soon, JOSM already requires 1.8. I needed a newer ant version, 1.8.4 did not work with JDK 1.8, but 1.9.7 seems to

Re: [mkgmap-dev] Option to output polygons in size order

2016-07-31 Thread Gary Bamford
Hi Ticker, Garmins approach to maps is layered, OSM is built on relationships, both have their flaws, and converting from relationships to layers is problematic at best. Point me to an area you are having problems with and i will check it out to see what my set up shows, Regards Gary

Re: [mkgmap-dev] Option to output polygons in size order

2016-07-31 Thread Ticker Berkin
Hi Gary For my problem areas I'll look at the OSM relationships in exact detail - I'm only just working out how to do this. Judging by how OpenStreetMap.org displays an area with overlapping polygons not in a relationship, it is making a consistent choice about how to show them. I haven't been

Re: [mkgmap-dev] Option to output polygons in size order

2016-07-31 Thread Thorsten Kukuk
On Sun, Jul 31, Gerd Petermann wrote: > The only other input file is the bounds file. I cannot think of a good reason > why that would > change the result unless it is somehow corrupted. The coastlines where several times broken in the last weeks and I saw a flooding of europe. Somebody was so