July 2011 - mkgmap-dev - The mkgmap lists

Index and equally named cities
by WanMil 11 Jul '11

11 Jul '11

Hi, there have been some reports on the list that there are problems searching for streets in cities with the same name but with different regions. I can confirm that and have created a very simple testcase to show that problem. Attached osm file contains two streets: 1: name=Hauptstrasse, city=Testcity, region=Region 1, country=DEU 2: name=Hauptstrasse, city=Testcity, region=Region 2, country=DEU So both streets differ only in the position and the region they contain to. The testfile should be compiled with the locator branch (parameter --index must be set). It's more easy to assign the city/region/country name I want to have with locator branch but with a modified testcase it should also work with the trunk. Now I can search for the street Hauptstrasse and get both streets as result (search1.png). When I add Testcity to my search I only get the street of Region 1 in my result although both streets should match the search. The testcase might be modified using two different streetnames (Hauptstrasse1 for street 1 and Hauptstrasse2 for street2). Entering a search for Hauptstrasse2 with city=Testcity will not find any result. Steve, do you have any idea where the problem might be located? WanMil

9 62

Commit: r1987: Swap the codes of hamlet and village. Suggested by Minko.
by svn commit 11 Jul '11

11 Jul '11

Version 1987 was commited by marko on 2011-07-11 09:24:04 +0100 (Mon, 11 Jul 2011) Swap the codes of hamlet and village. Suggested by Minko.

1 0

Commit: r1986: Omit man_made=cable_line from polygons.
by svn commit 11 Jul '11

11 Jul '11

Version 1986 was commited by marko on 2011-07-11 09:23:08 +0100 (Mon, 11 Jul 2011) Omit man_made=cable_line from polygons.

1 0

map-sea-color-opacity
by Hendrik Oesterlin 09 Jul '11

09 Jul '11

Hello, I am making some transparent map to overlay it with an orthophoto in photoshop (as the WMS-feature ist not jet available...... ;-) ) There is the possibility to use map-background-opacity : 0 in order to obtain an completely transparent background on land. In analogy, I tried map-sea-color-opacity : 0 but it is not allowed I have simply executed "set-setting name=map.coastline.mode value=ignore" do make no sea to be rendered, but it could be interesting in some cases to be able to define the sea transparency. Maybe some "to-do" while implementing the WMS feature? Regards Hendrik

1 1

unused polygons hexes
by maning sambale 08 Jul '11

08 Jul '11

A lot of POIs are being converted to polygons these days because of hires imagery. For my map I'm mostly interested to just show it as a point. The add-poi-to-areas switch is very helpful. However, I'm running out of possible hex to assign the polygon. Any advise on the unused hex we can recycle? I prefer an invisible hex when using the map even without a typ file. Of course I can make it invisible using a TYP editor but a hex that didn't have to edited is of course better. Is there such hex types? :) Thanks! -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 1

address search not working in nuvi 4-digit series
by maning sambale 08 Jul '11

08 Jul '11

I'm not sure if this was reported but already. We received reports from users that the address search is not working on newer 4-digt series of nuvi (1200, 1490t and 1310) The maps were loaded via mapsource. Search works on other models. -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 6

Commit: r1985: Remove access=yes from highway=*.
by svn commit 07 Jul '11

07 Jul '11

Version 1985 was commited by marko on 2011-07-07 21:55:20 +0100 (Thu, 07 Jul 2011) Remove access=yes from highway=*.

1 0

problem with highway=cycleway in default style
by Ben Konrath 06 Jul '11

06 Jul '11

