You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request to enable including geojson properties in default changeset comment.
Similar to functionality of per-task instructions box (#767), can we also enable the task admin to load geojson properties in the comments for that task?
example : #village_{CENSUS}
Screenshot of where I'd like to be able to enter this.. see highlighted text:
Benefit : We don't have to request the participants to manually put this info in to each and every node/way/area they add, and it helps in tracking, documentation, analysis etc later.
Rendering : We can keep it displaying with the curly braces like #village_{CENSUS} while the area isn't picked yet, and change it to corresponding value (like #village_55623) once a task/shape is picked and editing starts. I believe this display issue might be the only hindrance to getting this done.. I think we'll be fine.
The text was updated successfully, but these errors were encountered:
I'm afraid this would ask a certain amount of work. This is most probably not going to happen since the tasking manager v2 development is stopped in favor of v3.
There's a v3? Great, I'll post this there! Is it this : https://github.com/hotosm/tasking-manager/
The India HOT site http://tasks.openstreetmap.in directed me to this repo. I'd like to understand if it's this repo that's live there or the v3, and if there's any plan of moving to v3 or is v3 ready yet?
The India's tasking manager actually runs v2 (ie. the current repository).
As far as I know India's tasking manager is not managed by HOT.
So you should ask the India OSM community.
Feature request to enable including geojson properties in default changeset comment.
Similar to functionality of per-task instructions box (#767), can we also enable the task admin to load geojson properties in the comments for that task?
example :
#village_{CENSUS}
Screenshot of where I'd like to be able to enter this.. see highlighted text:
Benefit : We don't have to request the participants to manually put this info in to each and every node/way/area they add, and it helps in tracking, documentation, analysis etc later.
Rendering : We can keep it displaying with the curly braces like
#village_{CENSUS}
while the area isn't picked yet, and change it to corresponding value (like#village_55623
) once a task/shape is picked and editing starts. I believe this display issue might be the only hindrance to getting this done.. I think we'll be fine.The text was updated successfully, but these errors were encountered: