| 24 | | * add an HTML5 GeoLocation option ('Current Location') |
| 25 | | * 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) |
| 26 | | * display the geocoder results on a map for visual confirmation that the correct result has been returned |
| 27 | | * if we have admin boundaries available then the Lat/Lon provided can be validated against the selected Lat/Lon |
| 28 | | * if we have admin boundaries available then the correct hierarchy can be filled-in automatically if just the Lat/Lon are provided |
| | 24 | * Add an HTML5 !GeoLocation option ('Current Location') |
| | 25 | * we should use a 'nearby' algorithm (like gis.get_features_in_radius()) to re-use existing locations rather than adding a new one each time. |
| | 26 | * e.g. pr/person/presence could be recorded automatically upon login |
| | 27 | * 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) |
| | 28 | * Display the geocoder results on a map for visual confirmation that the correct result has been returned |
| | 29 | * If we have admin boundaries available then the Lat/Lon provided can be validated against the selected Lat/Lon |
| | 30 | * If we have admin boundaries available then the correct hierarchy can be filled-in automatically if just the Lat/Lon are provided |
