Thank you for the reply.
> These difficulties, and opposing ideas on how to deal with existing tags,
make it hard to change established tagging schemes. But I am strongly in
favour of not establishing new amenity=* for hitherto unmapped facilites,
but rather use new tags altogether, whose use can
Sorry to see that it missed out Jan :-(
As Joseph suggests, maybe take out the country specific & try again?
On Tue, 23 Apr 2019 at 11:22, Joseph Eisenberg
wrote:
> It looks like several critical comments mentioned that the country
> specific tagging (eg police:FR=*) was not good.
>
Just for i
That’s very close. I suppose it would have been approved with one more vote.
It looks like several critical comments mentioned that the country specific
tagging (eg police:FR=*) was not good.
I would suggest just removing these from being mentioned in the proposal.
Perhaps we can try talking to t
The 'Great North Walk' https://www.openstreetmap.org/relation/1388126
has - the ways that form the route ... and
3 relations with the roles 'alternate' that form alternative paths ..
one of them is a closed section that was the original path but is in
conflict with a shooting range.
On 23/0
Do you have a link to an example?
I’m reminded of the Oregon Coast bicycle route, which has alternative
section s that leave the main highway to follow a scenic but longer road
through the hills or closer to the coast. There are also alternatives that
follow a Main Street (high street) through a v
Long walking routes often have a main route and several additions of
various types. If these additions are not waymarked, they are not recorded
in OSM. Easy.
But often, they are. On maps these are usually shown as a striped line,
while the main route is usually a continuous line.
I would like to
Am Mo., 22. Apr. 2019 um 01:48 Uhr schrieb Paul Allen :
>
> It certainly makes overpass turbo queries a lot simpler and more intuitive
> if we can group all
> education facilities under education rather than under amenity. Typing
> "education=*" is shorter
> than "amenity=school or amenity=univer
The voting period for the refined police facilities proposal (
https://wiki.openstreetmap.org/wiki/Proposed_Features/Police_facilites) has
ended. The proposal has been rejected by 8 approvals against 3 rejections
(72.7% approval).
Best,
Jan
___
Tagging m
On Mon, Apr 22, 2019 at 8:47 AM Valor Naram wrote:
> I need to clarify the access=* key for my proposal to pleace this discussion.
>
> changing_table:access=yes
> The changing table is accessible to the public. This means you can change the
> nappy of your baby without being a customer. This happ
Hi everyone!
I have recently been mapping a lot of turn:lanes information on highways in
my area, but ran into the issue that turn:lanes fails to store all of the
necessary information in many junctions. Multi-lane roundabouts, single
point urban interchanges, 5 way intersections with divided road
On Mon, Apr 22, 2019 at 4:57 PM Michael Brandtner via Tagging <
tagging@openstreetmap.org> wrote:
> I don' think we should use no, but private. But as others have stated, I
> can't really think of a changing table that should be mapped in osm but
> isn't accessible even for customers.
> But us thi
On Mon, 22 Apr 2019 at 14:45, bkil wrote:
> leisure=outdoor_seating + shelter=no + covered=no
>
The wiki for the tag does not offer shelter or covered as associated tags.
Instead it
has weather_protection.
leisure=outdoor_seating seems to do what the OP wanted. The only quibble I
have with
it
I don' think we should use no, but private. But as others have stated, I can't
really think of a changing table that should be mapped in osm but isn't
accessible even for customers.
But us this really a point we need to discuss? Can't we just say that
changing_table:access should be used with v
On Sun, Apr 21, 2019 at 10:39 AM Joseph Eisenberg
wrote:
> > Col or gap (use saddle? And that is in OSM) = a col is the lowest point on a
> > mountain ridge between two peaks.
>
> Yes, "col" is the French word for saddle, a low point on a ridge.
>
> A gap is also usually a saddle (or sometimes a m
leisure=outdoor_seating + shelter=no + covered=no
On Mon, Apr 22, 2019 at 3:11 PM Paul Allen wrote:
> On Mon, 22 Apr 2019 at 13:49, bkil wrote:
>
>> Note that outdoor_seating is usually for customers, so don't forget to
>> add:
>> access=yes
>>
>
> True, usually it's associated with customers.
It could be added to the "features" key as "adjustable_height" value. Original Message Subject: Re: [Tagging] Feature Proposal - RFC - Baby changing tableFrom: bkil To: "Tag discussion, strategy and related tools" CC: To aid those with achondroplasia, I think it would also be useful
On Mon, 22 Apr 2019 at 13:49, bkil wrote:
> Note that outdoor_seating is usually for customers, so don't forget to add:
> access=yes
>
True, usually it's associated with customers. But there may be public
outdoor seating,
possibly covered.
Also, why not simply use the already established:
> sh
To aid those with achondroplasia, I think it would also be useful to
indicate whether adjustable_height is a feature of the table, though I
guess they are already prepared to use the floor anyway.
On Mon, Apr 22, 2019 at 2:22 PM Paul Allen wrote:
>
>
> On Mon, 22 Apr 2019 at 00:50, marc marc wr
Note that outdoor_seating is usually for customers, so don't forget to add:
access=yes
Also, why not simply use the already established:
shelter=no + covered=no?
On Mon, Apr 22, 2019 at 2:35 PM Paul Allen wrote:
> On Mon, 22 Apr 2019 at 11:01, bkil wrote:
>
>> This is what note=* is for - when
I need to clarify the access=* key for my proposal to pleace this discussion.changing_table:access=yesThe changing table is accessible to the public. This means you can change the nappy of your baby without being a customer. This happens rarely.changing_table:access=noThe changing table isn't also
On Mon, 22 Apr 2019 at 11:01, bkil wrote:
> This is what note=* is for - when you'd like to disclose an important fact
> with future mappers that is not that interesting to non-mappers. You may
> also draw a way/area and indicate the count of benches there or the total
> sitting capacity. We may
On Mon, 22 Apr 2019 at 00:50, marc marc wrote:
>
> if the goal is to talk about accessibility, then use the wheelchair tag.
>
That just says if you can get a wheelchair into the toilet.
but if by measuring the height of the table, you think you have done
> what it's need to inform accessibility
changing_table:location=unisex_toilet;wheelchair_toilet Original Message Subject: Re: [Tagging] diaper subkey for wheelchair toilets including a changing tableFrom: bkil To: "Tag discussion, strategy and related tools" CC: Well, the place I had in mind only had a unisex toilet - a
height=* was my fault, but I don't feel strongly about it, you may remove
it then. "straps" and "tilting" could still go under the list of
*:feature=*, though, that's a good idea.
toilet vs. room vs. dedicated_room:
How do you map a changing table that is found inside a small "toilets"
corridor/ar
Well, the place I had in mind only had a unisex toilet - a single,
unsegregated entrance with possible multiple booths. In this case, the two
are equivalent. If there exist two entrances: one unisex and one
wheelchair, then it is reasonable to differentiate the two.
On Mon, Apr 22, 2019 at 12:27 A
This is what note=* is for - when you'd like to disclose an important fact
with future mappers that is not that interesting to non-mappers. You may
also draw a way/area and indicate the count of benches there or the total
sitting capacity. We may need to submit a proposal this, though.
https://wiki
On 22/04/19 09:49, marc marc wrote:
Le 22.04.19 à 00:39, Paul Allen a écrit :
On Sun, 21 Apr 2019 at 22:56, marc marc wrote:
however I wonder if it's useful to promote changing_table:height
is there really any use for this tag ?
A parent in a wheelchair might find that useful informa
27 matches
Mail list logo
