-
Notifications
You must be signed in to change notification settings - Fork 101
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
Support Maproulette cooperative challenges #1340
Comments
A few additional notes Maybe start with the Tag Fix Challenges (docs), which are a lot easier to prepare and easier to apply. Hey also fit neatly in what was talked about in #585 (comment) with an However, it might be worth considering if the tag fix challenge data model should be extended first, see maproulette/maproulette3#2299 On the data format of cooperative challenges: If this format where to be used more, I think that would be a good time to also consider making the data format easier to access. The whole osc+base64 (see docs) create quite a big entrance barrier. |
If there's a desire to support Tag Fix challenges, maybe that should have it's own ticket. We wouldn't want to confuse closing that issue with full support for Cooperative challenges. |
Description
Maproulette cooperative challenges are special challenges that give the user data to work with, eg a new node.
@mvexel will be able to better explain, with JOSM it looks like there is an extra request, eg:
http://127.0.0.1:8111/import?new_layer=false&layer_name=MR%20Task%20215603166%20Changes&layer_locked=false&download_policy=&upload_policy=&url=https://maproulette.org/api/v2/task/215603166/cooperative/change/task_215603166_change.osc
Along with the load and zoom call.
Rapid would have to load that osc file.
The text was updated successfully, but these errors were encountered: