| 55 | | === Map elements between EDXL-SITREP and EDXL-RM === |
| 56 | | ''Not added to GCI spreadsheet -- time required says a week.''[[BR]] |
| 57 | | Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]] |
| 58 | | '''Specific : ''' There are several elements within the [http://tinyurl.com/bn9nxty | EDXL-SITREP] data standard that are identical to that of [http://docs.oasis-open.org/emergency/edxl-rm/v1.0/EDXL-RM-SPEC-V1.0.pdf | EDXL-RM]. The objective is to create a descriptive table of those elements that a programmer can use to develop a set of procedures to strip the RM data from SITREP to manage records in the relational database [[BR]] |
| 59 | | '''Measurable : ''' Requires diligently investigating each and every data element then comparing them with the two data standards SITREP and RM. Requires knowledge of data types and XML. If not, this exercise will help the student learn about XML and data standards [[BR]] |
| 60 | | '''Attainable : ''' [[BR]] |
| 61 | | Step 1 :: Go through EDXL-RM and EDXL-SITREP documentations [[BR]] |
| 62 | | Step 2 :: create example files to get an understanding of the data and structure [[BR]] |
| 63 | | Step 3 :: develop the table with RM and SITREP elements with a description [[BR]] |
| 64 | | Step 4 :: develop a simple XSL file to strip the RM data from SITREP [[BR]] |
| 65 | | '''Relevant : ''' Applies to Sahana interoperability policy. Given that Eden does support resource and incident management, it is important to derive the response resources and resource requirements from situational reports. This function would help automate some of those data extraction functions. That requires integrating the SITREP and RM components with underlying Eden schema [[BR]] |
| 66 | | '''Time-bound : ''' The exercise of understanding the data standards and mapping the elements should not take more than one week. developing a XSL to test the mapping may take another week, depending on the level of expertise with XML. (NB this is far too large a task for GCI. -- Pat)[[BR]] |
| 67 | | '''Evaluate : ''' The mapping table is the determining output. However, the example RM and SITREP files are also required. [[BR]] |
| 68 | | '''Reevaluate : ''' If the XSL transformation is developed, then the mapping can be tested with the sample RM and SITREP files [[BR]] |
| 69 | | |
| 70 | | == Intermediate Tasks == |
| 71 | | |
| 72 | | === Feature Enhancements === |
| 73 | | * Fix UI issues, add features, provide user-requested enhancements. |
| 74 | | * You can pick from these [/report/21 feature requests]. |
| 75 | | |
| 76 | | === OSM Importer UI [GCI] === |
| 77 | | |
| 78 | | ==== Current Status ==== |
| 79 | | * There is an import stylesheet for .osm files: static/xslt/import/osm.xsl |
| 80 | | * This currently has hard-coded mappings between OSM admin levels & Sahana admin levels |
| 81 | | * http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative#10_admin_level_values_for_specific_countries |
| 82 | | * There is an S3ImportPOI method to allow features to be extracted from either an uploaded .osm file or an OSM mirror: |
| 83 | | * https://github.com/flavour/eden/blob/master/modules/s3/s3gis.py#L7938 |
| 84 | | * this is accessed from the 'Import from OpenStreetMap menu option in /eden/gis |
| 85 | | |
| 86 | | ==== Enhancements Needed ==== |
| 87 | | 5 separate GCI Tasks here: |
| 88 | | 1. We need to add the Sahana UUID to these features in the OSM database. |
| 89 | | * This is needed so that we can do deduplication on subsequent imports (the OSM ID is insufficient for this as it can change over time) |
| 90 | | * This means we need to read the OSM credentials (currently a deployment_setting in 000_config.py) & do a REST API call to the main OSM database with the modified feature(s) |
| 91 | | 2. Move the OSM credentials from a global 000_config.py deployment_setting to a per-user setting (component resource of db.auth_user) |
| 92 | | 2. We would like to be able to control which features are imported from this UI (currently this is a deployment_setting in [000_]config.py - that should become the list of avaialble options rather than the absolute list) |
| 93 | | 3. We would like to be able to download features for a Location from main OSM database |
| 94 | | * We want to use the Polygon (falling-back to BBOX (min_lat, max_lon, etc)) to trigger a download of a suitably-filtered .osm file via the [http://wiki.openstreetmap.org/wiki/Overpass_API Overpass API] |
| 95 | | 4. We would like to be able to download features for a Polygon |
| 96 | | * Provide a map window with a Polygon selector tool which then triggers a download of a suitably-filtered .osm file via the [http://wiki.openstreetmap.org/wiki/Overpass_API Overpass API] |
| 97 | | |
| 98 | | === Fix a Hard Ticket === |
| 99 | | http://eden.sahanafoundation.org/report/1 |
| 100 | | Pick a bug report from http://eden.sahanafoundation.org/report/1, try to reproduce the issue in a local instance, fix the problem and submit a patch to the ticket on Trac, then notify the Sahana-Eden mailing list about your patch for verification. |
