weeklyOSM: weeklyOSM 850

iD's tagging schema v7.3.0 release adds a comprehensive set of new key/value pairs and validation rules for editors such as iD, GoMap!!, and EveryDoor, expanding the granularity of map features that can be captured and shared. For website owners who embed OpenStreetMap (OSM) tiles, location search widgets, or geodata APIs, the updated schema means a surge in AI‑driven crawlers that will query the OSM API for the newly exposed tags (e.g., `highway=cycleway:lane`, `amenity=charging_station:capacity`). These bots often harvest richer attribute data to train navigation, logistics, and autonomous‑vehicle models. Consequently, traffic patterns to your map tiles and geocoding endpoints may shift, and you could see higher request volumes for previously unused tag combinations. **Actionable tips:** 1. **Update your llms.txt** to list the new OSM‑related bots (e.g., `User‑Agent: osm‑bot/v7.3.0`) and set appropriate rate limits, ensuring legitimate traffic isn’t throttled while curbing abusive scraping. 2. **Implement tag‑specific monitoring** in your analytics stack—track requests that include the fresh tags (`highway=cycleway:lane`, `amenity=charging_station:capacity`) and flag spikes that exceed baseline thresholds. 3. **Deploy a robots.txt rule** that disallows generic AI crawlers from accessing raw OSM data endpoints but permits your own licensed data services, thereby protecting your site’s performance while complying with OSM’s usage policy.