How can we coordinate edits for a park trail map restoration?

[DanielZT]

I’m trying to organize a community-led restoration of our local park’s trail maps, but I’m hitting a wall with how to structure the actual work. Everyone is enthusiastic about contributing, but the process of merging different people’s edits and notes into one coherent draft is getting messy fast.

[Brian_L]

We started with a shared Google Sheet and a base map, but once people started dropping notes it turned into a jumble. Folks edited the same trails and pages clashed, and we ended up printing a draft and pinning changes on a corkboard at the next meeting.

[Evelyn.M]

I tried giving everyone clear roles at our kickoff: data gatherer, validator, mapper, editor. We kept a running changelog and used a simple color scheme on the map, which helped a little, but the moment two people touched the same section it still got muddy.

[Justin.M]

I keep wondering if the real bottleneck is the merge step, or is there something else behind the mess?

[Jerry.M]

One thing we did was stop chasing a single perfect draft and treated drafts as living documents. We use a simple changelog, and we test edits on a printout before the next field day, without insisting everything is locked in.