Martin, the goal is not to make OSM fit to Wikidata needs (I'm not even sure what those needs are). The goal is to make it easier to consume OSM data. Pretty much every single OSM data consumer I spoke with complained of how difficult it is to use OSM data - let's try to help them.
For this specific case, the railroad stations consumer would probably want a single raiway station, not multiples, so they are easier to analyze, easier to query by matching it up with wikidata, etc. Railroad station can have multiple parts, but so do many other things, and we tend to put common things in a relation for them. Why would you want railroad stations tagged differently, and duplicate the same wikidata tag on every part of it? On Wed, Aug 8, 2018 at 12:13 AM Martin Koppenhoefer <[email protected]> wrote: > > > sent from a phone > > > On 7. Aug 2018, at 18:36, peterkrauss <[email protected]> > wrote: > > > > It seems the basic premise, > > "Wikidata references should be unique as possible", > > I will use your phrase from here. > > > I don’t see the need for this, what is the problem with having 2 osm > objects pointing to the same wikidata object? > The alternative seems to be either modify wikidata so that it suits OSMs > needs, or OSM so that it fits with the existing wikidata structure. > > cheers, > Martin > > > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
