What makes for osm.wiki/Good_changeset_comments 🙂.

Given the addr:housenumber of the node used for Premier Inn, while the published address of this Premier Inn is actually (something like) 28-30, then the node should be moved back to the original position, and the Premier Inn tags transferred to a new node where the Premier Inn entrance is.

See (also) changeset #105526533 “10 links to the website are just too much spam”.

Noted; I was trying to be through (since tags can always be ignored) for the benefit of data-users (not knowing which tagging keys they'd recognise).
---

Published using OSMCha: https://osmcha.org/changesets/105526533

Thanks; I'll endeavour to use this more specific key in future.
---

Published using OSMCha: https://osmcha.org/changesets/105525283

Especially given the small geographic scope of these changes: what makes for osm.wiki/Good_changeset_comments 🙂.

What makes for osm.wiki/Good_changeset_comments 🙂.

Seconded.

When trying to have OSM show me only local (for me, that's the island of Jersey) changes, any with large bounding boxes (like this one) are also included in the list, since Jersey is within the bounding box.
Separate changesets to smaller geographic regions (in this case, UK, Spain, Canada, USoA) would avoid this overlap problem.

As for descriptive changeset comments; besides other contributors, they may also help your future self. I've already experienced this, when needing to undelete a node from a specific changeset. The comment helped me to re-find it quite easily. With generic comments, I would have had to examine (in detail) each changeset.

Some crafty use of various naming tags might avoid the perceived problem.

Besides name, there's short_name, official_name, alt_name, old_name, name:fr (given that so many Jersey roads are named in French), and probably some others that I'm ignorant of.

That's a lot of (your own) editing work you undid; I'm most curious as to why.

There's a specific (and expressive) syntax for opening_hours (so that it's machine-readable), it's not a free-entry textual field.

See: opening_hours=*

Else, I suggest using description:opening_hours instead. Though, with properly-implemented software to read the data, it can be displayed however one wishes. OsmAnd comes to mind.

Any well-designed and well-implemented editor should be able to help construct the correct syntax (otherwise, file bug-reports).

👍

👍

Abbreviations can be made in rendering software (as a ‘display problem’ rather than one of data).

Thankyou for adding this. Routing algorithms should now be less confused 🙂.

Relevant comment from original changeset:

Having re-surveyed, more recently, it seems that I made a mistake.

The building isn't used exclusively by Jersey Mutual. There's an outside door, in the North-West corner, with a separate & different addr:housenumber, which leads upstairs to offices used by an entirely different business.

Undoing the (mistaken) deletion in changeset/104369434

Restored (via [Level0](http://level0.osmz.ru/)) in changeset [#104642621](changeset/104642621).

osm.wiki/Undoing_deletions

Having re-surveyed, more recently, it seems that I made a mistake.

The building isn't used exclusively by Jersey Mutual. There's an outside door, in the North-West corner, with a separate & different addr:housenumber, which leads upstairs to offices used by an entirely different business.

So, how do I at least undelete the node I removed, if not revert this (and subsequent) changeset(s), to do things more correctly?