Changes between Version 19 and Version 20 of BluePrint/GIS/LocationSelector

Timestamp:

03/21/11 07:50:03 (14 years ago)

Author:

Fran Boon

Comment:

--

BluePrint/GIS/LocationSelector

@@ -18 +18 @@
   * New locations have their name automatically set from that of the Record, if no other name is provided
  * [wiki:BluePrintGISGeolocator Geocoder] lookup of a Street Address
- * Map-based lookup of Lat/Lon
- * Manual entry of of Lat/Lon (either from a GPS or looked up in an online resource like Wikipedia) 
-   * A Conversion tool is available to convert from Deg/Min/Sec to Decimal Degrees
+ * Map-based lookup of !Lat/Lon
+ * Manual entry of of !Lat/Lon (either from a GPS or looked up in an online resource like Wikipedia) 
+   * A Conversion tool is available to convert from !Deg/Min/Sec to Decimal Degrees
 
 == !ToDo ==
@@ -39 +39 @@
   * e.g. pr/person/presence could be recorded automatically upon login 
   * display the results on a map for visual confirmation that the correct result has been returned
- * 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)
+ * 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)
  * Display the geocoder results on a map for visual confirmation that the correct result has been returned
  * Use more Geocoders than just Google
- * If we have admin boundaries available then the Lat/Lon provided can be validated against the selected Lat/Lon
- * If we have admin boundaries available then the correct hierarchy can be filled-in automatically if just the Lat/Lon are provided
+ * If we have admin boundaries available then the !Lat/Lon provided can be validated against the selected !Lat/Lon
+ * If we have admin boundaries available then the correct hierarchy can be filled-in automatically if just the !Lat/Lon are provided
  * Experiment with downloading all Locations at startup (into a [http://api.jquery.com/data/ jQuery Data store]) & filtering client-side, or maybe downloading just the full next level of hierarchy proactively (e.g. we've got the L0 selected, we have the L1 dropdown populated accordingly...we could download *all* L2s within the L0 ready for when the L1 is selected & then filter the downloaded L2 data to those within the relevant L1 to populate the L2 dropdown with). This would also provide an automatic cache (within the page only).
  * Extend the location_id() API to support controlling which levels of hierarchy we're interested in for a resource (some may be only interested in the province, whereas others may need a precise location)