<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 9/2/22 16:19, Ian Steer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:00af01d81d74$8e1062c0$aa312840$@iinet.net.au">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoPlainText">>> I prefer hiking_scale:awtgs= as
you know that it is a hiking scale .. <o:p></o:p></p>
<p class="MsoPlainText">>> even if you don't know what
awtgs is.<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>Fair comment.<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">>> Routes are a different problem
.... while the worst one could be <o:p></o:p></p>
<p class="MsoPlainText">>> included .. what happens
if/when things change? Possibly better to leave it off?<o:p></o:p></p>
<p class="MsoPlainText">>> Consider that some routes have
alternatives, excursions...<o:p></o:p></p>
<p class="MsoPlainText">>><o:p> </o:p></p>
<p class="MsoPlainText">>One grade for the entire route,
which counts the worst bits of the whole distance, plus
separate grades for individual sections?<o:p></o:p></p>
<p class="MsoPlainText">><o:p> </o:p></p>
<p class="MsoPlainText">>& can we just write this up for
Oz use, or do we have to go down the full path of RFC /
Proposal / Voting? (Which will >undoubtedly be a Grade 5
trek!<o:p></o:p></p>
<p class="MsoPlainText">>:-))<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoNormal">I’m thinking “hiking_scale:awtgs=”. This
would have solved the problem of my well-meaning German friend
deleting my tags.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Since it is an Australian tag, I would have
thought adding it to the Australian Wiki would be sufficient.
</p>
</div>
</blockquote>
<p><br>
</p>
<p>No. Germans, French, English don't go looking for tags on every
countries wiki. The documentation should go on the main OSM wiki
so it can be found easily by anyone looking for it. <br>
</p>
<blockquote type="cite"
cite="mid:00af01d81d74$8e1062c0$aa312840$@iinet.net.au">
<div class="WordSection1">
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">With regard to users applying a grade using
this system, how about we use a “source:grade=” tag? Maybe if
the AWTGS grade has been sign-posted by the trail manager
(whoever that might be), it could be
“source:grade=as_signed”?? If a grade has been assigned by a
user, “source:grade=user” ??</p>
</div>
</blockquote>
<p><br>
</p>
If sources are state/suggested on the OSM wiki that would also
assist mappers trying to enter the data. <br>
</body>
</html>