December 2024 - mkgmap-dev - The mkgmap lists

Update on missing POI Labels on some devices and some questions...
by scott taggart 05 Feb '25

05 Feb '25

* As I posted here <https://www.mkgmap.org.uk/pipermail/mkgmap-dev/2024q4/034350.html>on 2024.12.01, I was having issues with POIs not displaying labels for some garmin devices (specifically the XT2 and Tread) when generating /img files using mp file input to mkgmap. I did some exploration and discovered this (maybe well known but not by me): ** * Each device model displays POIs differently (i.e., type 0x100 does not show the same thing). There seems to be no consistency across models (Felix echoed this in a follow-up post). * Each model displays labels for each POI type differently (some show no label, others show small vs big text). There seems to be no consistency across models. * I attempted to use the custom "[_point]" feature of the mp files and mkgmap but the custom point bitmaps only work for some garmins. Even then, it didn't help with my missing [poi] labels. * Prior to the labels not working on the XT2 and Tread units, I always used the 0x1400 POI code type for my labels. With a lot of cross-model experimentation I discovered a single POI code (0x1E00) will display large text on all garmin models I was able to test with (Montana 6XX and 7XX, XT, XT2, Tread). I have no idea if this POI code will work with all garmins that support custom maps. Questions: * Are these issues with each model behaving differently with respect to POI types well-known? If so, how are they gotten around by (OSM) map builders? How can a single map be built that has POIs and labels that are consistent across more than one device. What am I missing? * How does OSM handle this? I presume that an OSM map generated for an area works on all garmin devices? I will admit that I don't know what the OSM map limitations are across garmin models. Does the JOSN model allow the devices POI maps to be loaded on a per-map basis? If I were to switch to JOSN model for mkgmap input, could I get around all the device limitations I am running into with the mp file format? Can someone recommend a good tutorial on getting up to speed on generating JOSN for simple map input to mkgmap? * OSM uses the JOSM model to feed mkgmap. Does that model allow for more flexibility and control than the "mp" input file model? I presume the MP file format is obsolete. * Is there any better documentation for the MPO format than the CGPSMAPPER pdf file floating around on the internet? * Can anyone recommend either a different website or people whom I may contact for further help with any of this? Any and all help is appreciated. *

6 17

Re: [mkgmap-dev] Internal Error Failed to render Multipolygon
by Ticker Berkin 24 Dec '24

24 Dec '24

Hi Thomas I've just loaded the relation 1754729 with JOSM. JOSM validation reports no errors, but mkgmap (direct, no splitting) gives errors: WARN: uk.me.parabola.imgfmt.app.Area lakeLadoga.osm: Area.split 2852864 1400832 2854912 1402880 res 11 can't 2 1 WARN: uk.me.parabola.mkgmap.reader.osm.MultiPolygonRelation lakeLadoga.osm: Multipolygon http://www.openstreetmap.org/relation/1754729 [ele=4.84, int_name=Ladoga lake, name:en=Lake Ladoga, name=Ладожское озеро, natural=water, type=multipolygon, water=lake] contains errors. WARN: uk.me.parabola.mkgmap.reader.osm.MultiPolygonRelation lakeLadoga.osm: Polygon 4611686018427403156(4P)(259078070[118P]) carries role inner but is not inside any other polygon. Potentially it does not belong to this multipolygon The area.split WARN happens when there are too many object (points/lines/polygons) in 1 resolution unit. The other error is as described. I notice that this relation was edited a couple of days ago so maybe someone is fixing or creating problems. I'll try again in a few days and investigate more deeply. Regards Ticker On Mon, 2024-09-02 at 19:44 +0200, Thomas Morgenstern wrote: > Hi Ticker, I found : osmium-tool and splitter works proper. I can the > splitted <12345678>.osm.pbf open and render in JOSM. JOSM shows the part of > the multipolygon 1754729, which is inside the boundary of the polygonfile for > splitter. I assume, mkgmap has the problem. But sorry, I am not a good > programmer and can not do deeper investigation or find a solution. If you > interested, I can give you my polygon and the <maptile-number>.osm.pbf. > > Thomas > > > Am 02.09.2024 um 15:04 schrieb Ticker Berkin: > > > > > > Hi Thomas > > > > I get similar problems just using > > > > https://download.geofabrik.de/europe/britain-and-ireland.html > > > > directly. The relations that cause the problem are not within the above > > combined > > territories but excluding them would required a much more complicated shape > > to > > define the download area. > > > > Ticker > > > > On Mon, 2024-09-02 at 12:42 +0200, Thomas Morgenstern wrote: > > > > > > > > Hi Ticker, i made further investigation. You are right.: the > > > MultiPolygonRelation 1754729 ('Ladoga sea') was cut by ectract Scandinavia > > > from europe-latest.osm.pbf using osmium-tool . > > > I am not sure, but means this, that osmium can not write a proper > > > ectract, > > > if such Relation must bee split ? > > > This means also, osmium has a bug ? I must check my osmium version... > > > regards Thomas > > > > > > > > > Am 02.09.2024 um 10:30 schrieb Ticker Berkin: > > > > > > > > > > > > > > > > > > > > > Hi Thomas > > > > > > > > It isn't related to AngleChecker. > > > > > > > > I notice that both these relations have been changed in the last couple > > > > of > > > > days > > > > so maybe they were faulty. > > > > > > > > The large one is on the boarder with Scandinavia and it is likely that > > > > the > > > > map > > > > extraction download only had part of it and this gives rise to this type > > > > of > > > > error. > > > > > > > > Regards > > > > Ticker > > > > > > > > On Mon, 2024-09-02 at 09:43 +0200, Thomas Morgenstern wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello , I use mkgmap-4921 with patch from Ticker Berkin - > > > > > Angelchecker-V6. > > > > > With that i get in Scandinavia following error : Internal Error Failed > > > > > to > > > > > render MultiPolygonRelation 1754729 and 304507. Rel. 1754729 is > > > > > 'Ladoga'- > > > > > sea > > > > > with 5 226 Elements. Rel. 304507 is Multipolygon=water, 171 Elements. > > > > > I assume the error ist not specific to the patch...and more common.. > > > > > How to avoid this ? > > > > > > > > > > regards Thomas > > > > > > > > > > _______________________________________________ > > > > > mkgmap-dev mailing list > > > > > mkgmap-dev(a)lists.mkgmap.org.uk > > > > > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > mkgmap-dev mailing list > > > > mkgmap-dev(a)lists.mkgmap.org.uk > > > > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > > > > > > > > > > > > > > > > > > > > > > > > > > > >

