[OSM-talk] [Talk-GB] Improving ref=* documentation

[François Lacombe]

Le jeu. 5 août 2021 à 13:31, Mateusz Konieczny via talk <
talk at openstreetmap.org> a écrit :

>
>
> Aug 5, 2021, 10:38 by colin.smale at xs4all.nl:
>
> On 08/05/2021 10:07 AM Mike Baggaley <mike at tvage.co.uk> wrote:
>
> I suggest using name:signed and ref:signed to hold incorrectly signed
> values. You can then have name:signed=yes, name:signed=no and
> name:signed=<signed name>. I would suggest that if used to hold a value
> other than yes/no, then source:name and/or source:ref ought to also be
> specified so that it is clear why the name/ref is not the same as the sign.
>
>
> Problem solved, then. Thanks for the clear and pragmatic solution. ref and
> name carry the official, proper values, and if a sign disagrees, put that
> in name:signed or ref:signed together with information about the sources.
>
> What's not to like?
>
> This allows two different renderings to be derived from the same data -
> one using the official values, and one using the "as-signed" values. The
> consumer can choose, according to their specific use case. We provide the
> data for both.
>
> Note that we have also
> https://wiki.openstreetmap.org/wiki/Key:unsigned_ref for cases
> where ref is assigned but never signed with a clearly visible reassurance
> marker.
>
> (for some reason local road authority may post some barely visible signs,
> but they are
> unreadable even while cycling and invisible when driving and noone uses
> them to
> identify roads, such codes are appearing only in the  official
> documentation
> See
> https://wiki.openstreetmap.org/wiki/File:Barely_signed_road_reference_code.jpg
> where unsigned_ref is fitting
> Though I admit that unsigned_ref is a poor name for one that can be
> actually signed
> by some weird road authority officials... But noone really expected that.
> )
>

I don't get why ref=* can't always hold the value read on ground.

If we're able to criticise the validity of a reference, and then correct it
in some situations, it's only regarding a precise rule that MUST be
documented.
>From this perspective, consolidated, validated, corrected, extended,
whatever value may go in a specific ref:* key, not in ref=*

ref=* can't hold all rules, schemes, examples in the world, a dedicated
ref:*=* for each situation can.
That's what we do with ref:FR:*

My 2 cts

François
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20210805/87a65221/attachment-0001.htm>