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


Ignore:
Timestamp:
03/21/11 11:12:29 (11 years ago)
Author:
Fran Boon
Comment:

Use Cases

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/GIS/LocationSelector

    v22 v23  
    2121   * A Conversion tool is available to convert from !Deg/Min/Sec to Decimal Degrees
    2222
     23== Use Cases ==
     24=== Locate a Site ===
     25 * Enter the Address & use a Geocoder to open a map view to allow precise selection of Lat/Lon
     26  * e.g. http://www.addressfix.com
     27 
     28=== Locate a Person ===
     29==== Link them to a Site ====
     30 * Set a Staff member's Base Location to their Office Address
     31 * Check-in to a site
     32
     33Both would want to select Site from a Dropdown (ideally Combobox)
     34
     35==== Select their Home Address ====
     36 * Set a Volunteer's Base Location to their Home Address
     37
     38Like Locate a Site
     39==== Provide a WayPoint ====
     40 * Update Presence
     41
     42Maybe Lat/Lon entry (e.g. automated)
    2343== !ToDo ==
    2444 * Redesign the !Look/Feel to make it more usable
     
    3555  * display the results on a map for visual confirmation that the correct result has been returned
    3656 * Set the map entry default !lat/lon/zoom based on the selected Level in the Hierarchy (assumes we have at least Centroid information available, ideally use Polygons where we have them)
    37  * Display the geocoder results on a map for visual confirmation that the correct result has been returned
    38  * [wiki:BluePrintGISGeolocator Geocoder] lookup of a Street Address (port from old Selector)
    39   * Use more Geocoders than just Google
     57 * [wiki:BluePrintGISGeolocator Geocoder] lookup of a Street Address
     58  * port some code from old Selector
     59  * Display the geocoder results on a map for visual confirmation that the correct result has been returned
     60   * Use this for UI example: www.addressfix.com
     61  * Use more back-end Geocoders than just Google
    4062 * If we have admin boundaries available then the !Lat/Lon provided can be validated against the selected !Lat/Lon
    4163 * If we have admin boundaries available then the correct hierarchy can be filled-in automatically if just the !Lat/Lon are provided