You may subscribe to daily updated feeds for new areas, changes of the areas, and squares to review of each of the areas.
The list of the feeds is intentionally limited, but extendable!
And while we are on the topic of updates: just updated the #openstreetmap stats here https://wiki.openstreetmap.org/wiki/Stats#Contributor_statistics_reports seems as if March 2021 with over 54'000 active contributors broke the previous record of 53'000 from January 2017
So the #OpenStreetMap diary summarizing this thread is out.
The first release of #damn (python) client
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
Foo. Going to bed now. I will summarize the thread in some diary soon.
TM Projects can overlap -- To be honest, this was my number one when I read the Pete's diary.
Example output of the script:
$ ./intersecting_areas.py 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.
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.
The following are the technical issues.
1. TM projects can overlap
- Not possible to check if projects' areas overlap.
- Multiple projects used by different groups of mappers mapping the same area.
- Not easy, nor intuitive.
3. Local mappers
- Find local contributors within project's area and interact with them.
- Inactive projects hangs around for a long time.
- Incomplete data in the project's area.
- Issues for new projects with overlapping area.
- Hard to find people involved in the project.
- Onboarding process does not emphasise the importance of the project
documentation or link.
Areas of interest for beginners
- Bad categorisation of the project.
- Onboarding process (see above) forbids categorisation of urban environment as
the project for beginners.
- The solution works for one situation only.
3/3 Project creators
- One manager for many many projects.
- Responsibility for the onboarding process.
- Onboarding process strenghtening.
2/3 Project creators
- 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
- ensure that standards are met,
- ensure that the mappers are able to do what requested.
1/3 Project creators
- When TM was opened, the data quality was low due to poor project description.
The following is my summary (understanding) of the diary.
What is TM?
- What mapping process is?
- What is the origin of a project?
- What is the ownership of a project?
- For who is TM for?
- New mappers don't understand (because they don't have answers.)
- New mapper edits frustrate old mappers.
- Discourage new mappers.
- Learning process interruption.
From the #damn project's perspective.
The idea is to solve the technical issues, and discuss the non-technical ones.
It's now possible to run Overpass query for changed buildings/highways/waterways/landuse in last hour/3 hours/day/week/overall directly from the #damn client _statistics_ page now.
The statistics are approximate, however, because convex hull of all the squares is used for the query border.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!