Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion - re-adding or updating features as they change #13

Closed
slibby opened this issue Apr 3, 2017 · 2 comments
Closed

Discussion - re-adding or updating features as they change #13

slibby opened this issue Apr 3, 2017 · 2 comments

Comments

@slibby
Copy link
Collaborator

slibby commented Apr 3, 2017

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?

@mapmeld
Copy link
Owner

mapmeld commented Apr 19, 2017

pushing code which stores this as geoservice:objectid = {OBJECTID}

mapmeld added a commit that referenced this issue Apr 19, 2017
mapmeld added a commit that referenced this issue May 9, 2017
mapmeld added a commit that referenced this issue Jul 8, 2017
@mapmeld
Copy link
Owner

mapmeld commented Jul 26, 2017

we are currently not storing objectid on OSM

@mapmeld mapmeld closed this as completed Jul 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants