[Tagging] data model (was: Re: Feature Proposal - RFC - shop as post-partner)

Bert -Araali- Van Opstal bert.araali.afritastic at gmail.com
Sun Feb 28 13:40:25 UTC 2021


Yep, I was reading them but essentially what you do is create a many to 
one or many to many relationship. This could be possible in a many to 
one relationships, all the top level keys apply to all the attribute 
tags.  But how are you going to manage this when you get multiple ones.

F.i. you could  say amenity=restaurant;post_office;butcher (and where 
does this stop, at

Next brand=brand A; brand B; brand C; brand D;,

Operator= operator A; operator B;

Which relates or is linked to which ?

To make that clear I would need

restaurant:brand=brand A; brand D;
post_office:brand= brand C;
restaurant:operator= operator C;
.... this keys list are going to be very long and longer and longer

Where in the contrary, if we would allow nodes as being just data 
containers and use relations would be much more simple and powerful. 
Maybe we should introduce an additional key to indicate that these data 
container nodes are not intended to provide additional spatial 
information, like data_node=yes ?
In that situation you remain with one spatial node that provides the 
primary purpose of the location and many nodes that are just data 
containers.  The pure existence of these data nodes should attend a data 
consumer that he has to look for a relation or a spatial link to decide 
how it needs to be precessed or rendered.
Or, if we don't want a specific data_node=yes one could introduce a way 
called "data_link", linking all the data nodes with the single spatial 
node but not representing any spatial feature ?

Greetings,

Bert Araali

On 28/02/2021 14:04, Georg wrote:
>
>
> Am 2021-02-27 um 23:03 schrieb Bert -Araali- Van Opstal:
>
>> - we want to evolve into a model with millions of unique keys trying to
>> define all kinds of combined uses
>
> We do not need millions of keys, nor values - the amount of keys &
> values won't change much. The main difference would b, e that we can use
> multiple values for one single node; please see the posts of Martin
> (2021-02-27 22:08) and me (2021-02-28 11:28)
>
> _______________________________________________
> 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/20210228/c86de4cf/attachment.htm>


More information about the Tagging mailing list