Automated edits/Daniel ATZ

Status: paused. No future automated edits or imports are approved or scheduled.

Account, organiser and purpose

Daniel_ATZ is used by Daniel Bischoping / ATZ for commercially related Bosch Car Service location-management work. A Python/OSM API pilot on 8 September 2026 preceded the required public documentation and consultation. Project map writes have been blocked since 11 September 2026.

Method, sources and prior changes

The central activity documentation describes the actual prior export/geocoding/duplicate-heuristic/node-upload workflow, the inventory of 22 changesets and 22 nodes (20 visible and two deleted), unresolved source rights, proposed tagging, and the outstanding individual quality review and cleanup. That page is the maintained plan; it does not claim import approval. No fixed repetition schedule is currently authorised.

Source provenance and permission for the GBP/PowerBI-exported fields remain unresolved. Tool source and a permitted sample still require public review access before any complete proposal. Future algorithm details and material changes to scope must be documented and discussed before implementation is enabled.

Discussion and opt-out

Existing public discussion: changeset 188710840. Broader local consultation and formal import review have not started. A published wiki page alone does not start or satisfy the full import review.

Please contact Daniel via OSM or comment publicly to raise concerns or request exclusion of edited objects or areas. Such requests must be respected and recorded; a persistent exclusion register with preparation/upload checks is required before restart. Currently all candidates are excluded by the global write pause.

Validation and recovery

Existing object versions, other contributors' edits, surrounding objects, source rights, positions and tags must be reviewed individually. No blanket revert or deletion is authorised by this documentation. Coordinate corrective work with the community and involve the DWG for unresolved rights or recovery issues. Future geographically coherent changesets must identify the actual source and reviewed activity/method, include mechanical=yes or bot=yes where applicable, and preserve the information necessary for version-aware recovery.