OSM is the database. Not what any particular data consumer does with the data.
We don’t have control over what different data consumers do with the data. What we have control over is what data appears in the database. My position is that the data in the database should reflect on-the-ground reality as close as possible, so that data consumers can then make informed and meaningful decisions about how to present that data. If someone objects to how a particular data consumer presents the data, that’s between that person and the data consumer and shouldn’t have an impact on the OSM database, as long as the information in the database is correct and detailed enough for data consumers to make correct decisions. Cheers, Thorsten From: Graeme Fitzpatrick <[email protected]> Sent: Tuesday, 25 January 2022 12:04 To: Tom Brennan <[email protected]> Cc: OSM-Au <[email protected]> Subject: Re: [talk-au] Deletion of walking tracks/paths On Tue, 25 Jan 2022 at 11:26, Tom Brennan <[email protected] <mailto:[email protected]> > wrote: If the tracks were kept in OSM, but tagged appropriately so as not to appear in the rendering, & this is the big thing. Rendering needs to show that this track shouldn't be used. Maybe access=no gets a big red X across each entrance to say "closed". then when someone inevitably goes to add them, they would see the tracks there already. Notes as to why they have been removed could also be added. Possibly a description would be better than a note, because they carry across devices, rather than only being seen on OSM itself? Thanks Graeme
_______________________________________________ Talk-au mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-au
