[mkgmap-dev] Change mkgmap default options to make mkgmap more userfriendly

Fri Apr 30 13:37:59 BST 2010

Felix Hartmann <extremecarver at 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.)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20100430/031cd02f/attachment.bin 