Was node/1804845200 the only Jersey element?

What's the source for the name change?

Since I'm having difficulty loading this changeset in any analysis tool (see http://osmcha.org/changesets/117752030/ or http://overpass-api.de/achavi/?changeset=117752030 ), probably due to the size of it (both area of the bbox & count of changed elements); which element in Jersey was changed as part of this set (according to http://tyrasd.github.io/latest-changes/#12/49.2/-2.1 )?

👍🙂

Ah, OK. Fair enough. Objection withdrawn. Thanks for doing the cleanup.

@puma515

While I'm certainly not disagreeing, I think part of the problem is that his changes often span the International Date Line (longitude=180°), and whatever algorithm OSM uses to calculate the bbox does some kind of wrap-around instead.

Though, iWowik should be mindful of this (and using smaller CS areas anyway). Yet, he seems intent on ignoring the reasonable requests of other mappers, because he seems to (think he) know(s) best 🤷‍♂️.

Much smaller changeset areas, please: osm.wiki/Changeset#Geographical_size_of_changesets

Much smaller changeset areas, please: osm.wiki/Changeset#Geographical_size_of_changesets

For (my own) future reference: http://github.com/osmandapp/OsmAnd/issues/13740

👍🙂

Much smaller changeset areas, please: osm.wiki/Changeset#Geographical_size_of_changesets

Much smaller changeset areas, please: osm.wiki/Changeset#Geographical_size_of_changesets

Within OsmAnd, you can selectively upload changes. Doing so by region whom reduce the size of changeset bounding boxes.

Welcome to OSM, thanks for contributing.

Some helpful guidance & advice to make good quality changesets & help make your changes clear to other mappers (OSM is a community, after all):

▪︎what makes for osm.wiki/Good_changeset_comments (“new” isn't very descriptive of what you changed, where, how, & why)
▪︎much smaller changeset areas, please: osm.wiki/Changeset#Geographical_size_of_changesets — in this case, splitting your two changes into separate changesets, would've been better. The bounding box for each would've been small. Instead, doing both in one set means it spans the Atlantic and notifies everyone within the box who is monitoring their local area for changes
▪︎you should specify the source (see source=* ) of where the data for your changes came from
▪︎more generally, it would be wise to peruse osm.wiki/Good_practice

Much smaller changeset areas, please: osm.wiki/Changeset#Geographical_size_of_changesets

👍

Planning application for Moneypenny Lane: http://www.gov.je/citizen/planning/pages/PlanningApplicationDetail.aspx?s=1&r=A/2021/0966

Don't forget the barrier: node/1880734960

Having done a little digging …

None of
▪︎office=*
▪︎office=government
▪︎government=*
mention anything about how to tag a regulator.

Even TagInfo has only a few matches: http://taginfo.osm.org/keys/government#values

I'll have a think about what might make for suitable tagging.

Note to self: review which of these are valid & correct, for careful manual addition.

office=financial is also incorrect; suggests that JFSC is, itself, a financial services house (like a bank or trust administration), rather than a regulator.

office=government (without government=register) was closer.

Nope; a government=register_office is “Used to mark a register of births, marriages and deaths”.

While financial houses may have to register with JFSC, that's because it's a regulator. Conceptually different.