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
One of the benefits of using authoritative data in this workflow is the assumption that a local municipality has the most up-to-date data and correct naming/attribution for most features. It appears that the GeoServices tool will allow a user to rapidly add a bunch of features, but what happens when attributes or geometries for those features change?
Is there any way to retain a link between the source feature and the node/way created in OSM? Just brainstorming here, but maybe since osm does not restrict tagging, a tag with source_oid=objectid or something?
The text was updated successfully, but these errors were encountered:
One of the benefits of using authoritative data in this workflow is the assumption that a local municipality has the most up-to-date data and correct naming/attribution for most features. It appears that the GeoServices tool will allow a user to rapidly add a bunch of features, but what happens when attributes or geometries for those features change?
Is there any way to retain a link between the source feature and the node/way created in OSM? Just brainstorming here, but maybe since osm does not restrict tagging, a tag with
source_oid
=objectid
or something?The text was updated successfully, but these errors were encountered: