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 | |
| 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 | |