Add tools for occupant/non-civic address management

Currently, we offer data custodians and their data stewards no way of improving the occupants and points of interest they provide to location services. Most of these clients have no tools of their own other than a spreadsheet app and spreadsheet apps don't validate data against a user-defined schema! The DA group spends a substantial amount of time fixing up the addresses in these spreadsheets.

The current set of occupants and non-civic addresses are of low quality, incomplete, and limited to just a few categories of data. This reflects the primary purpose of the Geographic Sites Registry, the current intake tool, which is to load point data that is needed by an map app hosted by DataBC, into the BCGW.

With an Occupant/non-civic address editor, web service, and datastore, data custodians and stewards can easily improve their data. Occupant/non-civic address data integration should be included in any new automated geocoder data integration tool so that data managers can see their updates take effect within one day compared to the month or more it currently takes. Also the time and effort currently required to add new sources of occupant/non-civic address data is eliminated since the new data schema is fixed to those few metadata attributes actually required by the geocoder. The GSR allows clients to extend the schema to incorporate application-specific attributes.

The occupant/non-civic address web service can be implemented using GeoServer and OGC WFS protocol.

Current geocoder occupant and non-civic address data should be purged and only curated, high-quality address data should be populated, starting with data needed by MOTI to support OnRoute.

These tools will benefit all geocoder data suppliers particularly MOTI, whose OnRoute staff need to be able to add or update places of interest within a single day.