February 2011 - mkgmap-dev - The mkgmap lists

[TeamCity, FAILED TO START] Build display::trunk #305
by teamcity＠mkgmap.org.uk 06 Feb '11

06 Feb '11

Build display::trunk #305 failed to start ([Failure] Artifacts resolving failed). Agent: Iocaste Build results: http://teamcity.mkgmap.org.uk/viewLog.html?buildId=3266&buildTypeId=bt11 Changes included (1 change) ==================================================== Change (personal build) by steve (8 files): New MdrCheck program to verify that the links are correct and consistent with the input files. A work in progress. see more information about changed files: http://teamcity.mkgmap.org.uk/viewLog.html?tab=buildChangesDiv&buildId=3266… ============================================================================ Configure email notifications: http://teamcity.mkgmap.org.uk/profile.html?init=1&tab=userNotifications

1 0

Changing styles and TYP integrating
by Valeriy Pekarskyy 06 Feb '11

06 Feb '11

Hi All, I have several suggestions to default style, is there possibility to add these to mkgmap style? points: remove "amenity=toilets [0x4e00 resolution 21 default_name 'Toilets' ]" add "amenity=toilets [0x2f0c resolution 22 default_name 'Toilets' ]" Because of that 4e00 is shown at very low resolution levels, these toilets are shown even when no buildings and no streets are visible. Also it could be some bug in mkgmap, I suppose. But when using 2f0c, it worked as expected. ploygons: remove "building=* | man_made=* | amenity=* | tourism=* [0x13 resolution 24]" add "building=* & building != no {name '${addr:housenumber}' |'${name}'} [0x13 resolution 22] building=* | man_made=* | amenity=* | tourism=* {name '${addr:housenumber}'} [0x13 resolution 22]" This adds house numbers to be shown at the map so mapper could find where numbers are shown and where not. Also I have another question - how to integrate TYP file to map with mkgmap? I'm building the map with following commands: java -Xmx1024M -Xms1024M -jar mkgmap.jar --charset=windows-1251 --net --route --family-id=1011 --ignore-osm-bounds chernivtsi-orig.osm and have TYP file M00003f3.TYP I have tried to add TYP file at the end of that command, and also the next: java -jar mkgmap.jar --gmapsupp 63240001.img M00003f3.TYP to generate map with integrated TYP file, but to success... This typ file is with Family ID 1011. Yes, i can generate the map with TYP with help of MapSetToolKit.exe, cgpsmapper and MapSource but this way is too long... Any suggestions? Best Regards

4 19

problem with --generate-sea near Toronto, Canada
by Ben Konrath 06 Feb '11

06 Feb '11

Hi, I've run into a strange problem with --generate-sea while generating a map of Canada. Here's a screenshot of the problem I'm seeing: http://bagu.org/scratch/generate-sea-problem-lake-ontario.bmp I'm using mkgmap version r1783 with these options: java -Xmx400M -Dlog.config=/home/ben/osm/mkgmap/resources/logging.properties -jar \ /home/ben/osm/mkgmap/dist/mkgmap.jar --tdbfile --latin1 --gmapsupp \ --country-name=Canada --country-abbr=CAN '--series-name=OSM Canada' \ '--family-name=Open Street Map Canada 12 Jan 2011' --location-autofill=1 \ --add-pois-to-areas --ignore-unnamed-areas --road-name-pois --check-roundabout-flares \ --route --remove-short-arcs --drive-on-right --check-roundabouts --family-id=34244 \ --product-id=1 --generate-sea=extend-sea-sectors,multipolygon --make-all-cycleways -c template.args --description=ALL Does anybody know what's going on? What's the best way to debug a problem like this? Thanks, Ben

8 24

Background polygon
by WanMil 05 Feb '11

05 Feb '11

I have stumbled upon the class MapperBasedMapDataSource. It contains the method protected void addBackground(boolean mapHasPolygon4B) to add the background polygon but in fact it adds an unclosed line. Line 124 which closes the polygon is commented out. @Steve: Should this be fixed (uncomment line 124) or is there an unknown reason to do so? I haven't found a real problem with it but at least it's not clean coding ;-) WanMil

2 1

Commit: r1827: Distinguish cycleways from footways.
by svn commit 05 Feb '11

05 Feb '11

Version 1827 was commited by marko on 2011-02-05 11:52:18 +0000 (Sat, 05 Feb 2011) Distinguish cycleways from footways. Use 0x07 "alley" (same as highway=service) for cycleways. Use 0x16 "trail" for footways and highway=pedestrian. Do not add bicycle=yes to highway=path.

1 0

rev 1822 index branch
by Felix Hartmann 04 Feb '11

04 Feb '11

Well done, finally the first version where search not only works in Mapsource (street & city or anything else if correct is found), but also now in Basecamp! (in Basecamp only streets inside the active tile?? or close to center of map?? are found, but that's the first time - and the same behaviour as with City Navigator by Garmin). Seems that this version is pretty close to be correct (well I think housenumbers are not yet supported, but correct streetsearch is much more important of course..). Only problem is sending to device fails with the usual mdr_trim_addr.cxx-3923... error. Besides searching for intersections doesn't work yet (anyone knows if it works with cgpsmapper created maps??) but I personally have never used searching for intersections (as the biggest problem is that even with city Navigator after you have selected the first street, you are still offered all streets for second street - so you can only find an intersection if you know the exact name of both streets).

3 2

mkgmap index rev. 1809
by Felix Hartmann 04 Feb '11

04 Feb '11

Finally mkgmap is not anymore crashing for me when searching for city & street (& optional zip code) in Mapsource. But well, it's true that sending maps to device on the other hand currently crashes. However great that city & street seems to be working well (again). Also searching for "Bahnhofsstrasse" in extract of Austria still crashes (but does so since the advent of the index branch more or less).

5 15

Increase MAXHINCR or MAX_HEAP_SECTS
by Bernhard Kuemel 03 Feb '11

03 Feb '11

Hi! compiling http://downloads.cloudmade.com/europe/austria/austria.osm.bz2 failed: 'java -Xmx3000M -jar /usr/share/mkgmap/mkgmap.jar --route austria.osm' failed with Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS. How can I increase that? Will it help? debians dpkg says its version 0.0.0+svn1067-1. I haven't tried the current version because that hasn't finished a smaller map after 15 mins while debians mkgmap finished in seconds. Bernhard

5 5

How to fix amenity=shelter in the default style?
by Marko Mäkelä 02 Feb '11

02 Feb '11

Last week, I changed the POI type for amenity=shelter in the default style from 0x2b05 (bed icon) to 0x6402 (an icon of a building block). Even though I later changed the resolution to 24, this symbol (along with grave yard symbols) seems to be visible from much greater distance than shops or anything else. I tried with two different map detail levels on my Edge 705. So, it looks like the 0x6402 is meant for skyscrapers and the like. Next try is with 0x6412. Same problem: at normal detail level, it shows at 120m zoom while shops and the like start to appear at 50m. At the highest detail level, shops appear at 120m and 0x6412 appears at 500m. Can anyone suggest a more suitable symbol for amenity=shelter? It does not need to be searchable, and it should not be any more 'visible' than, say, 0x2f17 (transit service; used by highway=bus_stop). The 'problem' at hand are two shelters on a railway station platform. I do not want them to be more visible on the map than the shops and other features in the town centre. Here are the nodes: http://www.openstreetmap.org/browse/node/439195020 http://www.openstreetmap.org/browse/node/439195021 If nobody can suggest a better symbol for amenity=shelter, I would remove amenity=shelter altogether from the default style. There seems to be some agreement that amenity=shelter may be too inaccurate tagging for the tourism or hiking related shelters. Side note: the unsearchable 0x6412 'hiker symbol' could be a good choice for some minor hiking feature. I think that sites where overnighting is possible do require a searchable symbol. Best regards, Marko

4 9

Commit: r1815: Only img files are used to construct the mdx file.
by svn commit 02 Feb '11

02 Feb '11

Version 1815 was commited by steve on 2011-02-02 12:47:00 +0000 (Wed, 02 Feb 2011) Only img files are used to construct the mdx file.

1 0