[mkgmap-dev] maps overlaying each other

Sat Dec 26 15:57:40 GMT 2020

Hi.

With a bit of time, i gave it a try to use a polygon file, but the splitter is 
complaining when i add the polygon-file option.

I took to small countries, Estonia and Latvia, made a polygon file called 
foskan_ee_lv.osm.

Map data for the two countries was downloaded from geofabrik, combined with 
osmconvert into the file ee_lv.o5m.

Splitter command:
java -Xmx2000m -jar ${SPLITTER}  --polygon-file=./foskan_ee_lv.osm --output-
dir=ee_lv/splitted/ --max-nodes=250000 --no-trim kartdata/ee_lv.o5m

Almost directly the following java error is thrown:

Elapsed time: 0s   Memory: Current 59MB (4MB used, 55MB free) Max 1778MB
Time started: Sat Dec 26 16:44:09 CET 2020
org.openstreetmap.osmosis.core.OsmosisRuntimeException: Unable to parse <node 
into a double precision number.
        at 
org.openstreetmap.osmosis.core.filter.common.PolygonFileReader.parseCoordinates(PolygonFileReader.java:
294)
        at 
org.openstreetmap.osmosis.core.filter.common.PolygonFileReader.loadSectionPolygon(PolygonFileReader.java:
240)
        at 
org.openstreetmap.osmosis.core.filter.common.PolygonFileReader.loadPolygon(PolygonFileReader.java:
180)
        at 
uk.me.parabola.splitter.solver.AreasCalculator.readPolygonFile(AreasCalculator.java:
115)
        at 
uk.me.parabola.splitter.solver.AreasCalculator.<init>(AreasCalculator.java:52)
        at uk.me.parabola.splitter.Main.split(Main.java:216)
        at uk.me.parabola.splitter.Main.start(Main.java:121)
        at uk.me.parabola.splitter.Main.main(Main.java:81)

This error is also thrown with the example file which you were kind to provide 
a few weeks ago. The two polygon files (mine and example) both look identical 
in structure, the content is of course different.
Changing the decimal points to decimal comma inside the polygon file did not 
help.

if i remove the --polygon-file parameter it works normally.

What could be the issue?

Regards
Karl

On söndag 6 december 2020 kl. 14:22:38 CET Gerd Petermann wrote:
> Hi Karl,
> 
> attached is an old example file for the polygon-desc-file option. It builds
> two gmapsupp, one for Germany, one for the alps. A large part is shared.
> With europe.osm.pbf as input splitter writes extra files
> Germany-template.args and alps-template.args, each containing the arguments
> to calculate the tiles for the wanted area. Splitter writes each tile only
> once, but mkgmap will compute different tiles for them. I suggest to play
> with different variants, but only a small area and a small max-nodes, maybe
> 100.000.  Once you know what works best you can use real values.
> 
> Gerd
> 
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Gerd
> Petermann <gpetermann_muenchen at hotmail.com> Gesendet: Sonntag, 6. Dezember
> 2020 13:46
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] maps overlaying each other
> 
> Hi Karl,
> 
> I use splitter option --write-kml to produce a kml file which can load in
> JOSM (with the opendata plugin) or in Google Earth. The option
> --polygon-desc-file was added to splitter to help with overlapping
> gmapsupp. You can draw multiple OSM ways which may overlap, each with a
> name for the covererd area, and splitter produces template.args files for
> each named polygon. IIRC the tricky part is to set the OSM points on the
> correct garmin raster. Didn't do it for quite a while, but it worked with
> Europe or even planet.
> 
> Gerd
> 
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von 7770
> <7770 at foskan.eu> Gesendet: Sonntag, 6. Dezember 2020 13:33
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] maps overlaying each other
> 
> Hi Gerd and Michael.
> Yes, i should have been clearer.
> I do combine countries and have maps around 4GB each. I often disable one
> map, but sometimes this is not convenient. Such as when driving over a
> border or hiking in a border area, one usually wants to see both sides.
> 
> Anyhow i will try to generate the tiles differently.
> If i use splitter for a larger area to make sure i get one tile only for one
> area, but do not have a tool to see which tiles are crossing the borders
> (which can be many for long borders), what is the best way to know which
> tiles should go into both maps?
> 
> Regards
> Karl
> 
> On söndag 6 december 2020 kl. 12:32:03 CET Gerd Petermann wrote:
> > Hi Karl,
> > 
> > I prefer to merge the country data first and use one splitter run to
> > produce the tiles and one gmapsupp for all, but you can also produce
> > mutliple gmapsupp where some tiles appear in both, just make sure that
> > those tiles are really the same. So, computing the *.img files once and
> > combining them in different gmapsupp should work.
> > 
> > Gerd
> > 
> > ________________________________________
> > Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von
> > 7770 <7770 at foskan.eu> Gesendet: Sonntag, 6. Dezember 2020 11:42
> > An: mkgmap-dev at lists.mkgmap.org.uk
> > Betreff: [mkgmap-dev] maps overlaying each other
> > 
> > Hi.
> > How can i avoid that a section of a map (in a gmapsuppA.img) overlays some
> > neighbouring map (in a different gmapsuppB.img) making it inaccessible on
> > the GPS unit?
> > 
> > Example,
> > say i have Sweden and Norway, neighbouring countries. Data is downloaded
> > from goefabrik per country. Splitting and generating map done per country.
> > Sweden gets --draw-priority=50 and Norway gets 51.
> > In the border areas, when the tiles are a bit outside of the country, the
> > Norwegian map overlays the Swedish, details from both maps are visible but
> > one cannot click on a point on the Swedish (lower) map because the empty
> > Norwegian map is drawn above.
> > 
> > --transparent option is not used to avoid other non-wanted transparency.
> > --bounds is used.
> > --add-boundary-nodes-at-admin-boundaries is used.
> > 
> > 
> > Is there some good way to avoid this issue, to make sure that details from
> > the lower map can be accessed? Perhaps make the splitter more strict on
> > the
> > borders?
> > 
> > 
> > regards
> > Karl
> > 
> > 
> > 
> > _______________________________________________
> > mkgmap-dev mailing list
> > mkgmap-dev at lists.mkgmap.org.uk
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> > _______________________________________________
> > mkgmap-dev mailing list
> > mkgmap-dev at lists.mkgmap.org.uk
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> 
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev