Moin, I am trying to restrict the access to some streets during the routing, but I can't get it working. I have a rule in my style file like: highway=* & mkgmap_routing=foot {set motor_vehicle=no} [0x09 road_class=1 road=speed=1 resolution 22] I want the street only to be used for routing, when the routing mode is set to food. But right now mapsource is using the streets also in car/motorbike routing. Is there a mkgmap-switch (version 1575) required, if I want to use the access restrictions? Gruss Torsten
Hello Mark,
motor_vehicle is not understood by mkgmap
Actually, why not? If my memory serves right, mkgmap understands motorcar and motorcycle (and maps them to the same access bit), but why not motor_vehicle? For example in my understanding, tractors are covered by motor_vehicle but not motorcar or motorcycle. The road sign for banning motor vehicles does ban tractors too. Best regards, Marko
Hello Mark,
motor_vehicle is not understood by mkgmap
Actually, why not? If my memory serves right, mkgmap understands motorcar and motorcycle (and maps them to the same access bit), but why not motor_vehicle? For example in my understanding, tractors are covered by motor_vehicle but not motorcar or motorcycle. The road sign for banning motor vehicles does ban tractors too. Best regards, Marko
Hi Marko,
motor_vehicle is not understood by mkgmap
Actually, why not? If my memory serves right, mkgmap understands motorcar and motorcycle (and maps them to the same access bit), but why not motor_vehicle? For example in my understanding, tractors are covered by motor_vehicle but not motorcar or motorcycle. The road sign for banning motor vehicles does ban tractors too.
Well, no good reason, actually. It's just never been done. Consider it an omission. Cheers, Mark
2010/2/21 Mark Burton <markb@ordern.com>:
Hi Marko,
motor_vehicle is not understood by mkgmap
Actually, why not? If my memory serves right, mkgmap understands motorcar and motorcycle (and maps them to the same access bit), but why not motor_vehicle? For example in my understanding, tractors are covered by motor_vehicle but not motorcar or motorcycle. The road sign for banning motor vehicles does ban tractors too.
Yes, "motor_vehicle" is a group for all motorized vehicles and "vehicle" is a group for *all* vehicles, including the group motor_vehicles. Wiki: http://wiki.openstreetmap.org/wiki/Access
Well, no good reason, actually. It's just never been done. Consider it an omission.
It would be great if mkgmap could be made "motor_vehicle" and "vehicle"-aware, as actually, the garmin class we use for motorcar & motorbike seems to mean all motor vehicles, afaik. In my own style, I use this line before the highway definitions: highway=* & ( motor_vehicle | vehicle ) = ( no | destination |agricultural | private) { add motorcar=no} To get all those cases of "motor_vehicle=no", "motor_vehicle=agricultural" and "vehicle=no, bicycle=yes" right. Btw, is there any difference for my garmin unit between motorcar=no and motorcar=destination? I mean will *=no be avoided more strict than *=destination, even when there is no other way to reach a target? cheers, Martin
motor_vehicle is not understood by mkgmap
Actually, why not? If my memory serves right, mkgmap understands motorcar and motorcycle (and maps them to the same access bit), but why not motor_vehicle? For example in my understanding, tractors are covered by motor_vehicle but not motorcar or motorcycle. The road sign for banning motor vehicles does ban tractors too.
I assume, it is not converted, because there is no acces bit for it in the garmin format. For motorcar and motorcycle there are explicit bits and can be mapped 1:1 to the img file. Tag motor_vehicle is a combination of both and should be converted in the style file.
Hi Johann, Martin, Mark, all, First, sorry for the duplicate post. I had to switch outgoing mail servers, and did not realize that my first attempt at sending the message was queued.
motor_vehicle is not understood by mkgmap Actually, why not? If my memory serves right, mkgmap understands motorcar and motorcycle (and maps them to the same access bit), but why not motor_vehicle? For example in my understanding, tractors are covered by motor_vehicle but not motorcar or motorcycle. The road sign for banning motor vehicles does ban tractors too. I assume, it is not converted, because there is no acces bit for it in the garmin format. For motorcar and motorcycle there are explicit bits and can be mapped 1:1 to the img file.
Which two bits would they be? As far as I can tell from the source code, motorcar and motorcycle are treated the same. What would you think of the attached patch? I will test it later and post about the outcome. Best regards, Marko
Hello Marko, + new AccessMapping("motor_vehicle", RoadNetwork.NO_CAR), That's not enough because if motor_vehicle=no, you also want stop psv/taxi/emergency/hgv. It's more like: String mv = way.getTag("motor_vehicle"); if(accessExplicitlyDenied(mv)) { way.addTag("motorcar", "no"); // and so on for the other motor vehicle types } else if(accessExplicitlyAllowed(mv)) { way.addTag("motorcar", "yes"); // ... } That will get the Java to do what some people have been doing in the style file. Mark
Hello Mark,
+ new AccessMapping("motor_vehicle", RoadNetwork.NO_CAR),
That's not enough because if motor_vehicle=no, you also want stop psv/taxi/emergency/hgv.
I see, although I would not stop emergency. In which order will the access tags be processed then? What would happen with the following: motor_vehicle=no taxi=yes Johann Gail and I suppose Felix Hartmann would like to be able to specify access rights by explicit mkgmap:* attributes in the style definition. That should be straightforward for ways, but what about turn restrictions? Could the access attributes be set in the relations file? Best regards, Marko
motor_vehicle is not understood by mkgmap Actually, why not? If my memory serves right, mkgmap understands motorcar and motorcycle (and maps them to the same access bit), but why not motor_vehicle? For example in my understanding, tractors are covered by motor_vehicle but not motorcar or motorcycle. The road sign for banning motor vehicles does ban tractors too. I assume, it is not converted, because there is no acces bit for it in the garmin format. For motorcar and motorcycle there are explicit bits and can be mapped 1:1 to the img file.
Which two bits would they be? As far as I can tell from the source code, motorcar and motorcycle are treated the same.
I haven't looked into the sourcecode. But on my etrex I can choose the types Motorbike and Car (beside HGV, Taxi and others), so there has to be some difference. As far as I know, these access restrictions are handled by different bits. I personally don't like to have this dependencies hardcoded in the java code. I think it is the use of the style files to map different osm tags (like the motor_vehicle) to specific garmin ones. So each user can do it to his own thoughts and use cases. Regards, Johann
participants (5)
-
Johann Gail -
Mark Burton -
Marko Mäkelä -
Martin Simon -
Torsten Leistikow