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 JOSM plugin or the panel for
iD. If you prefer manual square lock workflow, use the mappy
You may use RSS to keep track of the areas changes, and python scripts for checking abandoned/intersecting areas.
The community discusses all the damn things. The community makes damn decisions. The community encourages creating new clients of all kinds.
Discuss. Try to be empathetic, respectful, patient. Try to discuss without emotions.
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.
Because 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.