Re: [OSM-talk] Routing through access=delivery

2016-02-17 Thread Greg Knisely
Markus,

Indeed, Mapzen (Valhalla) routing was processing motor_vehicle=delivery
incorrectly.  We have updated our servers with the latest code and we are
no longer taking the service road as you described.  Thank you for
reporting this issue and let us know if you have additional issues.

Thanks again.

--Greg Knisely


On Sat, Feb 13, 2016 at 7:00 AM, <talk-requ...@openstreetmap.org> wrote:

> Send talk mailing list submissions to
> talk@openstreetmap.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.openstreetmap.org/listinfo/talk
> or, via email, send a message with subject or body 'help' to
> talk-requ...@openstreetmap.org
>
> You can reach the person managing the list at
> talk-ow...@openstreetmap.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of talk digest..."
>
>
> Today's Topics:
>
>1. Routing through access=delivery (Markus Heidelberg)
>
>
> --
>
> Message: 1
> Date: Sat, 13 Feb 2016 10:13:45 +0100
> From: Markus Heidelberg <markus.heidelb...@web.de>
> To: talk@openstreetmap.org
> Subject: [OSM-talk] Routing through access=delivery
> Message-ID: <5799001.Sx99Mkpynt@evo>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> last week after missing the exit on a highway=motorway, a Garmin NĂ¼vi
> 300 with a Lambertus map tried to turn through a service road mapped
> with motor_vehicle=delivery. This road connects the motorway directions
> via service area on each side.
>
> I thought this might be a problem with mkgmap (which creates the Garmin
> maps), but Mapzen and OSRM routing behave the same:
>
> https://www.openstreetmap.org/directions?engine=mapzen_car=49.31689%2C8.57541%3B49.31659%2C8.57453#map=17/49.31827/8.57205
>
> Is this on purpose or do all three maps/routers ignore the
> access=delivery tags wrongly?
>
> Additional info on an already existing note at the concerned location
> (in German):
> https://www.openstreetmap.org/note/238113
>
> Markus
>
>
>
>
> --
>
> Subject: Digest Footer
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
> --
>
> End of talk Digest, Vol 138, Issue 12
> *
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


Re: [OSM-talk] new payment type

2015-02-24 Thread Greg Knisely
First, thank you both for the feedback.  From a routing/driving directions
perspective, I was hoping to determine if the user needs to slow down at
all where a toll exists if they use an ETC device.  Obviously, if you have
to pay with cash, your route will take longer.

I was looking for general payment types (cash, coin, transponder) so that
this costing can be done.  However, I do see benefits of calling out the
ETC device as well.

Thank you for your time.

  --Greg.

On Mon, Feb 23, 2015 at 4:44 PM, Paul Johnson ba...@ursamundi.org wrote:

 On Mon, Feb 23, 2015 at 3:31 PM, Greg Knisely g...@mapzen.com wrote:

 I think for that situation it could be easily handled with
 payment:transponder=ez_pass;pikepass.  This is what is used for other
 tags.  A great example of this is the ref tag.

 As for payment:fasttrak=no, I think if one would just leave the tag off
 that would imply that it is not accepted.


  I generally explicitly tag toll lanes in areas one would normally expect
 the tag in question, since there's plenty of cash only lanes that dont take
 the ETC tag, and ETC lanes that don't take cash.  But they don't
 take...American Express.

 /PIKEPASS, it's everywhere you want to be?

___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk


[OSM-talk] new payment type

2015-02-23 Thread Greg Knisely
Hello all,

I was wondering what people's thoughts were on adding a new payment type of
transponder.  For the road toll section, there are three transponder
companies listed (http://wiki.openstreetmap.org/wiki/Key:payment):

payment:e_zpass=*
payment:pikepass=*
payment:via_verde=*

So instead of listing all the companies in the world, I am proposing
payment:transponder=*  The values could be e_zpass, pikepass, via_verde,
peach_pass, etc., but also yes or no.

This payment type would be very helpful in routing applications for toll
roads.  For example, the narrative could call out Exit 2b [Coin and
Transponder(Via Verde) Only Accepted].

Thanks.

  --Greg Knisely
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk