<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/15/2011 12:55 PM, yvecai wrote:<br>
<blockquote cite="mid:4EC2D1C5.7020906@gmail.com" type="cite">I
think it will be more useful in a local db maintained by local
people and used from local services aware of what is to be fixed
around.<br>
</blockquote>
<br>
There's a relatively new standard called Open311 which aims to
automate the reporting<br>
of issues to municipalities. I see a two way data connection
potential here, with benefits for both OSM and the various owners of
infrastructure.<br>
<br>
<br>
So the proposal on the table is:<br>
<br>
<hr size="2" width="100%">maintenance=ok<br>
No reasonable person would think anything is out of order
<br>
maintenance=broken<br>
The facility cannot perform its basic function.<br>
maintenance=needs_repair<br>
The facility can be used, but the main function is impaired:<br>
water may dribble out, the toilet may rock. But you can get
your job done.
<br>
<br>
maintenance:detail=________________________________<br>
A text description meant for the person who needs to fix it<br>
(e.g. "hornet nest in upper left corner of 3rd restoom from
right").
<br>
<br>
source:pkey=county_restroom_12345<br>
<hr size="2" width="100%"><br>
An enhanced osm mobile app could be used to set the maintenance
status.<br>
Reports could be generated for exchange with local authorities.<br>
<br>
I could do an intersection of "maintenance not ok", and the outline
for a particular<br>
city. Then send the resulting report to the local city manager, or
the local newspaper.<br>
<br>
Existing projects in this area focus only on broken stuff, not
mapping both the good and broken stuff.<br>
<br>
-Bryce<br>
<br>
<a href="http://download.geofabrik.de/osm/north-america/us/">http://download.geofabrik.de/osm/north-america/us/</a><br>
</body>
</html>