Hi everybody, I've found a problem with the highway=cycleway in the default style. The current setting from the default lines file is this: highway=cycleway {add access = no; add bicycle = yes; add foot = yes} [0x07 road_class=0 road_speed=1 resolution 23] One small problem is that the cycleway should probably be listed as a path or trail (0x16) instead of alley (0x07). The bigger issue, however, is that the extra tags which are added to highway=cycleway makes cycleways routable by car under certain circumstances. The problem comes from the way that the access tag is used in the style file. The access tag in OSM describes legal access to a given highway: http://wiki.openstreetmap.org/wiki/Key:access A tag with 'access = no' means that the general public is not allowed to go on that particular highway. Likewise, 'access = yes' means that the general public is allowed to use that highway. And then there's specific types of access in between yes and no for specific types of traffic as listed on tag's wiki page. In the default style of mkgmap, it seems that the access tag is used to represent whether or not a particular highway type is routable by motor vehicle. If you have have cycyleway that is tagged with 'access = yes' - meaning the public is allowed use that cycleway - the 'add access = no' rule will not overwrite the access rule in the OSM data and the cycleway will be routable by motor vehicle. An example of this can be found in Red Deer, Alberta, Canada on the Bob Johnson Trail: http://www.openstreetmap.org/?lat=52.276167&lon=-113.804459&zoom=18&layers=… To solve this problem, I've changed 'add access = no' to 'set access = no' so that the access tag will be overwritten and cycleways will not be routable. But this seems to be a hack because it's not really describing the OSM data correctly. I think it would be better to use the motor_vehicle tag to determine if a cycleway is routable by car. The motor_vehicle tag is described on the 'access' tag's osm wiki page above. Here's the proposed style for cycleways: highway=cycleway {add motor_vehicle = no; set bicycle = yes; add foot = yes} [0x16 road_class=0 road_speed=1 resolution 23] This would prohibit motor_vehicle routing on cycleways by default if the cycleway if the cycleway doesn't have a motor_vehicle tag. This would also allow motor vehicle routing on cycleways that allow it as described in this thread from last month: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q2/011771.html We'd still have to support the OSM access tag somehow. I did a quick grep through the mkgmap source and it seems that there isn't support of the motor_vehicle tag. I would like to make a patch to address this issue but I have a couple of questions first. Is the access tag used to describe motor vehicle access in mkgmap? Does the garmin format support the idea of public / private access separately from motor vehicle access? For now, I'm using the attached patch prohibit . I've change 'add bicycle = yes' to 'set bicycle = yes' because anything tagged a cycleway must allow bicycles by definition. Thanks, Ben

3 12

[Announce] CommonMap Island v0.5.9 (beta version, helpers needed)
by Sam Vekemans 06 Jul '11

06 Jul '11

Hi all, Happy to report that CommonMap Island v0.5.9 (beta) is now available... The idea is simple. Show all map features in the same location, so then everyone knows how to map. The 2nd tab on this spreadsheet is what im working on now 'mkgmap1979_Garmin_Features_A-Z' https://spreadsheets.google.com/spreadsheet/ccc?key=0Am70fsptsPF2dHJxMG05Zm… It's basically all of the osm key/value pairs which line up to the standard garmin Map Feature codes. I made a quick document that i will enhance to show the latest mkgmap version and show the Category/Description, as gpsmapedit sets them. https://docs.google.com/document/d/1hieJ1JzIcLOWeAXErdNBN6Xw1ko0zW5YOf8zmxF… Off the coast of CommonMap Island is 'Mkgmap Island' http://api.development.i386.commonmap.org/?lat=-0.02061&lon=0.04799&zoom=15… & Over on the 1st tab 'OSM Map Features', we can see 'JOSM ver.4064 Presets' across the top (column T), I'll be making a new Sheet showing all of the osm key/value pairs and how they line up with JOSM presets. I have a column for potlatch2 presets and another for mapnik presets, and a few others, merkaartor and taginfo usage... These will be smaller Islands surrounding the main 'CommonMap Island' which holds all of the map features which are found on all of the surrounding Islands. If anyone Is interested in helping out, please contact me directly. I emailed the nzopengis(a)googlegroups.com list, as over in Wellington, NZ I dropped in some of the linz data http://api.development.i386.commonmap.org/?lat=-41.286&lon=174.833&zoom=11&… And last but not least, over on the Open Map Features spreadsheet is where you'll find all (alot, not all) of the external dataset features, which corrispond to OSM key/value pairs https://spreadsheets.google.com/spreadsheet/ccc?key=0Am70fsptsPF2dENGRWNOQ3… My aim is to setup an Island for each of the datasets, showing all of the features & the categories and codes they are found in. It'll all get done... in time... and proportional to how much help is available for it. :) Cheers, Sam --- Across Canada Trails - Beyond 2017 - The National Trails Network Victoria, BC Canada Twitter: @Acrosscanada Blog: http://acrosscanadatrails.posterous.com/ Facebook: http://www.facebook.com/sam.vekemans Diaspora: acrosscanadatrails(a)joindiaspora.com<https://joindiaspora.com/people/44143> Skype: 'Sam Vekemans' Member, CommonMap Inc. http://commonmap.org/ IRC: irc://irc.oftc.net #CommonMap Also find us on Facebook, Twitter and LinkedIn

1 0

Mysterious capitalisation (or not) of labels
by Charlie Ferrero 05 Jul '11

05 Jul '11

mkgmap, or Mapsource, or Garmin in general, seems to have inconsistent capitalisation of labels. Take the following two buildings: Building 1 (http://www.openstreetmap.org/browse/way/99899451) name=Khalidiya Palace Tower A building=yes Building 2 (http://www.openstreetmap.org/browse/way/99899455) name=Khalidiya Palace Tower C building=yes In Mapsource (6.16.3) these labels render differently (see attached). Building 1 renders as Khalidiya Palace Tower a Building 2 label renders as Khalidiya Palace Tower C Is this a bug in mkgmap or a bug in Mapsource? -- Charlie

4 3