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=mkgm
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\8011.mp: internal
error? The nodeCount doesn't match value calculated by RoadNetWork:
(htt
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
RoadNet
@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 not
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,
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
leve
