I will work on @pedrito1414's #OpenStreetMap diary tonight.
https://www.openstreetmap.org/user/pedrito1414/diary/395256
From the #damn project's perspective.
The idea is to solve the technical issues, and discuss the non-technical ones.
The following is my summary (understanding) of the diary.
What is TM?
Questions:
- What mapping process is?
- What is the origin of a project?
- What is the ownership of a project?
- For who is TM for?
Problems:
- New mappers don't understand (because they don't have answers.)
- New mapper edits frustrate old mappers.
Consequences:
- Discourage new mappers.
- Learning process interruption.
1/3 Project creators
Problem:
- When TM was opened, the data quality was low due to poor project description.
2/3 Project creators
Solution:
- Onboarding process. Making sure that managers fulfill the expectations of
having skills to:
- engage local communities and contributors,
- respond the questions and info requests,
- ensure the documentation of the project is on the wiki (in the case of
organised editing,)
- ensure that standards are met,
- ensure that the mappers are able to do what requested.
3/3 Project creators
New problems:
- One manager for many many projects.
- Responsibility for the onboarding process.
- Onboarding process strenghtening.
Areas of interest for beginners
Problem:
- Bad categorisation of the project.
Solution:
- Onboarding process (see above) forbids categorisation of urban environment as
the project for beginners.
New problem:
- The solution works for one situation only.
Project documentation
Problem:
- Onboarding process does not emphasise the importance of the project
documentation or link.
Unclosed projects
Problem:
- Inactive projects hangs around for a long time.
Consequences:
- Incomplete data in the project's area.
- Issues for new projects with overlapping area.
- Hard to find people involved in the project.
The following are the technical issues.
1. TM projects can overlap
Problem:
- Not possible to check if projects' areas overlap.
Consequence:
- Multiple projects used by different groups of mappers mapping the same area.
2. Feedback
Problem:
- Not easy, nor intuitive.
3. Local mappers
Problem:
- Find local contributors within project's area and interact with them.
Feedback -- There is _join discussion_ at the bottom of each #damn client page.
Local mappers -- I've upgraded the _statistics_ page: click _local mappers_ under the map for getting the list of #OpenStreetMap contributors that haven't used Divide and map. Now. while contributing within the same area. Solved by #overpass query.
TM Projects can overlap -- To be honest, this was my number one when I read the Pete's diary.
https://git.sr.ht/~qeef/damn-client.py
Example output of the script:
```
$ ./intersecting_areas.py https://server.damn-project.org/
testing https://server.damn-project.org/:
- 2229 intersects with 2253 of https://server.damn-project.org/
- 2253 intersects with 2229 of https://server.damn-project.org/
```
Actually, I didn't know these areas intersect.
I've tested with the localhost:8000 too, to check the script works for multiple server instances.
The first release of #damn (python) client
https://git.sr.ht/~qeef/damn-client.py/refs/v0.1.0
The output of the _abandoned areas_ script:
```
$ ./abandoned_areas.py https://server.damn-project.org/
Areas abandoned on https://server.damn-project.org since 2020-12-26T03:20:40:
- 7114 has only 1 commits
- 2245 has only 1 commits
- 7100 has only 2 commits
- 7102 has only 2 commits
Finished.
```
Foo. Going to bed now. I will summarize the thread in some diary soon.
Hi @qeef . I'm the 'mariotomo', in Panamá, where pedrito1414 took the lead for the topic.
you are missing a problem, the original one actually: there's organizations which "make themselves handsome in an OSM dress", without a clear understanding of the global OSM environment.
it's like "project owners behaving as eternally novice mappers". HOT implemented a screening of project owners, but there's organizations providing formal project ownership that is considered as legitimate by HOT.
Hi @mariotomo, I was paraphrasing the problems introduced in the @pedrito1414's diary. I can imagine that some of the problems are consequences of "organizations wearing OSM dress," but that's deeper.
"Newbie project owners" is the problem when you can't fix it yourself. Therefore I think that the project owners screening is less efficient than openness.
@qeef @pedrito1414 "openness" was my request to the YouthMappers. it's been impossible to talk about it. have you seen the diary entry »https://www.openstreetmap.org/user/mariotomo/diary/394356« ?
@mariotomo @pedrito1414 I've just read it (only english sentences,) and I completely agree with you. It's really sad that professors of the #YouthMappers chapter knows nothing about #OpenStreetMap.
From the conversation I guess that the biggest problem is that students are not participating in OSM-related (asynchronous) communication channel. But how could the students be lead to participate when the professors don't do that either?
This is YouthMappers failure, IMO.