You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With documented geocoded workflows, there is now an expectation that the gaiaDB is extended to include geocoded addresses.
While the gaiaCore tools are one possible way for populating the gaiaDB with geocoded address data, gaiaDB should be geocoder-agnostic.
We need to specify a target for geocoded addresses. If user A uses gaiaCore geocoder, and user B uses something else, they should both be storing data in the correct location and with similar (overlapping where necessary) schema.
The text was updated successfully, but these errors were encountered:
With documented geocoded workflows, there is now an expectation that the gaiaDB is extended to include geocoded addresses.
While the gaiaCore tools are one possible way for populating the gaiaDB with geocoded address data, gaiaDB should be geocoder-agnostic.
We need to specify a target for geocoded addresses. If user A uses gaiaCore geocoder, and user B uses something else, they should both be storing data in the correct location and with similar (overlapping where necessary) schema.
The text was updated successfully, but these errors were encountered: