[mkgmap-dev] How to track an error in OSM data ? (and style's behavior, error) (David)
From David david.tlp at orange.fr on Mon Aug 1 18:20:51 BST 2011
To Chris and Wanmill, I know the need to add "continue" rule to apply the next filter on data. But the fact is it does not seem to work as expected at least with "landuse=forest" and "natural=wood" with Ireland PBF file (splitted with splitter r2009 and compiled with mkgmap r2009). I do not have any clue, only a temporary solution. But the biggest trouble is still the corrupted map generated for Northern Ireland around Belfast with a huge commercial area polygon displayed in levels 0 and 1. Basecamp can display the map without any problem at all zoom and detail levels. My first idea was an error in OSM file, but I cannot find bad data. It looks like a bad result with early generate-sea option development (at least one year ago). Regards, David Le 01/08/2011 13:00, mkgmap-dev-request at lists.mkgmap.org.uk a écrit : > Am 31.07.2011 12:32, schrieb WanMil: > >>> >> I also found an error in a style file for forest polygons. You have to >>> >> write the rules like this if you want the result expected : >>> >> >>> >> landuse=forest& wood=coniferous [0x54 resolution 18] >>> >> landuse=forest& wood=decideous [0x50 resolution 18] >>> >> landuse=forest& wood=mixed [0x55 resolution 18] >>> >> landuse=forest& wood !=* [0x50 resolution 18] /*this line is applied if >>> >> no data matches the ones above*/ >>> >> >>> >> and not like that : >>> >> >>> >> landuse=forest& wood=coniferous [0x54 resolution 18] >>> >> landuse=forest& wood=decideous [0x50 resolution 18] >>> >> landuse=forest& wood=mixed [0x55 resolution 18] >>> >> landuse=forest [0x50 resolution 18]/*this line overrides the ones above*/ >> > As far as I know all rules after the first >> > matching line with a garmin id are skipped unless you add a continue >> > statement. So the default style should be correct. > Yes. mkgmap stops at the first matching rule. > > Exeptions: > > Action rules ( example : maxspeed=DE:urban {set maxspeed=50} ) > and the continue-statement: > > barrier=fence [0x34 resolution 24 continue] > > Chris > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20110801/ab2ce13c/attachment.html
- Previous message: [mkgmap-dev] How to track an error in OSM data ? (and style's behavior error)
- Next message: [mkgmap-dev] How to track an error in OSM data ? (and style's behavior, error) (David)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list