Hi all,
the default style contains this line:
motor_vehicle=* { add mkgmap:car='${motor_vehicle}' }
My understanding is that motor_vehicle includes
mkgmap:truck, mkgmap:car, mkgmap:bus, mkgmap:taxi,
mkgmap:emergency, and mkgmap:delivery, not just mkgmap:car.
So motor_vehicle=no means something
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 happ
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 bu
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"
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
2010/2/21 Mark Burton :
>
> 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 ar
>
>> 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_vehic
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_vehic
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
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
10 matches
Mail list logo
