"Please bear in mind that quite a lot of them can be re-tagged
automatically"
Can you give a single example of similar automatic re-tagging in the past ?
Yves___
Tagging mailing list
Tagging@openstreetmap.org
Dear all,
martianfreeloader wrote Tue Sep 20 2022 20:59:07 GMT+0200
But yes, you're totally right, it will still be a considerable task to >
re-tag all the 2k via ferratas, 3k climbing routes and ~20k difficult
> hikes.
Please bear in mind that quite a lot of them can be re-tagged
Hello all,
Following the rejection of my previous proposal, I've created a new
proposal. It proposes to deprecate passenger_information_display and
introduces new keys which can be used to add additional information about
the departures boards.
There are apps for that. ;-) For trees, I mean. But thanks for adding
them anyway.
Anne
On 20/09/2022 20:03, martianfreeloader wrote:
I agree.
We have loads of tags that only mappers with special knowledge can use
correctly (just dive into the world of railways). This doesn't mean
these tags
Tens of thousand in remote areas, where contributors are scarce, just to change
sac_scale=demanding_mountain_hiking to
highway=demanding_mountain_hiking_alias, I don't see this going to get a lot of
support. I'm also afraid that would put a lot of strain on a relatively small
community of
I agree.
We have loads of tags that only mappers with special knowledge can use
correctly (just dive into the world of railways). This doesn't mean
these tags shouldn't used by those who know what they're doing.
When it comes to trees, I'm a quite "ordinary" mapper. I have no idea
how to
Introducing a new highway value to replace rather common existing values can
only succeed if the community agrees AND significant data users and renderers
confirm they can and will handle it, AND local communities commit to implement
it massively. And that is, assuming consensus is reached and
Nope, didn't forget about that.
My point was rather that in case the community decides the discussed
primary-tag distinction is favourable, it would be the least effort for
us is to keep highway=path for the vast majority of ways (12 million)
instead of changing them all to highway=easy_path
Le 20 septembre 2022 19:04:59 GMT+02:00, martianfreeloader
a écrit :
>
>How about this:
>
>- keep highway=path for everything that can be walked by normal people (this
>means we don't need to re-tag millions of ways)
>- introduce a new tag highway=demanding path for everything else.
>
I
sent from a phone
> On 20 Sep 2022, at 18:07, Joseph Eisenberg wrote:
>
> This proposed tag would be used for much less well known sites. How should
> ordinary mappers determine if a ruin is an old fort or a fortified settlement
> or a an ancient prison?
either there will be a sign
Hi Georg,
I mostly agree, except in one point: I totally did have steep
mountainous paths in mind in the definition of highway=path, as long as
regular people can walk them.
I think your highway=demanding_path tag instead of highway=scramble is a
great idea!
How about this:
- keep
Re “ it makes a differences whether the structure results in a self-imposed
isolation or isolation created by an adversary party.”
How can a non-archeologist determine the initial purpose of an
archeological site?
For example, Machu Picchu is a very famous site in Peru which has been
extensively
Dear all,
Peter wrote Tue Sep 20 2022 14:02:24 GMT+0200
This would mean that there is a new primary tag `highway=scramble` which makes
some currently existing primary tags obsolete:
1) `highway=via_ferrata` gets replaced by `highway=scramble +
scramble=via_ferrata`
2) `climbing=route` gets
Dear all,
martianfreeloader, wrote Tue Sep 20 2022 10:52:06 GMT+0200
I think if something is tagged highway=path then data consumers should
be able to expect that regular people can walk on it without having to
look at an ever growing zoo of secondary tags. > ...
I think a new generic highway=
Mvg Peter Elderson
> Op 20 sep. 2022 om 13:49 heeft martianfreeloader
> het volgende geschreven:
>
> This would mean that there is a new primary tag `highway=scramble` which
> makes some currently existing primary tags obsolete:
> 1) `highway=via_ferrata` gets replaced by `highway=scramble
Hi Anne,
Thanks for the proposal. I've left a comment on the wiki talk page.
On 18/09/2022 12:39, Anne-Karoline Distel wrote:
Hello everyone,
I'm proposing to introduce a new sub class of (archaeological) site
types "defensive settlement":
Yes, what I have in mind is a new primary tag:
`highway=scramble`
with secondary tags like
`scramble=via_ferrata`
`scramble=climbing`
`scramble=alpine_hiking`
etc.
Tertiary tags would be:
`via_ferrate_scale=*`
`climbing:grade:uiaa=*`
`sac_scale=*`
The secondary tags would be orthogonal. In
sent from a phone
> On 20 Sep 2022, at 10:56, martianfreeloader
> wrote:
>
> This would encompass
> - via ferratas
> - demanding or dangerous hikes
> - climbing routes
> - anything else?
>
> To me, highway=scramble seems a good solution for this, but I'm not a native
> English speaker, so
I think if something is tagged highway=path then data consumers should
be able to expect that regular people can walk on it without having to
look at an ever growing zoo of secondary tags.
Data consumers, like all of us, have limited capacity. We make their
lives much easier if primary tags
I agree with Patrick, Niels, Sebastian and Anne.
Tag names in other languages only if at least one of these is true:
- it's an *official* translation by the competent authority (e. g. the
municipality)
- or the name is in *common use*
- or it's a *documented historical* name in another
20 matches
Mail list logo
