The damn project helps mappers by dividing some big area into smaller squares that a human can map.
Try to map some squares or manage areas.
If you are advanced mapper, check out the
damn plugin for JOSM or the
panel for iD. If you prefer manual square lock workflow, use
the mappy client.
You may use RSS to keep track of the areas changes, intersecting web page to check if your new area intersects with other active areas, and python scripts for checking abandoned/intersecting areas.
The community drives the damn project.
Become a good community member.
Be empathetic, respectful, and patient. Try to discuss without emotions.
Learn to be efficient.
Distinguish if you are talking about what, why, or how.
How is discussed only after what is agreed.
If you present what, be prepared to explain why in different points of view tirelessly.
If you discuss what because you agree/disagree with it, try hard to understand why and provide constructive feedback.
Help others. It is nice, and it increases efficiency.
Multiple mapping workflows are supported by the damn clients. The following sections contain summary of particular mapping workflow, supported clients, and diagram of possible states before/after the square is locked.
Basic mapping workflow good for all kinds of mapping. Newbie mappers should start with the Map-review-done workflow. The mapper choose to map the recent, oldest, random, or nearest square. The reviewer choose to review the recent, oldest, random, nearest, or newbie’s square.
When no review is needed, it may be skipped. Good for personal projects or for areas that need only checking.
Each square of the area must be locked manually. This workflow helps fixing mistakes introduced in other workflows, or to prepare the area, e.g. merging all the water squares and marking them done.
Similar to the Map-review-done workflow with three
basic differences: prepared data are loaded when mapping begins, only JOSM
damn plugin is supported, square splitting and merging must be avoided.
This is improvement to previous mapping workflows when working with
damn plugin for JOSM can be set-up with the period to
download the notes.
This is improvement to previous mapping workflows when using
plugin for JOSM. You can select which mapper’s work to follow by right
click to Divide and map. Now. dialog window, then which mapper, then
put the mapper’s name.
Setting the mapper’s name affects map and review actions, except the review newbie.
Example use-case is when you want to review squares of particular mapper: you set the mapper’s name and click Review button.
Area is a place to be mapped.
Manager is a user of Divide and map. Now. who creates or changes areas.
Abandoned area is an area with no commits in last month. (One commit is one arbitrary activity: locking square for mapping and marking it for review are two commits; changing area’s priority is one commit.)
Area to finish is an area with priority -10. Areas with the priority less than zero are not listed between active areas.
Finished area is an area that has been removed from the database and is available in read-only fashion.
Every day, there is a periodic check for abandoned areas. Priority of each abandoned area is changed to -10. Thus, it actually becomes an area to finish.
Every day, there is a periodic check for areas to finish. Each area to finish that has no commits in last month is removed from the database and published in read-only fashion. Thus, it actually becomes an finished area.