Short answer

This is working as designed, not a bug. The Location Tag is set and kept up to date automatically — it re-derives whenever you save an asset. If the asset sits inside an area you've drawn on the map and tagged, it inherits that area's tag; if there's no area over it, it falls back to the nearest street. So if you type a tag in by hand on an asset that isn't inside a drawn area, it won't stick — on save it reverts to the nearest street. The asset's actual map position is unaffected; only the auto-derived tag changes. There's no need to keep re-setting it after each edit.

Detail

The Location Tag isn't a free-text field you set once — it's a derived value the platform recalculates each time the asset is saved. The rule it follows:

  1. Inside a tagged area? If the asset's pin falls inside a polygon you've drawn and given a location tag (a park, allotment site, building footprint, etc.), it inherits that area's tag — e.g. Memorial Park, Allotments.
  2. No area over it? It falls back to the nearest street name (e.g. Disbrowe Court, High Street).

Because step 2 re-runs on every save, manually typing a different tag on an asset that has no area over it is overwritten the next time you edit and save that asset. That's exactly what's happening when a clerk types "Caldecott" and watches it revert to a street name — the pin is still correctly placed; the tag has simply re-derived to the nearest street because no "Caldecott" area is drawn.

This street default is genuinely useful, and most councils leave it as-is. Searching a street name pulls up every bin, street light, or sign along that road in one go — handy for street-level work without any setup.

If you want assets to read a specific area name automatically (e.g. "Caldecott"), the way to make it stick is to draw that area on the map and set its location tag. Everything inside it then inherits the tag on its own, and it won't wander on save. Typing the tag onto individual assets won't hold without the area behind it.

In practice you only need to draw areas where there's an operational reason to group assets — for example a park where you want a weekly routine to inspect all the play equipment and do a litter pick, or an allotment site where the sheds and plots should all tag as "Allotments". For general street furniture, the nearest-street default usually does the job, so drawing areas isn't necessary.

Watch-outs

  • Don't fight the auto-tag by hand. Re-typing a tag after every edit is wasted effort if there's no area anchoring it — it will revert on the next save. Draw the area instead, or accept the street default.
  • The map position is separate from the tag. A tag reverting to a street name does not mean the asset has moved — check the pin; it's almost always still correct. The tag is cosmetic/searchable metadata, not the location itself.
  • Inheritance needs the area's Location tag field set, not just the area drawn. A drawn-but-untagged area won't pass anything down. See How do map areas work, and how do location tags get inherited?.
  • Areas aren't retroactive at draw time. Assets already placed before you draw an area aren't auto-retagged until they're next processed/saved or you do a bulk filter-and-edit pass.