Commit r4271: improve reader for polish (*.mp) format
Version mkgmap-r4271 was committed by gerd on Mon, 11 Feb 2019 improve reader for polish (*.mp) format - fix restriction handling (various errors, esp. NPE and "can't locate arc from 'via' node..." error messages - make sure that route nodes are only calculated for POLYLINE nodes given for level 0 TODO: SIGN section (exit hints) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4271
Hi Gerd, I have complied a big map from mp sources (about 3.8GB in 50 files) in one go. Map is usable, routable, with index search and DEM. It is quite impressive, thanks! The problems I have noticed: - Overview map is not accepted by Mapsource and Basecamp. It looks ok, but it includes NET, NOD and DEM. Maybe empty NET/NOD is a problem? - I can't control parameters defining house number after street name or zip code before city name. I guess mkgmap takes them form some config file, which is not used for mp sources. - Value of mapid is taken form file name instead of mp source. - There seems to be 2 sets of city/region/country names in search index. In my sources country is named "POLSKA TOPO~[0x1d]PL" and some results from address search contain this name, while others use simply "PL". I don't use "bounds" option, I can't guess from where comes country "PL". In my mp sources, city/region/country appears in 2 places. Once as statements CitName, RegionName, CountryName, second as a part of Numbers# statement. Maybe there is different processing for them? - ~[0x1d] is a special character, indicating country/region abbreviation. See cgpsmapper manual paragraph 4.2.2.1. Mkgmap doesn't process this code in country name. My guess is that any value inside "~[]" could be simply inserted into label as a hex value. - For search results with country name from my sources, national characters are wrong. Maybe mkgmap assume that mp source is in Unicode? Cgpsmapper doesn't support Unicode, my mp sources are in code page 1250. -- Best regards, Andrzej
Hi Andrzej, thanks for testing. I've also noticed that some settings in the mp file are ignored. I'll try to fix that. No idea about the overview map. Is that created from an mp file or is it computed by mkgmap from ovm_* ? The setting Preview in [IMG ID] section is ignored, as are many others. I don't know if that is intended. I think the String PL comes from the LocatorConfig.xml, but I'll verify that tomorrow. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Andrzej Popowski <popej@poczta.onet.pl> Gesendet: Montag, 11. Februar 2019 17:43 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Commit r4271: improve reader for polish (*.mp) format Hi Gerd, I have complied a big map from mp sources (about 3.8GB in 50 files) in one go. Map is usable, routable, with index search and DEM. It is quite impressive, thanks! The problems I have noticed: - Overview map is not accepted by Mapsource and Basecamp. It looks ok, but it includes NET, NOD and DEM. Maybe empty NET/NOD is a problem? - I can't control parameters defining house number after street name or zip code before city name. I guess mkgmap takes them form some config file, which is not used for mp sources. - Value of mapid is taken form file name instead of mp source. - There seems to be 2 sets of city/region/country names in search index. In my sources country is named "POLSKA TOPO~[0x1d]PL" and some results from address search contain this name, while others use simply "PL". I don't use "bounds" option, I can't guess from where comes country "PL". In my mp sources, city/region/country appears in 2 places. Once as statements CitName, RegionName, CountryName, second as a part of Numbers# statement. Maybe there is different processing for them? - ~[0x1d] is a special character, indicating country/region abbreviation. See cgpsmapper manual paragraph 4.2.2.1. Mkgmap doesn't process this code in country name. My guess is that any value inside "~[]" could be simply inserted into label as a hex value. - For search results with country name from my sources, national characters are wrong. Maybe mkgmap assume that mp source is in Unicode? Cgpsmapper doesn't support Unicode, my mp sources are in code page 1250. -- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, overview is my fault. I have used wrong options. I set 3 layers of DEM, while overview map has only 1 layer of data. That kind of setup is not supported by Garmin. I have corrected it and now overview map is OK. I got 2 errors "The nodeCount doesn't match value calculated by RoadNetWork", which I have to check yet. There is something wrong with displaying map in Mapsource. Some colours are wrong and sometimes Mapsource doesn't redraw map properly. And I have found a missing polygon. -- Best regards, Andrzej
Hi Gerd, I have extracted objects, that are problematic on my map, see attached file. Both roads trigger error messages, when I compile my whole map: SEVERE (RoadDef): D:\Emapa\Popej\_Topo-360\zrodla\00008011.mp: internal error? The nodeCount doesn't match value calculated by RoadNetWork: (http://www.openstreetmap.org/browse/way/326440) SEVERE (RoadDef): D:\Emapa\Popej\_Topo-360\zrodla\00008042.mp: internal error? The nodeCount doesn't match value calculated by RoadNetWork: (http://www.openstreetmap.org/browse/way/986610) There are no errors, when compiling this extract. Maybe there is interaction with other roads? Single polygon is not compiled correctly. Compared to GPSMapEdit and map compiled by cGPSmapper, some parts of polygon are missing. I think polygon processing should be exactly like for ESRI shape file. Values of DATA are direct equivalent of rings in SHP. This is what I have found, when preparing conversion form SHP to mp. If I put all rings from SHP to mp objects, then cGPSmapper can deal with them correctly. According to ESRI Shapefile Technical Description, a polygon can contain multiple outer rings and inner rings. Difference between outer and inner is drawing direction. Vertices for outer ring are ordered clockwise, while holes are ordered counterclockwize. When following a border, interior of a polygon is always to the right side. See page 8 of Description: https://www.esri.com/library/whitepapers/pdfs/shapefile.pdf -- Best regards, Andrzej
popej wrote
- I can't control parameters defining house number after street name or zip code before city name. I guess mkgmap takes them form some config file, which is not used for mp sources.
Data is now taken from *.mp source See http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4275 popej wrote
- Value of mapid is taken form file name instead of mp source. I guess I should evaluate this line instead? ID=9940015
I hope the labels work besser now, I did not test it very much. Gerd -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
participants (3)
-
Andrzej Popowski -
Gerd Petermann -
svn commit