I wouldn't do that because then logically you have two features, but in this case they are one in the same, it's a rideshare pickup parking lot, as opposed to a on-street section designated for rideshare pickup/dropoff.
On Thu, 5 Nov 2020 at 09:38, Simon Poole <si...@poole.ch> wrote: > While I would try to avoid it, you can naturally simply duplicate the > geometry (and you don't even need to duplicate the nodes to do that). > Am 04.11.2020 um 22:26 schrieb Andrew Harvey: > > > On Wed, 4 Nov 2020 at 20:10, Philip Barnes <p...@trigpoint.me.uk> wrote: > >> On Wed, 2020-11-04 at 07:26 +1100, Andrew Harvey wrote: >> >> >> >> On Tue, 3 Nov 2020 at 23:14, Simon Poole <si...@poole.ch> wrote: >> >> We don't seem to have a tagging currently for dedicated pickup locations >> in this kind of context, bus stops etc are naturally taggable), if >> considered really useful I don't see why we couldn't introduce a >> amenity=...pickup... tag. >> >> >> But if such a dedicated pickup location is a carpark then it needs >> amenity=parking, so it can't fit into the amenity key. >> >> >> A pickup point will be a node within a car park area. >> >> Its is already common to add amenity=bicycle_parking nodes within >> amenity=car_park areas. >> > > Why would it be a node within a car park? For example > https://www.openstreetmap.org/way/366754575 is the designated airport > Uber, etc. pickup location, not some point inside the car park, but the > whole car park itself. > > _______________________________________________ > Tagging mailing > listTagging@openstreetmap.orghttps://lists.openstreetmap.org/listinfo/tagging > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
