[Tagging] Feature Proposal - RFC - trailblazed=poles;cairns
Bert -Araali- Van Opstal
bert.araali.afritastic at gmail.com
Tue Mar 9 11:36:11 UTC 2021
True Mira, its exactly what I noticed also. By just allowing marker=* to
be used on a way can solve that problem.
I understand, you tried to solve that in trails. But maybe it could be a
good idea to keep the tagging concept of trails more similar to other
"way" tagging and use what we have. You can also freely mix and use
markers / guidepost etc.... .
No need for trailblazed, less discussion. Even an opportunity to gently
deprecate or replace "marked_trail" and "trailblazed" (none of them
where accepted anyway). The presence of marker=* on the way designates
it as a marked trail or being trailblazed.
You can propose a change to marker=* (node & way) and make a nice
separate section with examples for trails ?
On 09/03/2021 12:08, Jaromír Mikeš wrote:
> Hello Bert,
> I like your idea,but I am not sure if the marker=* key perfectly fits
> here, makers as they are defined now are not meant for ways.
> I tend to extend the key which was from the beginning meant for trails ...
> BTW I just updated proposal page by description how poles and cairn
> are different from guidepost and osmc trail marking
> po 8. 3. 2021 v 17:24 odesílatel Bert -Araali- Van Opstal
> <bert.araali.afritastic at gmail.com
> <mailto:bert.araali.afritastic at gmail.com>> napsal:
> Have we all forgotten the marker=* key ?
> I know, it is defined to describe an individual marker, and mostly
> used in the context of marking some utility. The concept however
> and the way it is described perfectly fits the purpose here.
> If we allow, or maybe better said document it's possible use, on a
> way, it could perfectly fit the purpose here, if we use it on a
> trail, it opens the opportunity to tag the makers individually or,
> when used on a way it indicates these type of markers are used
> along this way.
> Much as we do and document other "attribute" keys for different
> Bert Araali
> On 08/03/2021 17:11, Marc_marc wrote:
>> Le 07.03.21 à 19:03, Jaromír Mikeš a écrit :
>>> I am proposing trailblazed=poles and trailblazed=cairns to get
>>> possibility tag trails which are marked by poles or by cairns
>>> https://wiki.openstreetmap.org/wiki/Proposed_features/trailblazed%3Dpoles;cairns <https://wiki.openstreetmap.org/wiki/Proposed_features/trailblazed%3Dpoles;cairns> <https://wiki.openstreetmap.org/wiki/Proposed_features/trailblazed%3Dpoles;cairns> <https://wiki.openstreetmap.org/wiki/Proposed_features/trailblazed%3Dpoles;cairns>
>> I find this tag too specific, it implies that another tag would be
>> needed for the bike routes and so for each mode where it could be necessary.
>> Wouldn't support:symbol do the job and be more integrated
>> with the symbol tag ?
>> support:symbol=pole =tree =house =rock =ground =street_cabinet
>> for cairn, it's the support for a symbol ? or the cairn itselft is
>> the marker without any symbol on it ? if so, maybe symbol=cairn
>> Tagging mailing list
>> Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>> https://lists.openstreetmap.org/listinfo/tagging <https://lists.openstreetmap.org/listinfo/tagging>
> Tagging mailing list
> Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging