Treat locally-edited features differently

posm / posm-carto

A simple CartoCSS style for POSM, highlighting HDM features.

BSD 3-Clause "New" or "Revised" License

8 stars 2 forks source link

Treat locally-edited features differently #8

Open mojodna opened 8 years ago

mojodna commented 8 years ago

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

Depends on https://github.com/AmericanRedCross/posm/issues/129

hallahan commented 8 years ago

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 commented 8 years ago

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

mojodna commented 8 years ago

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 commented 8 years ago

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 commented 8 years ago

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.