<div dir="ltr">
The use of the proposed access tagging on roads to indicate whether or not a private hire/rideshare can drive on them I think we can all agree is straightforward, but it gets muddy when talking about other types of infrastructure that this might apply to.<div><br></div><div>I would like to better understand how such access tagging would work in practice for an example at my local airport. In that instance, the designated Uber pickup/dropoff location is a particular spot within a specific parking garage (tagged with amenity=parking + building=yes). Do I add private_hire=designated to the building? Okay, that can work. But then, adding operator=Uber doesn't work -- after all, Uber isn't operating the parking garage, they just have permission to make pickups at a particular signed location. This tells me that a POI that's separate from the parking garage object is needed to indicate the precise pickup location within the garage. Are we saying that's amenity=taxi + private_hire=designated? That doesn't work because a taxi stand implies on-demand transportation. I would just ask that we consider the full picture of how designated private hire/rideshare tagging should be done at airports and other transportation hubs; without that "big picture", merely focusing very narrowly on the access attribute feels incomplete.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 31, 2020 at 4:03 PM Simon Poole <<a href="mailto:simon@poole.ch" target="_blank">simon@poole.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>I think there is a bit of a misunderstanding here. <br>
</p>
<p>This is not about taxi stands or anything similar, but about
access for Lyfts, Ubers, Grabs employees to streets and
infrastructure that they would not be able to utilize if they were
driving for themselves (including actual ride sharing :-)).
Example pick up and drop off access at airports and similar, this
might include access to taxi dedicated infrastructure too. This is
quite legit and no beef with the companies wanting to be able to
model this to improve routing for their drivers and customers.</p>
<p>Simon<br>
</p>
<div>Am 31.10.2020 um 15:23 schrieb Brian M.
Sperlongano:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>In the United States at least, there is a very real
difference in meaning between "rideshare" and "taxi" services
when it comes *specifically* to access at airports. And I
believe that is the intent of this proposal: how do I tag the
special area in the airport where I must go in order to be
picked up by XYZ rideshare company?<br>
</div>
<div><br>
</div>
<div>At an airport, if you wish to take a taxi, you walk up to a
taxi stand (amenity=taxi), where the taxi cabs line up, and
you take the first taxi cab in line. This is an explicit area
where only taxis queue up.</div>
<div><br>
</div>
<div>Alternately, if you wish to take a "ride share", you are
using an app to make an arrangement with a specific vehicle
and driver to be picked up at a specific location. In this
case, airports often (at this point, probably "usually") have
a specified location where such ride shares are allowed to
pick up and/or drop off passengers.</div>
<div><br>
</div>
<div>In some cases, the ride share pickup/drop-off locations
have specific areas that are different for different ride
share providers. For example, at my local airport, due to
disagreements about how much these companies should pay the
airport for curb access (really), there is one location where
you can pick up a Lyft, and a separate location 100 meters
away off the airport property where you can pick up an Uber!</div>
<div><br>
</div>
<div>The point here is that in the US there is a very real
distinction between these two classes of objects, and the
information someone traveling through the airport looking for
ground transportation would want to know is:</div>
<div>1. Is it a ride share (pre-arranged pickup) or taxi stand
(on-demand pickup)</div>
<div>2. Is it limited to only specific ride share companies?</div>
<div>3. Is it pickup only, dropoff only, or both?</div>
<div><br>
</div>
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sat, Oct 31, 2020 at 6:36
AM Simon Poole <<a href="mailto:simon@poole.ch" target="_blank">simon@poole.ch</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>For starters I would oppose using the term "rideshare"
for what is a taxi/chauffeur service. It should be noted
that there are actual rideshare organisations and
services out there, but uber, grab, lyft etc. are not
among them, they are simply trying to co-opt a term with
positive associations for their operations.</p>
<p>Further, real rideshare services don't get special
access treatment anywhere I know of, outside of vehicle
occupancy regulations, which isn't surprising as real
ride sharing simply involves sharing costs and car on a
trip that the driver was going to make anyway.</p>
<p>If there are actual legal differences between taxi and
chauffeur access somewhere, we could use chauffeur or
chauffeur-driven as an access tag (better suggestions
welcome).<br>
</p>
<p>Simon<br>
</p>
<br>
</div>
</blockquote>
</div>
</div>
</blockquote>
..............<br>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>