See "Parking-Protected Bike Lanes | The City of Portland, Oregon":
https://www.portlandoregon.gov/transportation/77882
在 2020年10月27日週二 01:45，Supaplex 寫道：
> Do you have an example picture/mapillary or similar of such a street? You
> call this case yourself "parking lane" and the way you describe
Am Di., 27. Okt. 2020 um 00:38 Uhr schrieb Dave F via Tagging <
tagging@openstreetmap.org>:
>
>
> On 26/10/2020 23:26, Martin Koppenhoefer wrote:
> >
> > crossing_ref as far as I have understood the tag, is not about the
> > type of crossing,
>
> I think you've misunderstood.
then I am happy I
On 26/10/2020 23:26, Martin Koppenhoefer wrote:
crossing_ref as far as I have understood the tag, is not about the
type of crossing,
I think you've misunderstood.
DaveF
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetm
Am Mo., 26. Okt. 2020 um 17:12 Uhr schrieb Dave F <
davefoxfa...@btinternet.com>:
> 'Zebra' shouldn't be use on the primary tag 'crossing'
>
> crossing_ref was created for use within the UK because many parts of the
> rest of the world didn't understand what was meant by 'zebra'. It is, after
> al
to avoid a lot of relations, I think we should have 2 functions (or pois
within the feature):
1.
place where you can buy the tickets, and
2.
place where the tickets are checked
this could also be the same place (e.g. ticket office where you have to
pass through in order to enter the POI).
Of place
On 26/10/2020 15.19, Jeroen Hoek wrote:
On 26-10-2020 19:31, Matthew Woehlke wrote:
Alternatively, clients might look at the sort of highway running
through a parking area. A highway=tertiary is probably "street-side
parking", while a highway=service, service=parking_aisle probably is
not.
Tha
On 26-10-2020 17:52, Janko Mihelić wrote:
> I have a feeling the poi role is a bit vague. I would keep it optional,
> with only admission and issue being required for the admission relation
> to work.
Wouldn't issue be optional as well if any admission:issue:* tags are
used? For example, the roami
On 26-10-2020 19:31, Matthew Woehlke wrote:
> Alternatively, clients might look at the sort of highway running
> through a parking area. A highway=tertiary is probably "street-side
> parking", while a highway=service, service=parking_aisle probably is
> not.
That's not a bad thought, but it would
On 25/10/2020 03.58, Jeroen Hoek wrote:
Our proposal facilitates this: renderers can render street-side parking
however they wish, because the tag tells them it is street-side parking.
Alternatively, clients might look at the sort of highway running through
a parking area. A highway=tertiary i
pon, 26. lis 2020. u 18:13 Justin Tracey napisao je:
>
> Another thing worth addressing in the proposal is how this relates to
> public transit systems. Things like a ferry that require a ticket for
> entry might translate pretty directly, but what about bus or light rail
> systems where you buy
Do you have an example picture/mapillary or similar of such a street?
You call this case yourself "parking lane" and the way you describe it,
it sounds like a typical case for parking:lane:* =
parallel/diagonal/perpendicular, but not for
parking:lane:*/parking=street_side. "street_side" is intended
On 2020-10-24 9:32 a.m., Janko Mihelić wrote:
> Here is my proposal on the wiki:
> https://wiki.openstreetmap.org/wiki/Proposed_features/Admission
>
> In short, we don't have any way to connect places that need a ticket for
> entrance, with the place that sells those tickets. Usually those places
pon, 26. lis 2020. u 15:20 Jeroen Hoek napisao je:
> On 26-10-2020 13:44, Janko Mihelić wrote:
>
> I would use a separate role for the poi (point-of-interest) itself, so
> data consumers know what the subject of the relation is (the poi), where
> its places of admission (entrances) are, and where
'Zebra' shouldn't be use on the primary tag 'crossing'
crossing_ref was created for use within the UK because many parts of the
rest of the world didn't understand what was meant by 'zebra'. It is,
after all, a nickname:
https://wiki.openstreetmap.org/wiki/Key:crossing_ref
DaveF
On 16/09/
On Sat, Oct 24, 2020 at 6:40 AM Supaplex wrote:
> Hey all,
>
> I would like to invite you to discuss a proposal for "parking =
> street_side" for areas suitable or designated for parking, which are
> directly adjacent to the carriageway of a road and can be reached directly
> from the roadway wit
On 26-10-2020 13:44, Janko Mihelić wrote:
> Although, now that I think of it, you can add the whole theme park
> to the relation, and add role "admission", that doesn't hurt.
I would use a separate role for the poi (point-of-interest) itself, so
data consumers know what the subject of the relation
ned, 25. lis 2020. u 16:16 Martin Koppenhoefer
napisao je:
> as an additional datapoint
> shop=ticket is the only one with significant usage: (15000)
>
> https://taginfo.openstreetmap.org/search?q=ticket#values
>
> From its definition, it could also not be suitable (unclear), or maybe it
> is?
>
It's easy to see how we would tag simple cases, like a cinema and a ticket
shop. Just add a relation, type=admission, cinema gets the role
"admission", and the ticket shop gets the role "issue".
The question is, how do we tag edge cases.
For example, a big amusement park. In my opinion, there shou
18 matches
Mail list logo
