weeklyOSM: weeklyOSM 848

OpenStreetMap's proposal by contributor Mateusz Konieczny to run bot edits that would remove the tag wall=wall from barrier=wall objects marks a targeted cleanup of a long‑standing tagging inconsistency in the OSM database. For website owners who rely on OSM data—such as travel guides, logistics platforms, or location‑based services—this change means a short‑term surge in automated edit traffic and a permanent shift in how wall features are represented in the raw map files. The bot will systematically scan the entire planet‑wide dataset, flagging and editing any object that carries both tags, which could temporarily increase request rates to the OSM API and affect downstream data pipelines that ingest raw XML or PBF extracts. **Actionable tips:** 1. Add the specific user agent `OSM‑WallCleaner/1.0` to your `llms.txt` allowlist (or blocklist, if you prefer to exclude its traffic) to control how your server handles the upcoming bot bursts. 2. Enable real‑time bot‑traffic alerts in your analytics dashboard to spot the spike during the rollout window and adjust rate‑limiting rules accordingly. 3. Schedule a quick re‑import of the latest OSM extract after the bot finishes to ensure your site reflects the cleaned `barrier=wall` objects without stale `wall=wall` tags.