Hi Marc, I am convinced survey:date is not the solution for maintaining large swathes of OpenStreetMap data. Nor do I think putting a survey date at a per tag level is realistic or workable.
Best regards, Stuart On Mon, 6 Apr 2020 at 12:24, Marc M. <marc_marc_...@hotmail.com> wrote: > Hello, > > Le 06.04.20 à 09:31, European Water Project a écrit : > > I have been thinking about ways we can efficiently verify data > > here's my workflow : > - once a year, I query all poi (bar, restaurant, shop) within my comfort > zone, and check all tag again. > if nothing change, I update the tag survey:date=YYYY-MM on it > > of course the main problem occurs when everything is not checked (does > the wifi work?) or verifiable (does the fire hydrant work?). > for this last point, during the proposal on fire hydrants, we had agreed > to use operational_status:date, for this king of technical object, it's > fine. > for a test of the restaurant wifi, it's not ideal, maybe not even desirable > for opening jours, I don't know what to use. > seeing the restaurant (source=survey) doesn't say clearly what was seen, > was it just the fact that the restaurant was open? also the name ? > or all the tags like I do ? > of course one solution is to put lots of tag1:date tag2:date > I hate this because the next contributor will modify tag1 without > necessarily modifying tag1:date (it's the same problem with the source > tag on objects that informs the source used by the one who added the > object and not the source of the current object, with sometimes big > difference such as a change of poi type) > > Regards, > Marc > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging