<div dir="ltr">Hi Paul,<br><div><br></div><div>Thank you for your comments. </div><div><br></div><div>You may well be right in your analysis.... Recording a fountain out of order through the app is possible. I already count each fountain/refill cafe click per fountain in a server side mysql database (yes, I know osm numbers are mutable). . </div><div><br></div><div>This being said, I do think it makes sense to have a generalize solution... not everyone will use our app for surveying water fountains globally ... and I am sure the issue of staleness is universal. </div><div><br></div><div>For discussion purposes, it seems there are about 6.6 billion tag instances in the OpenStreetMap universe. If we decided to create a last updated meta data date for the year and month only (reducing to 2 Bytes) for 25% of the total tag universe, the uncompressed storage usage would be about 3GB or a 3% overhead. I think this overhead is worth considering. </div><div><br></div><div><a href="https://wiki.openstreetmap.org/wiki/Rarely_verified_and_third-party_data_staleness_in_OpenStreetMap">https://wiki.openstreetmap.org/wiki/Rarely_verified_and_third-party_data_staleness_in_OpenStreetMap</a> <br></div><div><br></div><div>Best regards,</div><div><br></div><div>Stuart </div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 6 Apr 2020 at 15:11, Paul Allen <<a href="mailto:pla16021@gmail.com">pla16021@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Mon, 6 Apr 2020 at 08:33, European Water Project <<a href="mailto:europeanwaterproject@gmail.com" target="_blank">europeanwaterproject@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div><div>In order to maintain/improve the data quality for our mobile application, I have been thinking about ways we can efficiently verify data for refill points for drinking water at fountains participating refill cafes, bars and other establishments. One idea I had was to create a map with possible stale refill cafes (and rural fountains) for volunteers to verify. </div><div><br></div><div>Please find attached a draft note for a feature proposal, which I have no idea if is even technically possible, for automatically adding a last verified date/creation date to specific keys. Maybe there is a better/more efficient way ?<br></div></div></div></blockquote><div><br></div><div>As others have pointed out, there are downsides to recording this in OSM. Others</div><div>have also suggested the use of a parallel database. And I'd point out the</div><div>additional burden of signing up to OSM/learning how to edit for ordinary</div><div>data consumers who want to flag that some location has stopped providing</div><div>free water.</div><div><br></div><div>The best way to do this would be in your own app. Allow users to confirm they</div><div>were able to get water or that the refill point is defunct. Record the data on your</div><div> app's server against an ID you assign for each location. Come up with a tag</div><div> for use in OSM that can be added to a refill point that gives a URL to check</div><div> against your app's server's information, say drinking_water:ewp_id</div><div>(and then wait for everyone to insist we don't have abbreviations in key</div><div>values and that it should be drinking_water:european_water_project_id).<br></div><div><br></div><div>It's going to need two QA packages. One to scan OSM for refill points and</div><div>flag those that aren't in your own db. One to scan your own db for defunct</div><div>refill points and flag to a human that they should be removed from OSM.</div><div><br></div><div>Oh, and it's going to need a db at your end. :)</div><div><br></div><div>-- <br></div><div>Paul</div><div><br></div></div></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>