Changes between Version 22 and Version 23 of BluePrint/GIS/GPSSharing

12/08/10 16:44:21 (14 years ago)
Fran Boon



  • BluePrint/GIS/GPSSharing

    v22 v23  
    2121== Requirements ==
     24== Use Cases ==
     26=== Scenario 1: GPS coordinates exchange within the office ===
     29 * An aid worker returns from the field after having assessed the damage in a particular area/needs of the population and includes the GPS coordinates in her report. Coordinates are not shared.
     31''To work in the field, it is sometimes difficult to get appropriate access to information, e.g. where to find a well with clean drinking water to cater thousands of people, for example, as recently needed in Haiti. A member of Caritas Haiti could now enter data with GPS location on where there are intact wells, which would be saved to the map. The same map could be used later on, e.g. by a group of water experts wanting to examine the quality of the water to easier find the wells - with the help of navigation tools in their cars. They could even upload up to date information on the quality of the water or potential repair needs to the map.''
     34 * Aid worker uploads a GPX or spreadsheet file to a webpage, with the opportunity to provide metadata (most critically the category/name. Time & Person are defaulted automatically)
     35  * There should be an option for uploaded data to be validated by an admin before publishing
     36 * Users can download data by selecting different layers (e.g. all broken bridges) retrieved in different file formats (e.g. GPX to download back to the GPS or KML to share with users of Google Earth)
     38Implementation Notes:
     39 * There are already GPX/KML export stylesheets in Eden & the S3XRC engine allows URL-based filtering to make selections.
     40  * ''We could usefully develop a little UI to provide a simple front-end for this'' (either in Ext to integrate with the current client or else a 'cuddly' one in jQuery like Maps-on-a-Stick)
     41 * ''Provide a UI to edit the uploaded Waypoints before importing into the database'' (a GPX file often just contains the numeric IDs & the metadata is stored in a notebook with pen/paper, so the import stylesheet is less useful)
     42  * Ext Store to upload data to (fields the same as gis_waypoint: name, description, category)
     43  * Ext Table with Editable Rows to edit the data in spreadsheet-style (fast for users & familiar interface)
     44  * AJAX call to import to the gis_waypoint table via the gis/waypoint controller
     45 * Uploaded data needing to be admin-validated is already in the Eden roadmap for core ACL functionality, so is probably not usefully developed as part of RHoK
     46 * CSV/OpenOffice data can already be uploaded to Eden, although, inevitably, the structure needs to be quite specific. There is also a [ graphical wizard for importing Excel spreadsheets] which allows field mapping, etc. However this isn't yet robust...''making this tool robust would be useful both for this project & for other Sahana applications''.
     47 * Currently the editing of features using the map is clumsy, we could really use the editing toolbar to be working (needs to be enabled in modules/ or use one from [ GeoEditor]) to allow Features to be:
     48  * Added
     49   * Have a popup to select the type of resource being created.
     50   * Then open up another popup to add the relevant details? Just add Name initially & add this feature to a worklist to go back & fill out other details?
     51  * Edited
     52   * Need to add an 'Edit' button to the existing Popups? Separate toolbar button?
     53  * Moved
     54   * Simply do an AJAX call to update the coordinates
     55  * Deleted
     56   * Need to add a 'Delete' button to the existing Popups? Separate toolbar button?
     57   * Simply do an AJAX call to delete the record (& then remove the feature from the current display)
     58 * Provide UI to access the 'copy' functionality from S3XRC to create hospitals/offices/warehouses/activities from Waypoints & vice versa
     59 * Complete the per-category Icons for both display & GPX export (currently icons are per-resource, although work has started to rectify this)
     61=== Scenario 2: Data analysis ===
     62Want to be able to view the different layers together to improve Decision-Making.
     64''The Operation coordinator needs to see location and distribution progress of only Emergency Shelters to see if there are any gaps. Solution: being able to toggle layers on/off independently, e.g. topographic layer-demographics-waypoints etc. and extract and create piecharts from metadata.''
     66Implementation Notes:
     67 * Contours are a key piece of information here. These can be rendered in local OpenStreetMap tiles
     68  * Help getting this working would be much appreciated (must be something small that we're missing!):
     69 * We want to be able to [ display graphs on top of the map]
     70  * Small graphs as Icons
     71  * Larger graphs within Popups
     72  * [ Heat Maps]
     73 * We don't currently have tables for Demographic data
     74  * Would be useful to add models for these. What's a good source of fields to use?
     76=== Scenario 3: Data exchange between offices ===
     78 * HQ needs to write a donor report & wants to be able to show the donor(s) the locations of the Project Activities
     79 * Country office is doing security planning & wants to have all security incidents visible on a single map
     80 * Many different agencies are working in a location & wish to share a common operational picture across the cluster (programme) or all-agencies (security)
     83 * Synchronize the data between Sahana instances in a controlled manner
     84 * Import & Export data using Open Standards (this is usually compressible text files, which are easy to email)
     86Implementation Notes:
     87 * There is already a core synchronization engine in Eden which supports Push (to allow a 'server' behind NAT to share data with a central portal) & 'Pull' (to allow a 'server' on an intermittent connection to retrieve data when it is connected)
     88 * This engine can also be used to control the Import/Export of data to/from Open Standards using XSLT Stylesheets.
     89  * Alternatively the data can be imported/exported manually using the same stylesheets
     90  * Import stylesheets for KML/GeoRSS are yet to be developed:
     92=== Scenario 4: Printing a Map ===
     93''Would like to see A4 District-level maps with names and boundaries of sub-districts (e.g. Tehsils for Pakistan) that we can insert text and tables onto top of.''
     94 * There is a basic print.css stylesheet to allow simple screen prints which could possibly be enhanced.
     95 * There is basic support for using the GeoExt client libraries to interface with the MapFish PDF print library (e.g. as-embedded into GeoServer), however this could use polishing.
     96 * Would be great to allow users to have better layout control of where Legends, Scalebars & Compasses are positioned to get them out of the way of the meaningful data
     97 *
    2298== High-Level Architecture Proposal ==
    2399It would be ideal if as much of the reference dataset as possible could be incorporated into the Base Map - !OpenStreetMap is ideal for this.