On 09.12.2009 12:45, Steve Hosgood wrote:
Felix Hartmann wrote:
I do agree though that OSM's tagging for road surfaces is a bit of a mess, but it needs an OSM-level cleanup if that's a problem, not at mkgmap-level.
AFAIK there are "surface=???" "smoothness=???" "mtb:scale=???" "sac_scale=???" "rtc_rate=???" tags in OSM, all of which (sometimes in combinations) ought to be enough to give mkgmap the clues needed to set the routeability of a given way. Plus "access=???" and "<vehicle>=no" of course.
Not just that, but those tags already exist. We should be using them. Steve
You don't seem to understand.
No - I understand fine, thanks. I just disagree with the idea that this proposed new tag should be mkgmap-specific. No, sorry to be so direct, but you clearly don't understand. There is no bloody new key or tag. There is just an mkgmap internal command for conversion. There will never be a universal understanding of what is paved and what not (or whether you can go there with your car, foot, bicycle or not). Therefore we have so many keys. Now it is only a question of how to convert it to Garmin .img. And that is what the style file is used for.
Noone wants that you add this key to OSM data! The same is true for ferries. Noone want you to add mkgmap:ferry=1 to osm data, but by using it like this one could for example only exclude gondolas or other features on avoid ferries, but not block ferries themselves. Garmin format is limited (or can you show me an avoid "cablecar" or avoid "drag_lift" key?) - therefore many mappers add actions to commands that are not what they tell you they are - so e.g. by clicking avoid ferries, you will actually avoid cablecars and other aerialways. Some other people might find this useful to block/enable public transport routing. The same goes for unpaved. Not everyone will use it to block unpaved ways. Some people will want to convert this function to something completly different. E.g. if I want to create a public transport only map for Garmin I could avoid toll=yes to avoid bus lines and tramways, avoid unpaved roads to avoid tubes and regional trains, and avoid ferries to avoid long distance trains.
You can use them and the default style should use some of them. However there is no clear borderline of what is paved and what is unpaved, therefore it is best to use a new key.
Well, a new key is one option, getting the entire OSM community to tidy up a bit on the use of existing keys is another option.
IMHO, if use of the existing keys isn't feasable, then any new key should be more like "autorouter=avoid" or something. This is not mkgmap-specific, it would apply to all the other projects looking to use OSM data for in-car GPS navigators, and the browser-driven computer navigators too.
But before adding a new key, we should be able to "prove" that no combination of the existing keys does it for us.
Steve
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev