What this guide helps you do
A useful map needs enough reports to show problems, but not so many duplicates that nobody can read the pattern. Duplicate reports can hide real changes and make cleanup planning harder.
Use this guide before reporting a place that may already be visible on the map.
- Use this when
- Use this guide before reporting a place that may already be visible on the map.
- Best outcome
- The map shows one clear location record with useful confirmations instead of several scattered markers for the same problem.
Check nearby pins before starting a new report
Open the map and zoom into the area where you are standing. Look for nearby pins with similar material, ZIP, and description. The same problem may already be on the map even if the pin is a little off.
If the existing pin clearly matches the spot, use a confirmation or follow-up note instead of creating a new report. That keeps the history tied to one place.
If the existing pin is nearby but not the same problem, submit a new report with a location note that explains the difference.
Submit a new report when the place or material is different
A new report makes sense when the litter is in a different location, the material type changed substantially, or the scale is different enough to require a separate response. A tire pile and a bottle scatter on the same road may need different records.
Use your description to prevent confusion. Say “separate pile across the road” or “new bags near the bridge entrance” when the location is close to an existing pin.
Do not create a new pin just because you are frustrated that the old one remains. If nothing changed, confirm the status instead.
Use confirmations to show status
Confirmations tell readers whether a report is still there, cleaned, or changed. They preserve the history without adding clutter.
A confirmation can be short. “Still there today,” “cleaned as of Saturday,” or “tires remain after bags removed” gives people the status they need.
Status updates make the map more trustworthy. They show that reports are not abandoned after submission.
Use community threads for planning and discussion
The map should show location records. The community board should hold cleanup timing, route notes, disposal questions, and longer follow-up. Splitting those jobs keeps both pages easier to use.
If a report has several people involved, a thread may be better than repeated map notes. The thread can summarize what is planned and link people back to the map.
Keep threads specific. A post tied to a ZIP, route, or reported location is more useful than a general complaint about litter.
Correct bad data instead of adding around it
If a report is clearly wrong, duplicated, or confusing, use Contact with the details. Adding another report to compensate may make the map worse.
Good corrections include the URL or location, what is wrong, and what the correct information should be. Avoid long arguments.
A clean map is an ongoing process. Reports, confirmations, moderation, and corrections all work together.