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

Treat locally-edited features differently #8

Open
mojodna opened this issue Mar 29, 2016 · 5 comments
Open

Treat locally-edited features differently #8

mojodna opened this issue Mar 29, 2016 · 5 comments

Comments

@mojodna
Copy link
Member

mojodna commented Mar 29, 2016

Check for user=POSM to identify features that have local edits.

Depends on posm/posm#129

@hallahan
Copy link

hallahan commented Apr 1, 2016

Note, I don't know if this is the best long term solution. Finding a way to let editors use their real OSM user name in POSM would be really good. We just haven't thought of the solution to this yet...

@almccon
Copy link
Contributor

almccon commented May 10, 2016

What's our current thinking on this issue, @mojodna & @hallahan?

@mojodna
Copy link
Member Author

mojodna commented May 10, 2016

Uhhh...

I defer to @dalekunce.

With a recent extract, the username associated with "local" edits is dkunce_import (and can be pulled in via osm2pgsql w/ the --extra-attributes option (in addition to --hstore-all)).

@dalekunce
Copy link

I redefer back to @mojodna

using my import account is fine as an extra attribute I guess for now.

Maybe we could just watch for all updates after the extract happens?

@hallahan
Copy link

We are including metadata in OpenMapKit Server showing that the edits were done with OpenMapKit, as well as ODK data endpoints. You can use this changeset info to determine edits were made with OMK, and therefore POSM.

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

4 participants