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

Show information about latest state of feature #151

Open
planemad opened this issue Apr 28, 2017 · 1 comment
Open

Show information about latest state of feature #151

planemad opened this issue Apr 28, 2017 · 1 comment

Comments

@planemad
Copy link

planemad commented Apr 28, 2017

When one is inspecting a bad change, it is very helpful to know if the feature had been later modified/corrected by another user. This helps a reviewer take appropriate action if needed.

Current workflow

screen shot 2017-04-28 at 11 48 07 am

https://osmlab.github.io/changeset-map/#48202080

To find out if this feature has been deleted, the user currently needs to check the OSM object page https://www.openstreetmap.org/way/489873496/history

screen shot 2017-04-28 at 11 50 15 am

Expected workflow

On clicking the feature in changeset-map, indicate if a newer version of the object exists or has been deleted. This will allow the user to jump to inspect the latest changeset involving this feature or know that the issue is resolved without needed to check an external site. This saves considerable time when cycling through various features of a changeset.

Mediawiki watchlist does this by showing if the change is part of the current state of the page.

cc @batpad @ajithranka @rasagy @manoharuss

@batpad
Copy link
Collaborator

batpad commented Apr 28, 2017

Thanks for the ticket @planemad .

I imagine we would do this by querying some API for the feature id that would let us know if there were further edits made to it.

Let's explore possibilities.

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