[Tagging] Feature Proposal - RFC - information=qr_code

[Volker Schmidt]

My objection was against tourism=qr_code. Because it would conflict with
other uses of tourism=* on the some object. For example tourism=attraction
or tourism=information (maps, boards)

On Mon, 20 Jun 2022, 17:52 Anne-Karoline Distel, <annekadistel at web.de>
wrote:

> I only tried one of them and the text was short enough and might fit in
> the constraints of the inscription field. However, at LlanfairPG train
> station (that's the one with the 48 letter name), you could listen to
> the name being pronounced, so that wouldn't go into the inscription field.
>
> The url is already part of the proposal.
>
> Anne
>
> On 20/06/2022 14:33, Martin Koppenhoefer wrote:
> > as the information in the code is static, why not adding the url in the
> qr code with the url=* tag? If there is no url, we could add the content of
> the decoded qr tag to a tag (inscription:qr=* maybe?)
> >
> > Cheers Martin
> > _______________________________________________
> > Tagging mailing list
> > Tagging at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/tagging
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220620/dc4f211d/attachment.htm>