Skip to content
MangoMap Help Centre
Esc
↑↓navigate↵open⌘Jpreview
On this page

How feature editing works in MangoMap

Understand which layers you can edit, who can edit them, and why a saved feature edit changes the dataset on every map that uses it.

Feature editing changes the dataset behind a layer. The saved change appears on every map that uses the dataset.

Available actions

For an editable vector feature, the popup menu provides:

  • Edit attributes
  • Edit geometry
  • Add feature
  • Delete feature

Raster and WMS layers do not contain editable vector features.

Permissions

The editing actions appear only when the signed-in user can edit features in the dataset. Your account role and your access to the dataset both matter.

See How dataset access works and Account roles for that model.

Popups are the entry point

Select an existing feature to open its popup, then use the three-dot menu. A layer with popups disabled does not provide this entry point.

Adding also starts from an existing feature. MangoMap uses it to identify the dataset, layer, and attributes. The dataset’s geometry type sets what you draw. Because adding needs an existing feature, the map editor cannot add the first feature to an empty dataset.

Changes affect source data

Action Dataset effect
Edit attributes Changes the values of one feature
Edit geometry Changes one feature’s shape
Add feature Adds a feature
Delete feature Permanently removes the feature

A map that is already open picks up the change within about 20 seconds.

One saved edit reaches every map that uses the dataset, and a later file update replaces it:

Where a feature edit goes Data flow: an edit, add or delete in a popup writes to the dataset, which gets a new tile version, so the layer on every map that uses the dataset shows the change; there is no per-map copy and no undo, and a file update or Dropbox sync replaces the dataset's features and overwrites the edits. WRITES REPLACES Popup editedit, add or delete File updateor Dropbox sync Dataset new tile version no per-map copy no undo ON EVERY MAP Layer on map 1 Layer on map 2 Layer on map 3

No per-map edit or undo

Data edits apply to the dataset, not one map. Layer styling, popup configuration, and attribute formatting can differ per map, but feature values and geometry belong to the dataset.

MangoMap does not keep an in-product revision history for feature edits. Delete feature asks you to confirm, but after you confirm you cannot undo the deletion.

For large changes or recovery from an external source, update the dataset from a prepared file instead of editing features one at a time. A file update or a Dropbox sync replaces all the dataset’s features with the ones in the file, so it overwrites any edits made in the map.