2 7

Error or feature?
by Gerd Petermann 23 Dec '24

23 Dec '24

Hi all, this discussion in the German forum https://community.openstreetmap.org/t/mkgmap-extra-pois-definieren/122931 brought up an issue with mkgmap and the --nsis option. With the command java -jar mkgmap.jar --nsis --output-dir=map examples\typ-files\mapnik.txt somedata.osm the *.typ file is copied into the output directory ./map as expected while the this sequence which compiles the typ file first java -jar mkgmap.jar examples\typ-files\mapnik.txt java -jar mkgmap.jar --nsis --output-dir=map mapnik.typ somedata.osm doesn't copy the *.typ file to the output directiory ./map but the *.nsi file expects it there. Does anybody remember if there is a good reason for this different behaviour? For me it looks plain wrong. Gerd

1 1

Problem in AngleFixer?
by Gerd Petermann 15 Dec '24

15 Dec '24

Hi all, in a private email Thorsten Kukuk contacted me about wrong turn instructions a sharp angles. An example is the node https://www.osm.org/node/27550903 A route coming from South that follows the way https://www.osm.org/way/36138336 at this junction should NOT produce a turn instruction. A route that turns left SHOULD produce a turn instruction. With current mkgmap it's vice versa and thus not OK. I thnk the current code in AngleFixer.java is too agressive as it tries to enlarge the angles so that a compact format can be used to write the heading values of the arcs at the mentioned node. It does this by changing the heading values of both arcs with go to the north. @Ticker: The code was introduced with your arcHeading_v2.patch, but maybe it existed before. Can you explain why the constant AngleChecker.SHARP_DEGREES is set to 46° instead of maybe 22.5° ? Gerd

3 37

Address index incomplete
by Alessio Medici 05 Dec '24

05 Dec '24

