Changes between Version 38 and Version 39 of BluePrint/GIS/GPSSharing


Ignore:
Timestamp:
12/08/10 16:58:15 (14 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/GIS/GPSSharing

    v38 v39  
    2828''The result would be an interactive map of great practical value for the program planning and control of the relief operation.''
    2929== Requirements ==
     30Desirable: It would be ideal if as much of the reference dataset as possible could be incorporated into the Base Map - !OpenStreetMap is ideal for this.
    3031
    3132=== Constraints ===
     
    3637 * System needs to be easy to backup to a single file (which could be a .zip of a .sql dump)
    3738 * Some data can be sensitive , so the system needs to be secure
     39  * We already have ACL within Sahana - extending this to map layers is already on the imminent roadmap
    3840
    3941== Use Cases ==
     
    116118''Link to vehicle-mounted GPS sending data back via GPRS/SMS''
    117119 * This could be through integration with [http://opengts.sourceforge.net OpenGTS]
     120
    118121== Implementation ==
     122
    119123=== High-Level Architecture ===
    120 It would be ideal if as much of the reference dataset as possible could be incorporated into the Base Map - !OpenStreetMap is ideal for this.
    121 
    122124Propose to:
    123125 * Set up a Virtual Machine containing all necessary software (to make it easy to install on any available PC - this setup may need replicating in several offices, although no need to sync between offices except via main !OpenStreetMap database at this time)
     
    125127 * Build a GUI within Sahana to allow the uploading/editing of GPX data
    126128
    127 === Other Options Considered ===
    128  * Garmin !MapSource
    129   - can't load more than 1 GPX file at a time
    130  * Google Earth
    131   - allows access to simple, known tools for manipulating the Waypoints to download an authoritative GPX
    132   - treat the basemap as more static (do an initial 1-time basemap inc contours & follow this up with a process for updating the contours.osm with Osmosis)
    133   - doesn't work offline, although could use a KML super-overlay when offline:
    134    * http://svn.openstreetmap.org/applications/utils/wms2kml/
    135    * !GeoServer can produce the !SuperOverlay from cascaded WMS:
    136     * http://geoserver.org/display/GEOS/GSIP+47+-+WMS+cascading
    137     * http://docs.geoserver.org/stable/en/user/googleearth/index.html
    138    * [http://wiki.openstreetmap.org/wiki/Mod_mapnik_wms mod_mapnik_wms] to create the WMS
    139  * [http://depiction.com Depiction]
    140   * Data primarily only shareable with other Depiction users which means hard to gain traction even within an organisation let alone for interagency work.
    141   * Installation requires admin rights on the PC, which many field staff won't easily have access to - again lowering the ability to get wider adoption.
    142   * Can't create new Depictions or use Base Maps at all without an active Internet connection.
    143   * Revealers seem very gimmicky: I don't find them useful & they're really hard to use in practise (I just wanted a 'full-screen option').
    144    * !GeoExplorer already has the ability to dynamically edit layer opacity, which is the 1 thing I'd use them for.
    145   * Licensing costs push this beyond local partners to whom we want to handover the tools when moving from Response -> Recovery -> Mitigation/Preparedness (USD 200/machine + add-ons, such as $50 just for icons that come free with Sahana!)
    146   * No support for KML (or GeoRSS)
    147   * No ability to edit the !OpenStreetMap base layer which adds so much value to these maps
    148   * Adding Elevation data is clumsy (fairly easy to make this 'seamless' ;) )
    149 
    150 === Detailed Architecture Proposal ===
     129
     130
    151131=== Sahana ===
    152132The current GPX layer interface is probably insufficient.
     
    226206  * [http://www.mkgmap.org.uk/ mkgmap]
    227207
     208=== Other Options Considered ===
     209 * Garmin !MapSource
     210  - can't load more than 1 GPX file at a time
     211 * Google Earth
     212  - allows access to simple, known tools for manipulating the Waypoints to download an authoritative GPX
     213  - treat the basemap as more static (do an initial 1-time basemap inc contours & follow this up with a process for updating the contours.osm with Osmosis)
     214  - doesn't work offline, although could use a KML super-overlay when offline:
     215   * http://svn.openstreetmap.org/applications/utils/wms2kml/
     216   * !GeoServer can produce the !SuperOverlay from cascaded WMS:
     217    * http://geoserver.org/display/GEOS/GSIP+47+-+WMS+cascading
     218    * http://docs.geoserver.org/stable/en/user/googleearth/index.html
     219   * [http://wiki.openstreetmap.org/wiki/Mod_mapnik_wms mod_mapnik_wms] to create the WMS
     220 * [http://depiction.com Depiction]
     221  * Data primarily only shareable with other Depiction users which means hard to gain traction even within an organisation let alone for interagency work.
     222  * Installation requires admin rights on the PC, which many field staff won't easily have access to - again lowering the ability to get wider adoption.
     223  * Can't create new Depictions or use Base Maps at all without an active Internet connection.
     224  * Revealers seem very gimmicky: I don't find them useful & they're really hard to use in practise (I just wanted a 'full-screen option').
     225   * !GeoExplorer already has the ability to dynamically edit layer opacity, which is the 1 thing I'd use them for.
     226  * Licensing costs push this beyond local partners to whom we want to handover the tools when moving from Response -> Recovery -> Mitigation/Preparedness (USD 200/machine + add-ons, such as $50 just for icons that come free with Sahana!)
     227  * No support for KML (or GeoRSS)
     228  * No ability to edit the !OpenStreetMap base layer which adds so much value to these maps
     229  * Adding Elevation data is clumsy (fairly easy to make this 'seamless' ;) )
     230
    228231----
    229232[wiki:BluePrintGeographicInformationSystems GIS BluePrints]