Changes between Version 5 and Version 6 of BluePrintBuildingAssessments

Timestamp:

02/23/11 07:32:00 (14 years ago)

Author:

Gavin Treadgold

Comment:

--

BluePrintBuildingAssessments

@@ -16 +16 @@
   * TODO
 
+* (1/immediate) Turk Geocoding of Addresses - initially no lat/long will be provided of the building assessed. It would be great to have a simple form interface that serves up an address from the database, and allows a (remote) user to use Google Maps to search the address and add latitude/longitude to the address to enable mapping. This can be done without providing access to any data other than the name of the building and the address. Note that this ideally needs to be a manual process as quite a few addresses will be ambiguous, and we may require some people with local knowledge to properly geocode them. This is essential to have immediate mapping of assessments - following SEP 4 it took 4-5 days to map, it will be a big win if we can do this near instantaneously (e.g. as soon as someone geocodes a submitted address).
+
+* (1/immediate) Map Geocoded Addresses - it is critical that we able able to map all geocoded assessments basically as they are entered. The real value in this system will be in the near realtime mapping (assessment will show on map once triage form entered and geocoded).
+
+* (1/immediate) Stats Reporting - we had a lot of requests for information about number of assessments undertaken, growth over time etc, and this will happen again. We would like a couple of key reports to be able to point public information officers and media to:
+  # A report providing assessment totals, and breakdown by assessment type and status (e.g. Level 1 (red, yellow, green) Level 2 (R1-R3, Y1-Y2, G1-G2).
+  # An hourly record of assessments - to provide a quick report of growth over time. My thought here is that an hourly cron job or similar would be run at the top of the hour that polls the number of assessments of each class, and records these in a table. The report would then present these so we can show activity over time. Highest priority is a table, graphs would be a bonus.
+
 * (2/24-36 hours) Full Data Entry Form - complete form as outlined in the documents. 
-
-* (1/immediate) Turk Geocoding of Addresses - initially no lat/long will be provided of the building assessed. It would be great to have a simple form interface that serves up an address from the database, and allows a (remote) user to use Google Maps to search the address and add latitude/longitude to the address to enable mapping. This can be done without providing access to any data other than the name of the building and the address. Note that this ideally needs to be a manual process as quite a few addresses will be ambiguous, and we may require some people with local knowledge to properly geocode them. This is essential to have immediate mapping of assessments - following SEP 4 it took 4-5 days to map, it will be a big win if we can do this near instantaneously (e.g. as soon as someone geocodes a submitted address).
 
 * (2/few days) Turk Council Identifiers - we need at least two council identifiers to enable Christchurch City Council to link the data we're collecting back to their business-as-usual information systems. Ideally want to support adding of n unique identifiers. Currently, there are two valuable identifiers we will need to link to. I may need to clarify what their ideal names are for export via CSV and the like. It would be good to have a simple turking process as above that pops up an address, and asks user to enter these IDs. These will be done be people here in Christchurch that have access to the councils mapping system to look up these IDs. This won't be a publis process, but will be similar to Turk Geocoding of Addresses.
   * 'prupi' - this is a reference to the property in the council system
   * 'gisratingid' - this is a reference to a polygon of the rating unit
+