Hi, I am trying to create maps with address index, but it seems the index contains only a few (something like 10) cities. >From geofabrik.de I have downloaded the .osm.pbf file for Europe than I have run splitter and mkgmap using the following command lines: java -jar "/home/Alessio/bin/splitter/splitter.jar" \ --description="Italia" \ --output-dir=. \ --geonames-file="../Italia.txt" \ --wanted-admin-level="11" \ --mapid="13900000" \ --max-nodes="5000000" \ --polygon-file="../Italia.poly" \ "/home/Alessio/GarminMapsCreation/planetfile/europe-latest.osm.pbf" java -jar "/home/Alessio/bin/mkgmap/mkgmap.jar" \ -Dlog.config=logging.properties \ --max-jobs \ --gmapsupp \ --output-dir="gmapsupp" \ --country-name="Italia" \ --family-name="Italia" \ --family-id="42" \ --area-name="Italia" \ --description="Italia" \ --series-name="OSM generic routable(Italia_20240728)" \ --product-id="42" \ --mapname="13900000" \ --country-abbr="" \ --draw-priority="26" \ --precomp-sea=../../sea-latest.zip \ --generate-sea \ --route \ --drive-on=detect,right \ --report-roundabout-issues \ --fix-roundabout-direction \ --process-destination \ --process-exits \ --name-tag-list=int_name,name \ --remove-ovm-work-files=true \ --bounds=../../bounds-latest.zip \ --verbose \ --location-autofill=is_in,nearest \ --make-poi-index \ --index \ --split-name-index \ --housenumbers \ --preserve-element-order \ --dem="/home/Alessio/GarminMapsCreation/hgt" \ --style-file=../../default_style \ --keep-going \ --improve-overview \ --min-size-polygon=15 \ -c "gmapsupp/template.args" The java version I use is: java 23 2024-09-17 Java(TM) SE Runtime Environment (build 23+37-2369) Java HotSpot(TM) 64-Bit Server VM (build 23+37-2369, mixed mode, sharing) on Ubuntu 24.04 The map is OK and I can use it for routing, but I have to choose manually the start and end point directly on the map. Can someone point me out where I am wrong? Thank you very much Alessio

2 2

Re: [mkgmap-dev] Problem with newer garmin device text labels not appearing
by scott taggart 03 Dec '24

03 Dec '24

Hi Felix, Thanks for the response. I am just getting started on my debugging and, in fact, one of the things I was going to try was changing the POI "types". I will let you know how it goes. Regarding line "types", I generate custom line types and supply the line pattern as opposed to using any of the well-known types. Maybe this could be a work-around for you? I could supply examples for you, if needed. The whole visibility of objects at different zoom levels has always been a challenge and is very device dependent, unfortunately. For what I do, I generally don't run into it too much (because I don't generate references to device-internal icons, etc.). As a whole, Garmin's UI and compatibility between devices is terrible and unfortunate. I think it stems for poor design decisions, limited memory, etc. I've worked at software companies for 4 decades (as a developer) and I've seen this kind of sloppy design and poor management. It is what it is and someday the phones will eclipse all this poor hardware and software. I saw you registered at my website. Please watch the (poor and outdated) videos and try it out. Let me know if you need any help and I am always willing to share all that I have. Oh, I just received a Tread and it also does not display the text for a "POI" type. I will start debugging now... Best of luck on your project. Scott

1 0

Problem with newer garmin device text labels not appearing
by scott taggart 02 Dec '24

02 Dec '24

Hello, Please forgive any missing information and clarity - my first post here. I have a (free, primitive) website ("TrickTracks <https://mapmaker.tricktracks.org/server/trick_tracks/file_uploader.php>") that allows users to "drop" a gpx file onto a webpage and receive a garmin .img map file as a download. Under the covers my My web server converts the gpx file to an MP file and then feeds mkgmap (currently r4000) to produce the .img file. I've had this website live for about 5 years and it's been well received by my users. The users are primarily motorcycle and bicycle riders who create tracks for their rides and use the maps on their various Garmin devices. My software does a bit of "special" processing on the gpx files in that certain waypoints are converted to large polygon targets and the gpx track lines have mileage marker polygons added at the user requested intervals. There are various web-page configuration options, etc. that let users specify map line width, etc. This has worked well on almost all garmin devices for many years. I now have a problem with some of the newer garmin devices (XT2 and Treads) where the labels for the polygons are not showing up. I'm looking for ideas on where to start with this issue. I have a few ideas and would like ideas on how to proceed: * First, is this a know problem in this community? Have the mkgmap/OSM developers already tackled this issues and has mkgmap been changed in some way to deal with it? I will admit I have not upgrade my server yet to the latest mkgmap. * I am assuming garmin changed something in their rendering software to now show labels that used to work (I suppose that's obvious). I have tried to see if there was a device setting that affected this but have not been able to find any that work. * Is there some limitation with using MP file input to mkgmap that will, in the future, hinder generating .img file for these newer devices. I do not generate and JOSM and have not researched that as it seems like overkill for my application. * Is there perhaps something in my TYP input to mkgmap that could cause this (I self generate TYP files on the fly but they have worked for years and still do on the XT, Montana, etc.). * As a side-note, the labels on my MP polylines do display correctly. * I can provide the MP file contents I am generating for the failing waypoint labels if that would help. Thanks you for any input and help you can give me. Scott

2 1