Revision History
Revision history automatically saves a snapshot of a GeoJSON layer every time someone edits a feature on the map — so you can see what changed and restore an earlier version if an edit needs to be undone.
Who can see this
Revision history is available for:
- GeoJSON layers imported from a file. Layers connected to an external URL do not have revision history, since AugmentCity does not store their data.
- Project owners and editors. Contributors and viewers do not see the Revision history button.
Viewing revision history
- Open the Layers panel.
- Expand the layer's row (click the chevron) to reveal its options.
- Click Revision history (clock icon).
The panel header shows Revision history with a Refresh button — click it to reload the list if you suspect a teammate has added a new revision.
Each row shows:
- Revision N · operation (for example, Revision 3 · Property edit) — the revision number and what kind of edit produced it
- The date and time the revision was created, and how many features the layer had at that point
- A Restore button
If no edits have been made yet, the panel shows: "No revisions yet. Edits made from now on will appear here." If the history can't be loaded, it shows: "Could not load revision history."
How revisions are created
You never create a revision manually. AugmentCity records one automatically whenever a feature on the layer is edited:
| Operation | When it happens |
|---|---|
| Property edit | A feature's attribute values are changed |
| Geometry edit | A feature is moved or reshaped on the map |
| Feature copy | A feature is duplicated |
| Restore | An earlier revision is restored (see below) |
| ID backfill | AugmentCity assigns stable IDs to older features that lack one |
| Manual save | A save that doesn't fall into any of the categories above |
Each revision stores the layer's state before the edit that triggered it. This means the newest revision in the list is the one to restore if you want to undo the most recent change.
Copying features keeps your styling
When you copy a feature, the copy keeps styling and domain attributes such as color_id, category_id, and status_id — so a copied feature keeps the same marker colour or chart coloring as its source. Source-specific identifiers like OBJECTID, FID, and GlobalID are still removed from the copy, since those must stay unique to the original feature.
Restoring a revision
- Open Revision history and find the revision you want to bring back.
- Click Restore. The button is replaced by Confirm restore and Cancel restore.
- Click Confirm restore to apply it, or Cancel restore to back out.
Restoring a revision is itself recorded as a new Restore revision, holding the layer's state from just before the restore. If you change your mind, you can always restore that revision to bring back what you had before.
Restoring replaces the current state of the whole layer with the selected revision's features. It does not merge changes — anything added or changed after that revision is undone.
Notes
Revision snapshots never block editing. If the revision history service is briefly unavailable when you save an edit, the edit still goes through — it simply won't have a snapshot in the history list.
Revision history only tracks edits made through feature editing on the map (property edits, geometry edits, copies, and restores). Re-importing a file over an existing layer, or renaming/restyling the layer, does not create a revision.