Changes between Version 31 and Version 32 of BluePrintBuildingAssessments
- 02/24/11 00:42:46 (11 years ago)
v31 v32 1 1 2 Building Assessments blueprint initially based on requirements for the February 2011 Christchurch earthquake. 2 3 3 4 == References == 4 5 This application is designed to implement the Building Safety Evaluation in a State of Emergency: Guidelines for Territorial Authorities. These guidelines were produced by the New Zealand Society for Earthquake Engineering, and were based on the US Applied Technology Councils ATC-20 assessment process. 5 6 6 * http://db.nzsee.org.nz/Publications.xml - see the section titled Bulding Safety Evaluation. 7 7 8 8 Note that the forms contained on the NZSEE webpage are outdated, as newer draft updated forms (that had yet to be published) were used for both the 4 SEP 2010 Canterbury, and 22 FEB 2011 Christchurch earthquakes. The forms that should be used, in addition to the updated guidelines, are contained below: 9 9 10 10 * http://www.kestrel.co.nz/files/NZSEE-BSE-201008-update.zip 11 == Locations Hierarchy == 12 * L0 = New Zealand (hard-coded) 13 * L1 = Canterbury (CAN) (Needs fixing!) 14 * L2 = Christchurch City Council 15 * L3 = Locality (Same as Wikipedia suburbs? Those are currently set as L2s, so need updating) 16 17 == Workflow == 18 * All buildings will first undergo a Triage report (mandatory fields only). 19 * Many buildings will have a Level 1 initially (external assessment) followed by a Level 2 (internal, structural), and may have multiple L1 or L2 over time. 20 * e.g. if there is another significant earthquake, the whole process will be restarted. 21 22 == Security == 23 * All assessment information should be protected to registered and admin-approved users. We will probably look at providing some public information from this site over time, but initially it needs to be closed and protected. 24 * DONE: Authentication requires Email Confirmation & Approval. Buildings data also requires the Buildings role. (FPB) 25 * Normal Authenticated users can only do the Geocoding task. 26 27 == !ToDo == 28 1. Improve the Usability of the main frontpage & the module homepage: http://nz.sahanafoundation.org/eden/building 29 2. Improve the Usability of the Geocoding application which will we'll put out a call for help on: http://nz.sahanafoundation.org/eden/gis/geocode_manual 30 * add help text 31 * hook into Google Geocoder (e.g. using the geocoder() function in controllers/gis.py) 32 3. Unique identifier visible on forms (Dominic?) 33 4. Provide the historic reports scheduled task 11 34 12 35 == Capabilities == … … 55 78 * Status: Form is printable in a near OCR-compliant way, although currently these forms won't be OCRable (fix by Monday? Fix will only work with new forms, not ones printed today) (FPB) 56 79 * To be able to pre-print forms, we'd need a dump of that database available to load. If we get this database then we can take a look at being able to do this. Map-based selection of records is on the roadmap, but is unlikely to get done within the timeframe for this response, I'm afraid. (FPB) 80 57 81 == Considerations == 58 82 * System may need to scale to potentially handle 100k assessment records after 1 month. 59 83 * This shouldn't be an issue. 60 == Security == 61 * All assessment information should be protected to registered and admin-approved users. We will probably look at providing some public information from this site over time, but initially it needs to be closed and protected. 62 * DONE (FPB) 84 * How many concurrent users are expected? 85 * Hard to know at this point. May be just a few to start with, but could scale to a 20-40 over time. But as we scale, more of these will be spending more time entering data e.g. as numbers increase, load on system won't increase in proportion, as it will take longer for users to enter full forms. 63 86 64 == Clarifications == 65 * Currently all Buildings are set to be within Christchurch L1. 66 * Do we want the list of L2s to be available as a dropdown? (list imported from Wikipedia, but only a couple have Lat/Lon currently) 67 * Level 2's are a different, more detailed report, so it actually needs to parallel the level 1 form. Many buildings will have a Level 1 initially (external assessment) followed by a Level 2 (internal, structural), and may have multiple L1 or L2 over time. Eg if there is another significant earthquake, the whole process will be restarted. 87 == Clarifications/Questions == 68 88 * Is the Postcode field useful? 69 89 * Yes. We may not use it straight away, but it could be useful. 70 * Will the Geocoding be done by anonymous users? 71 * Possibly, but only for lat/long from Google Maps/Earth. Ideally we'd have some logins that limits ACL just to that. 72 * We have have another class of users that are doing geocoding to council IDs (prupi, gisratingid). Will probably be separate usergroup to Google geocoders, as may have full access to data - they'll likely be council workers. But we may have to adjust this on the fly as it depends who we get here to do the geocoding. 73 * How many concurrent users are expected? 74 * Hard to know at this point. May be just a few to start with, but could scale to a 20-40 over time. But as we scale, more of these will be spending more time entering data e.g. as numbers increase, load on system won't increase in proportion, as it will take longer for users to enter full forms.