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

How data updates work in MangoMap

When to update a dataset from a file and when to sync it with Dropbox. Both keep the maps that use it, their styling, and the dataset's URL in place.

Update a dataset in your library in two ways: upload a file from your computer, or sync a Dropbox folder. The dataset’s Configuration page has separate Update from file and Sync sections. You can use either or both. Choose the method that matches your data source.

This page is the explanation. For the canonical control list, see Data updates reference.

Where these sections are

Both are on the dataset’s Configuration page (in the dataset’s sidebar). Its sections are Data details, Access, Update from file, and Sync.

Update from file and Sync are not shown for GeoTIFF (raster) datasets or WMS datasets. You cannot replace those formats by upload. If the source changes, delete the dataset and import a new one.

Update from file vs. Sync

Path When to use it
Update from file The data lives somewhere you don’t want MangoMap to read directly — a local file, an export from another system, a one-off snapshot. You decide when to update by uploading a fresh file.
Sync The data lives in a Dropbox folder you control. You want MangoMap to pick up changes automatically whenever the file changes in Dropbox.

You can use both on the same dataset. If sync is on and you upload a file manually, the manual upload wins for the moment; the next Dropbox change replaces it. To make manual uploads authoritative, disconnect Dropbox first — see How to change or disconnect Dropbox sync.

Sync on a dataset moves between a few states. After you connect Dropbox, picking every required file turns sync on and runs the first sync. If a changed file in Dropbox fails the checks, the Sync card shows Sync failed: …, but sync stays on: the next change with a good file brings it back. Update File Location takes you back to picking files. Disconnect turns sync off from any state, and the dataset keeps its data.

Follow one dataset from Connect Dropbox to Disconnect:

Dropbox sync statesState machine: Connect takes a dataset from Not connected to Connected; picking every required file turns sync on and runs the first sync; a bad file in Dropbox moves sync to Sync failed and a fixed file moves it back; Update File Location goes back to picking files; a manual upload while sync is on is replaced by the next Dropbox change; Disconnect from any state returns to Not connected and keeps the data.CONNECTFILES PICKEDNEW LOCATIONBAD FILEFIXED FILEMANUAL UPLOADreplaced by the next Dropbox changeNot connectedConnect to DropboxConnectedpick the files to syncSync activeupdates when files changeSync failedsync stays onDISCONNECTFrom any state, back to Not connected. The dataset keeps its data.

What’s preserved across updates

A dataset has an identity that’s separate from its file content. Updating a dataset keeps its identity:

  • The dataset URL stays the same.
  • The dataset’s group access (View and Edit toggles) stays the same.
  • Maps that use the dataset as a layer keep using the dataset. Maps show the new content the next time they are opened.
  • Styling, popups, and configuration applied to layers using the dataset stay in place, as long as the new file has the same attribute structure.

The update replaces the data: the rows or features in the new file replace the old ones.

What can break

MangoMap checks three things before it replaces the data, and refuses the file if any check fails:

  • One layer. A dataset holds one layer, so the new file must hold one layer too. MangoMap can’t choose between several, so a file with more than one layer is refused, and the message names them. If only one of the file’s layers imports, MangoMap uses that layer.
  • Geometry type. The new file must hold the same geometry type as the dataset: point, line, or polygon. Single and multi-part shapes count as the same type. Every map’s style for the dataset is built for its geometry type, so a different type would break them all.
  • Existing columns. The new file must keep every column the dataset already has, matched without regard to capital letters. It can add new columns. A file that drops or renames a column is refused with Missing required columns: ….

MangoMap runs the checks in this order and stops at the first one that fails:

Checks before your data is replacedFlowchart: a new file from Update from file or a Dropbox change must hold one layer, the same geometry type, and every existing column; if it passes, the data is replaced and the URL, access and layer styling are kept; if any check fails, the dataset is unchanged and the message shows in the dialog or on the Sync card.NONONOYESYESYESA new file arrivesUpdate from file or a Dropbox changeOne layerin the file?Same geometrytype?Every existingcolumn there?File refusedthe dataset is unchangedmessage in Processing failedor Sync failed on the cardData replacedsame URL and accessevery map keeps its styling

Within those rules, problems can still occur:

  • Reserved field names. Columns named id, gid, geom, geometry, or the_geom (case-insensitive) are stored with a leading underscore (_id, _gid, etc.) — see Reserved field names. Keep the original names in your update files. Do not rename a column to its stored name (for example _id).
  • Type changes. A column that was Integer in the old file but Text in the new file can break number formatting and quantity-based styles.
  • Different feature counts. Maps and groups don’t break, but if a viewer had a specific feature in mind, it may no longer be there.

MangoMap doesn’t warn about type changes during an update. Test the map after the update.

Supported formats

Update from file and Sync both support the same five vector formats:

  • CSV
  • GeoJSON
  • KML
  • Shapefile (multipart: .shp, .dbf, .shx, .prj)
  • TAB (multipart: .dat, .id, .map, .tab)

Both sections show a Data format dropdown to pick the format you’re uploading. The dropdown defaults to the dataset’s existing format if it’s one of the five; otherwise it defaults to Shapefile.

You can change the format between updates. A dataset that was originally imported as CSV can be updated from a GeoJSON file, and vice versa. The dropdown is what you set; MangoMap reads the file accordingly.

Multipart formats

Shapefile and TAB are multipart — they need several files together. Both sections show a Required files list with a row per extension. The upload doesn’t start until every required extension is present:

  • For Shapefile: .shp, .dbf, .shx, .prj (four files).
  • For TAB: .dat, .id, .map, .tab (four files).

If you drop only some of the required files, the section lists the files you added, shows 4 files are required, and marks each missing row File missing. The upload starts when the set is complete.

Who can use these sections

Both sections require dataset Edit access. That’s:

  • The dataset creator, or
  • The account owner, or
  • A user with an Editor (or higher) account role and Edit access on a group that has the dataset.

Viewer users — even with group Edit access — can’t update or sync a dataset; the role isn’t high enough. Admin users qualify.

For the full role and group rules, see Account roles reference.

What happens after an update

After a successful update, the data is replaced.

A failed upload doesn’t change the dataset — the previous content stays in place. For Update from file, the reason shows in the Processing failed dialog. For a Dropbox sync, it shows as Sync failed: … on the Sync card. Try again with the corrected file or contact support.

Dropbox sync is the only sync option today

Enterprise and Agency only

Sync is currently Dropbox-only. There is no option to sync from S3, Google Drive, OneDrive, an FTP server, or a generic URL. If you don’t use Dropbox, your only option is Update from file.

Connecting Dropbox requires the Dropbox integration on your subscription. If your subscription doesn’t include it, clicking Connect Dropbox opens an upgrade prompt. See How subscription and billing work in MangoMap for what each plan includes.