Skip to content

Location Services Architecture

James Rae edited this page Nov 18, 2015 · 1 revision

While not tied to the mapping API, the location services are tied to GIS-ish stuff so for now will reside in the geoApi library. We utilize the GeoGratis geographical names service and geolocation service

The section will require an initialization, in particular:

  • storing URLs to the location services, which are provided by the config object
  • pre-loading any domain-of-value lists from the services
    • province codes
    • concise codes (these group things into common categories, like Lakes, Roads, or Landmarks)

As well, the section should expose a search function that supports

  • Name search (including partials)
  • Forward Sorting Area search
  • Lat/Long search
  • Province filter
  • Concise code filter
  • Extent filter
  • Radius filter (for FSA and Lat/Long searches only)
  • Suggested results when no direct hits are found

The RAMP geoSearch module is already written in Angular.js and is probably a good starting point (UI stuff that will not reside in geoApi can also be happily stolen).