I’d like to document a small automated edit under OSM account PostboxMap.
PostboxMap already links many of our moderated UK postbox records to existing OSM amenity=post_box nodes (matched by Royal Mail-style ref + proximity). We propose adding only:
where that tag is missing, the live OSM element is still amenity=post_box, and validation passes. We will not create nodes, move geometry, or copy other fields.
source:* is not the namespace for this. It’s about the source for OSM, and is largely discouraged in favour of use on the changeset.
ref would be a more suitable namespace, eg ref:GB:postboxmap, but what’s the goal here? And since OSM and PostboxMap both collect Royal Mail refs, why not just use them to link the 2 datasets?
On the account: yes, the OSM user is PostboxMap (wiki page uses PostBoxMap casing; same account).
Goal: give mappers a direct URL from an already-matched OSM amenity=post_box node to the corresponding moderated PostboxMap listing (photos, cypher notes, discussion). We already hold an osm_type/osm_id link on our side; this would make the reverse link visible on the map object.
Royal Mail-style ref alone is not enough for that reverse link: many nodes have no ref, some refs are ambiguous or differ by trailing D, and a ref still does not give a stable URL into our catalogue.
On the key: happy to drop source:postboxmap. Prefer the community’s choice before any pilot. Would ref:GB:postboxmap=<id> (PostboxMap object id only) be acceptable, or would you rather see a full URL under another key?
I don’t think this (or any) tag is at all necessary for OSM - what value does it provide to us? As @CjMalone says, there are other ways to link back to OSM data. Filling in missing refs and postboxes would provide more value to both projects. I also detect a hint of vibecoding which suggests to me that any automated edit may introduce errors as we have seen in the past.
From what I have read on Terms of Service - PostboxMap.co.uk | PostboxMap.co.uk this is not a open project, and we are not able to transfer any information Postboxmap contributors have surveyed to OSM. In fact, the way it’s written seems actively hostile to OSM. It’s a no from me adding an identifier on every postbox linking to a closed source project.
Value for OSM. Fair question. The only intended value was an optional reverse URL on nodes we have already matched, so a mapper who wants photos / cypher notes can open that listing in one click. It is not essential map data. If UK consensus is that this does not earn a tag on the object, we will not run the automated edit. Happy to leave reverse links on our side only.
Terms / “hostile to OSM”. Section 8b is meant to stop the opposite problem: bulk copying PostboxMap coordinates, photos, or new nodes into OSM (which OSM’s Automated Edits / Import rules also forbid). It welcomes OSM→PostboxMap citation links and field-survey use where the mapper verifies on the ground. It does not licence our catalogue for transfer into OSM. That is why this proposal was citation-only on already-linked amenity=post_box nodes: no new nodes, no geometry moves, no photo reuse, no copying of other survey tags.
Automation quality. Understood on past bad bots. Algorithm is on the wiki; dry-run only so far; pilot would have been ≤20 with human review. That is moot if the community prefers no tag at all.
We will not --apply anything while this is unresolved. If the answer is “no identifier on OSM objects,” we will update the wiki status accordingly and keep inbound OSM links on PostboxMap only.
Reading the room: LordGarySugar’s post, the likes on it, and the poll (No so far, zero Yes) are enough. We are withdrawing this automated-edit proposal.
There will be no outbound citation tags written to OSM from PostboxMap. We will keep matching OSM nodes on our side only (inbound links), leave the wiki page marked withdrawn / cancelled, and will not run apply.
Appreciate the time spent explaining tagging norms and what is useful for OSM.
I can understand people initially being wary of openly allowing reuse of data they have invested time in collected, but I wonder if this approach might be worth re-considering? It looks, on the surface, that you have a rich dataset that may be helpful for OSM contributors. I strongly suspect that there wouldn’t be downsides to either project to allow more free sharing of data.
You are right that the dataset is richer than a simple ref list, and that “no reuse into OSM” can look unfriendly at first glance. Section 8b was written the other way round: to stop bulk copying of our coordinates, photos, or new nodes into OSM without a proper import discussion (which OSM’s own Automated Edits / Import rules also require). It was not meant as a snub to mappers who survey on the ground and want a handy link to photos or notes.
How we had hoped to sequence things:
First: optional reverse links / citations on nodes we have already matched, so someone looking at an OSM post box can open the PostboxMap page for more info (photos, cypher notes, discussion). That was all this withdrawn proposal was about. No new nodes, no geometry, no photo reuse.
Later, and only after a separate community discussion: whether there is a careful, OSM-shaped way to help with missing boxes or other gap-filling. That would need its own proposal, licensing clarity, and Terms updates. We would not bolt that onto a citation edit.
Given the poll and feedback here, we are leaving the citation auto-edit withdrawn for now and not writing tags. We can always un-withdraw later if UK consensus shifts toward optional reverse links. Happy to keep listening if the conversation turns toward a collaboration model that works for both projects. In the meantime we will keep matching OSM nodes on our side so PostboxMap users can jump to OSM.
What we actually want is simple: let someone on OSM click through from a post box node to the PostboxMap page for that box, so they can see photos and history. Only where we have already matched the same box. No new nodes, no moving anything, no copying our survey data into OSM.
We wrote that up about three months ago on the amenity=post_box Talk page, and there was no pushback on the idea itself at the time:
The bit that landed badly here was the packaging: source:* was the wrong namespace, and our Terms read as if we were anti-OSM. Fair enough. We have rewritten Terms §8b so it is clearer we welcome OSM and only mean “no bulk dump of our catalogue / no photo reuse”:
So: un-withdrawing the proposal, with that narrower plan. Happy to drop source:postboxmap and use whatever key people prefer (CjMalone’s ref:GB:postboxmap or another option), as long as there is a way to get to the page URL for click-through. Still no writes until the key is settled. Pilot would stay tiny (≤20) after that.
Separately: some people mentioned filling missing post boxes. That would be a completely different plan, only after a lot more discussion, and it is very much parked for now. This thread is only about the click-through link on boxes that already exist on both sides.
Wiki page will be updated to match once the key is clearer:
As per the first comment, I don’t really understand the reason behind doing this at all. Is there something data-wise here or is this just for getting more clickthroughs to your website?
I feel like it might be better the other way around, having your community help contribute to postbox data on OSM would go a long way.
The issue here is that there is a principle that OSM is not to be used to add endless ref tags linking through to external databases. As such there is a relatively high bar on community acceptance of such tags. Official (e.g refs to government ran systems), primary (e.g ref of the map feature’s owner) and wikidata are widely accepted. Beyond that it’s a case of convincing people.
Then once you have a tag, getting it so the website displays a click through link if another challenge. That is decided by those that maintain the website code.
Given there is already an official reference number for each UK Postbox (Royal Mail’s ‘box number’), I don’t think there’s a good case for adding another one to any specific third-party website, let alone one that doesn’t seem to be an Open Data project.
If PostboxMap could show itself to be useful to OSM (and perhaps the Open Data community in general), e.g. by releasing any data and photos collected as Open Data (specifically with an OSM compatible licence) and it had reasonable coverage of UK postboxes, then I could see that there might then be a case for map or tag2link maintainers to link values in the post-box ref=* key to a corresponding page on the PostboxMap website. But for this to happen, you’d need to be very much an Open Data project, be seen as the best open resource for postbox information, be able to accept links from all postboxes, and have clear benefits to users over linking to the official Royal Mail page for each postbox.
No-one here is really in a position to guarantee anything, but if you’re interesting in collaborating with OSM, then I think a good place to start would be to run a background process to match your records to OSM’s, produce a regularly updated online report on any boxes you have that are missing or misplaced/mis-tagged in OSM, and give OSM permission to use the info and photos you have to add/update things.
We may look at gap-filling as the primary integration instead: putting missing post box info into OSM where it helps, under an OSM-compatible licence. We are more than happy to do that automatically if the community wants it.
If we did, we would still need a source link back to the PostboxMap page so people can click through and see the photos. Without that, the photos stay stuck on our side.
Would that approach be the preferred first step?
We had planned to do that second. The idea was to finish matching known OSM boxes that are already on our map (so we have the node id on our side) before talking about adding anything new. Happy to reorder if gap-filling is what people actually want first.