Change mkgmap default options to make mkgmap more userfriendly
For most people understanding which mkgmap options they should choose, is not easy - as one first needs to have quite thorough understanding. I think in general useful options should be the default - and not stick for ages to old behavior. I'm afraid I make to many mistakes if I change it myself, but I would propose the following default option changes: *changes that only need a default change because one can disable them by setting the value to 0* --reduce-point-density=5.4 --remove-short-arcs=2.8 --location-autofill=1 *option needs to able to be switched off* --generate-sea=extend-sea-sectors,close-gaps=6000 (including this by default, may keep people more aware of coastline nondestruction) *options that would need to be reversed* --supress-dead-end-nodes --adjust-turn-headings --add-pois-to-areas (this seems to be the default behaviour of most renderers now) --ignore-maxspeeds (the current handling sucks, If we would change this to become default, I would be willing to rework the default style to make use of sensible maxspeeds) --route (the default style is routable, hence the default map should be routable too)
For most people understanding which mkgmap options they should choose, is not easy - as one first needs to have quite thorough understanding. I think in general useful options should be the default - and not stick for ages to old behavior. I'm afraid I make to many mistakes if I change it myself, but I would propose the following default option changes: Agreed in general. I have a file of lots of options that I always use. I don't think compatibility with old behavior is that important. --ignore-maxspeeds (the current handling sucks, If we would change I don't understand this; it seems simple to map maxspeed on ways to garmin road speed but obviously I don't really understand :-)
On 30.04.2010 14:16, Greg Troxel wrote:
For most people understanding which mkgmap options they should choose, is not easy - as one first needs to have quite thorough understanding. I think in general useful options should be the default - and not stick for ages to old behavior. I'm afraid I make to many mistakes if I change it myself, but I would propose the following default option changes:
Agreed in general. I have a file of lots of options that I always use. I don't think compatibility with old behavior is that important.
--ignore-maxspeeds (the current handling sucks, If we would change
I don't understand this; it seems simple to map maxspeed on ways to garmin road speed but obviously I don't really understand :-)
Well because it has nothing to do with the speed on can actually drive. a highway=residential & maxspeed=80 will be treated like a highway=motorroad & maxspeed=80, even though the average speed on a motorroad will be much higher. The maxspeeds should depend on the road type, and that is only doable by changing the style. Also actually link-pois-to-areas and including speed priority/speed reductions for highway=traffic_symbol, highway=stop and so on should be included in the default style/options because it will lead to much more realistic time estimates, shorter routes (there are some garmin logic reasons why this will work out), and faster arrival times in reality with much better estimated arrival times. Also much better routing over long distances (I was able to route from Vienna to Brest on my etrex with a testmap - default style will not even get me 1/3 of the distance before running out of memory). Currently the estimated arrival times are only working more or less, because the time penalties for turning are much higher than in reality.
Felix Hartmann <extremecarver@googlemail.com> writes:
On 30.04.2010 14:16, Greg Troxel wrote:
--ignore-maxspeeds (the current handling sucks, If we would change
I don't understand this; it seems simple to map maxspeed on ways to garmin road speed but obviously I don't really understand :-)
Well because it has nothing to do with the speed on can actually drive.
In the US, generally one can drive the speed limit plus a bit when things aren't congested. I have seen in Ireland limits of 100 km/hr outside of city limits when it would be nuts to go that fast, but here the legal speed is almost always safe to drive and usually attainable except in congested times (or places, in the city, which are usually congested). (Plus, on some Interstate-class roads near me, maxspeed is 55 mph but typical is 80 mph.)
a highway=residential & maxspeed=80 will be treated like a highway=motorroad & maxspeed=80, even though the average speed on a
There are certainly roads near me marked tertiary that one can drive 80 km/hr.
motorroad will be much higher. The maxspeeds should depend on the road type, and that is only doable by changing the style. Also actually
It seems like we really need typical_speed, and rules to infer typical_speed from maxspeed and road type when typical_speed doesn't exist. Then people can put the real data in when we have it, and not build up rules that are location-specific but don't make sense in other places. (I'd argue that typical_speed should be maxspeed by default, but maybe we want rules that apply in polygons where people know the world isn't like that.)
For most people understanding which mkgmap options they should choose, is not easy - as one first needs to have quite thorough understanding. I think in general useful options should be the default - and not stick for ages to old behavior. I'm afraid I make to many mistakes if I change it myself, but I would propose the following default option changes:
*changes that only need a default change because one can disable them by setting the value to 0* --reduce-point-density=5.4 --remove-short-arcs=2.8 --location-autofill=1
*option needs to able to be switched off* --generate-sea=extend-sea-sectors,close-gaps=6000 (including this by default, may keep people more aware of coastline nondestruction)
*options that would need to be reversed* --supress-dead-end-nodes --adjust-turn-headings --add-pois-to-areas (this seems to be the default behaviour of most renderers now) --ignore-maxspeeds (the current handling sucks, If we would change this to become default, I would be willing to rework the default style to make use of sensible maxspeeds) --route (the default style is routable, hence the default map should be routable too)
I agree to change the default options (this would be a good point for a new stable release?!). I don't want to ignore the maxspeeds by default. The handling might be moved to the style instead of the hardcoded version (if possible) but the default style should use the quite simple maxspeed => roadspeed definition. Using the style would also enable to use the maxspeed=DE:urban etc. which are more and more used. I know Felix that there might be very clever rules which gives a better estimation for travel times but as Greg pointed out they are always too local to use them in the default style. Maybe this could be added to a separate style? So in the end let's wait for the extra OSM typical_speed tag (or better start a campaign for it). WanMil
On Mon, May 03, 2010 at 10:59:45AM -0500, Jeffrey Ollie wrote:
2010/4/29 Felix Hartmann <extremecarver@googlemail.com>:
options that would need to be reversed --supress-dead-end-nodes
I couldn't find this one in the source. Is there a patch out there that implements this?
BTW, the correct spelling would be "suppress". On a possibly related note, there is a way attribute mkgmap:dead-end-check=false that disables the --report-dead-ends check. If an endpoint node of a oneway street carries a FIXME or fixme attribute, the OSM parser will assign mkgmap:dead-end-check=false on the way. Today I added a rule to the default style that sets this attribute on highway=construction, so that I could avoid adding fixme attributes to a construction site. (My aim is to keep finland.osm.bz2 clean of warnings, as defined by osm2img.sh, mkgmap.args, logging.properties, and logging.ignore at http://www.polkupyoraily.net/osm/.) Marko
participants (5)
-
Felix Hartmann -
Greg Troxel -
Jeffrey Ollie -
Marko Mäkelä -
WanMil