The Edit, Rules, Locks, History and Snapshots tabs, the map modes, how a save is answered per change, and what the panel says when it is not there.
Open the data item at /data/items, pick the layer tab if the item hosts several, and scroll to Editing. The panel appears only when the layer is ready and your instance has editing switched on. Its title row shows the layer's current edit version, your capability chips (editing on, create, edit, delete, geometry; a crossed-out chip carries the reason on hover) and, for managers, the On/Off switch.
The panel has up to five tabs. Edit and Snapshots are there for everyone who can see the layer; Rules and Locks need the lock permission; History needs the history permission.
Editing in the browser is online only and loads every feature of the layer into the page. It is the right tool for corrections, locks, rules and snapshots. For a layer above tens of thousands of features the panel says so and points you to Hyz Desktop, which handles big layers offline.
The left side is a map of the layer over imagery; the right side is the attribute form of the selected feature. Three modes sit above the map:
The attribute form lists every field of the layer. A required field is marked with an asterisk. A field is read-only, with the reason on hover, when the feature is locked, when you may not edit, or when the owner excluded it from the editable fields. The platform's own columns (revision and lock) are shown read-only beneath. Numbers are typed as numbers; everything else as text.
Delete removes the selected feature. It refuses a locked feature and, unless the feature is one you just added, needs the delete capability.
Managers also see Lock this feature and Unlock this feature here.
Nothing reaches the server until you press Save changes. Until then your changes are a local list: new features, moved vertices, typed attributes and deletions, with the revision each change is based on. Reload drops that list and takes the server's copy.
On save the whole list goes in one request, and the server answers per change:
The answer also carries every change other people made since you loaded, and the map merges them in, except where you still have an unsaved change on the same feature. A toast says how many changes were saved and how many were not accepted. Every applied change counts against the owner's edits-per-month allowance.
Save often. A change that conflicts with someone else's is refused with changed on the server since you loaded it; reloading shows you their version, and your refused change is listed so you can re-apply it by hand. The conflict policy in the rules decides whether that happens at all.
Managers shape how the layer is edited: allowed operations, whether geometry is editable, which fields are editable and which are required, whether editors are limited to their own features, whether new features start unlocked, and what happens when two people change the same feature. Draw an editing area jumps to the map: click the corners of the area, finish, and the polygon is saved as the layer's fence; Remove the area clears it. Save rules writes everything at once. The rules explains each one.
Switching editing on for the first time past your plan's allowance is refused with Your plan's limit of editable layers is reached.
Lock or unlock many features at once by a filter: a field, a condition (equals, not equals, greater, greater or equal, less, less or equal, like) and a value. Lock matching and Unlock matching report how many features changed. Locked features refuse every edit, the owner's included, until unlocked. See permissions and locks.
The last fifty entries of the edit log, newest first: the edit version, the verb (created, changed, deleted, lock changed), the feature, who did it and when. Below it, the Checkouts other tools hold on the layer, with their label, format, version and last sync. The full log is available through the API with filters by feature, person and version. See history, snapshots and restore.
Take a snapshot keeps the layer as it is now as a new version of the item. Each snapshot row names the item version, the edit version it was cut at, its feature count and its date. Restore is available to managers once the snapshot has been scanned clean; it asks for confirmation, keeps the current state as a safety snapshot first, then replaces the live features. Every Hyz Desktop checkout must be taken again afterwards.
| You see | Why |
|---|---|
| no Editing section | the layer is not ready, or editing is not switched on for your instance |
| Editing is switched off for this layer. It is read-only here. | the owner has not switched it on; managers see the switch and a hint instead |
| chips crossed out | your permission or the rules refuse that operation; hover for the reason |
| A large layer … | the layer is too big for comfortable in-browser editing; use Hyz Desktop |
| Your plan's limit of editable layers is reached. | the owner's plan; limits |