For editors and owners
Layers and editing
Who may edit and how to give someone edit rights; make layers, add fields (from the attribute table too), load files into them, change values in the table or a feature's form (a meter's reading too), a feature's History (who changed what, when) and Restore, calculate areas and lengths, draw, change, copy, merge and clip features, and work on delivered data through editable copies.
Cartema keeps two kinds of layers apart: the layers delivered to your organisation, which stay exactly as delivered, and the layers you make and maintain yourselves, which you can shape as you need — the way ArcGIS users work with feature classes.
Who can do what
| In an app with editing on | In an app with editing off | |
|---|---|---|
| Owner, admin | Everything on this page, on every layer of the app — whether or not the layer's Editable box is ticked | Read only |
| A client's owner or admin, in the client's apps | Everything on this page, on every layer of the app — whether or not the layer's Editable box is ticked | Read only |
| Editor | Everything on this page, on the layers marked Editable and those chosen for them in Who edits it | Read only |
| A client's editor, in the client's apps, or an Editor of that app (a role on the app alone) | Edit features and changing values in the attribute table, on the layers marked Editable and those chosen for them in Who edits it or named on; their new layers and editable copies go into My layers | Read only |
| An Administrator of that app (a role on the app alone) | Edit features, changing values in the attribute table, new layers and editable copies, on the layers marked Editable | Read only |
| Viewer | Read only, except the layers they are named to edit | Read only |
Editing is decided app by app. It is off in every app until someone switches it on, so an app of official data stays read-only whatever its layers are set to. Within an app, a layer can be kept to chosen editors, and people who only view the app can be named to edit one layer; see Who sees it and who edits it and Roles per app.
Editing changes a layer's data. A layer's look and its fields are its settings, the same for everybody who opens the app: changing an app layer's look from the map is for the app's administrators (see A layer's look and style), and adding or removing its fields for the people who manage the app's layers (see Fields in the attribute table).
Giving someone edit rights
Editing rights are set in Studio, by the people who manage the app there. Choose the steps for how much the person should edit:
- One layer of an app (or every layer of a folder), even for somebody who only views the app: name them on the layer.
- Open Studio → Apps and the app.
- In its Layer tree, choose Rights (the key icon) on the layer's row.
- Under Named editors, type part of their name or e-mail in Find a person and click them.
- Choose Apply. The names are kept at once. See Named editors. Or ask Buddy Pro, for several people, layers or apps at once: "let Anna edit the Pipes layer in Northfield". See Who edits which layers.
- Every layer of one app: make them Editor of that app, where a role can differ from app to app (a client's people, and the viewers listed on an app kept to listed people). In Studio → People, click the app's chip on their line and choose Editor; or open the app's page in Studio and change their role under Who can open it. See Roles per app.
- The workspace's apps and Studio: make them Editor of the workspace: in Studio → People, pick Editor in their line. See Roles.
Whatever is chosen, the app's Editing in this app must be On (on the app's page in Studio). Then the layer's Editable box decides for the app's editors as a whole. The workspace's owners and administrators and a client's owners and administrators edit every layer without it, and so does an editor chosen for the layer in Who edits it, or named on it, who changes the app's data. To keep a layer's editing to some of the app's editors only, use Who edits it in the same Rights window. Each editor of an app and each named editor takes an editor seat of the plan.
Layers you edit by name
When you are named as the editor of some layers of an app you otherwise view, the map says so:
- Edit features and the attribute table's editing offer those layers only; every other layer of the app stays read only for you.
- In Edit features, a green line under the layer choice counts them: 3 of the app's 9 layers are yours to edit. You view the others. Nothing marks them in Layers itself, so long names stay readable.
On those layers you can draw new features, change and delete features, change their values in the attribute table, add attachments, go back to an earlier version and undo your edits, change several features at once, split features, copy or duplicate features into the layer, and load a file into it as new features. Changing the layer's fields, calculating a field, merging, clipping and copying the layer as a new one are for the app's editors; changing its look is for the app's administrators.
All of it holds only while the app's editing is on: if the app's Editing in this app is switched Off, nobody edits, and the tools go away. Somebody who only views the app edits a layer they are named on only while its Editable box is ticked; an editor of the app named on it edits it either way. Who is named is set in Studio by the app's team; see Named editors.
Switching editing on
In Studio → Apps, open the app and set Editing in this app to On. The change is saved at once and kept in the app's history. Setting it back to Off hides every tool on this page and refuses every change, without deleting anything.

Below it, the app's layer list has an Editable box for each layer: it says which layers' features can be changed while editing is on. Layers made or copied from the map are editable from the start. The box does not limit the workspace's owners and administrators, nor a client's owners and administrators in the client's apps: while editing is on, they edit every layer of the app. An editor chosen in Who edits it, or named on the layer, edits it without the box too.
Making an editable copy of a layer
To work on a layer you cannot edit — a delivered survey plan, a cadastre, a block's properties — make a copy of it that is yours:
- In the layer list, open the layer's menu (…) and choose Make an editable copy.
- Name the copy and choose Make the copy.
The copy is switched on and editable, with every feature the layer shows (a layer filtered to one block copies that block), every attribute with its rules, and the same style. Put the copy in place of the original in this app is ticked to start with: the copy takes the original's place in the layer list, so nothing is drawn twice. Untick it to keep both. Either way the original stays in the workspace's data exactly as it was, and the copy remembers which feature each of its features came from — so when it is handed back (see My layers), the features it changed are updated rather than added a second time.

To show the same data a second time with another look, you need no copy: see Showing a layer again with another style.
Showing a layer again with another style
To see one layer twice, side by side with two looks — water lines once by material and once by diameter, for example — show it again rather than copying it:
- In the layer list, open the layer's menu (…) and choose Show again with another style.
- The style window opens at once on a copy of the layer's current look, with the new layer's name at the top (the layer's name with "(2)"). Change the look as in Style — One colour or By field, the field and its values' colours, the width, the label — and watch it on the map.
- Choose Show it again. Cancel makes nothing.
To give the new layer a style that already exists instead, choose Use an existing style… at the bottom of the window: it lists the styles this app's layers draw with on the same data, and the data's default.
The second layer comes in just above the original, switched on, with its own legend. No data is copied: both draw the same features, so a feature changed through one is changed in the other. It keeps the original's filter and definition query, whether its features are identified, searched, exported and edited, and who may see and edit it. Later, choose Style in its menu to change the look again. Only those who arrange the app's layers, and may change their look, have it. In Studio, the app's layer list does the same with Duplicate on a layer's row.
Making a new layer
- Open Edit features in the left rail and choose New layer.
- Give it a name and choose Points, Lines or Polygons.
- Describe its fields. Each has an Alias (the name people read, in any language), a Column name (lower-case letters, digits and _; written for you from the alias), a Type, and under the arrow its Rules.
- Under Look, choose how it is drawn: its colour, and for areas the fill and outline, for lines the width, for points the Size and Shape (see A layer's look and style). With a List field, By a list gives each of its choices its own colour and, for points, its own icon.
- Choose Create layer. It appears at the top of the app, ready for its first feature.

New layers and copies of those who do not arrange the app
A new layer, an editable copy or a clip into a new layer changes the app's layer list, so it goes into the app only for the people who arrange that list: the workspace's owners and administrators, its editors where they arrange apps, a client's owners and administrators in the client's apps, and an app's administrators. Everybody else who edits — a client's editors, for example — makes theirs in My layers: New layer in Edit features opens a layer of your own, Copy to my layers in a layer's … menu makes your copy, and Clip cuts the layer itself. Share it from there as you like; to have it in the app for everyone, share it with an owner or administrator of your client, or use Submit to the workspace…, and they add it (see My layers).
Types: Text · Whole number · Decimal number · Yes / no · Date · Date and time.
Rules:
- Required — a feature cannot be saved without a value.
- Default — the value a new feature starts with; when a field is added to a layer that has features, they all take it.
- Length — for text, the most characters it keeps.
- Allowed values — one per line;
res = Residentialstores “res” and shows “Residential”. The form then offers a list, and any other value is refused.
A list for a field a layer already has. In Studio → Datasets, open the layer's data; under Field settings, click the field's Rules (it reads Any value while the field has none) and fill in Allowed values, one per line, in the order the list shows them. When a style of the layer already colours it by that field's values, Take from the style's categories fills the list with the style's categories, in the style's order; add, remove or move lines as you like, then choose Save. From then on, Edit features offers the field as a list — for one feature, for a new one and for several at once — and so does the attribute table, with an empty choice unless the field is required. A value that is not on the list is refused, whichever way it comes: the map, the table, the field calculator, a file loaded into the layer, or Buddy Pro. A value a feature already holds that is not on the list stays until somebody changes it, and an undo or a restore of an earlier version may bring back a value the feature held before the list, that very value only. The list is set by the people who set a layer's fields in Studio. Buddy Pro does it in one message too — "set the allowed values of Status from its style" (see Buddy Pro).
Changing a field's type. In Studio → Datasets, open the layer's data; under Field settings, click Change type beside the field's type and choose the new one: Text, Whole number, Decimal number, Yes / no or Date. Text becomes any of them; a number becomes text, the other kind of number or Yes / no; Yes / no becomes text or a number; a date becomes text. Preview says how many features have a value, how many convert and how many can't, with a few of those values. Nothing changes until you choose Change the type; when some values can't convert, tick Empty the values that can't convert first, or correct them and look again. Rules that don't fit the new type (a length, a default, allowed values) are removed. Undo type change, beside the type, puts the type, the rules and the values back for 30 days; a feature changed since keeps its change. List (allowed values) keeps the type and fills the field's allowed values with the values it holds, most used first: check them and choose Save. The type is changed by the people who add and remove a layer's fields in Studio, on a layer made in Cartema, a file you uploaded or a layer moved into Cartema alike. On a layer its source still updates (a delivery, a meter feed), the source's own fields keep the source's type, because the next update would bring it back; they can still be made a list, and a field added in Cartema changes freely. A field that keeps an app's layer to its features (its filter or definition query) keeps its type.
A layer's look and style
Style in a layer's … menu changes how it is drawn, on the map as you choose, until you Save or Cancel. The same choices are under Look when you make a layer.
A layer's look is the same for everybody who opens the app, so Style on the app's layers is for the app's administrators: the workspace's owners and administrators, a client's owners and administrators in the client's apps, and whoever's role on the app is Administrator. On the map, editors and viewers do not see it: editing changes a layer's data, not its look. The workspace's editors change styles in Studio (see Styles and print layouts). A layer of yours under My layers is styled by you and the people you let edit it. To hide a layer's labels for yourself only, use Labels on the map in its menu (see The map).
- Colour: one of nine, or another from the colour picker. By a field gives each value of a field its own colour instead; open a value in the list to change it.
- Fill and Outline, for areas: the fill None, Light, Medium or Solid, and the outline None, Thin or Bold. With None for both, the areas are not drawn at all, but a click on one still finds it, and the legend shows an empty box.
- Width and Arrows, for lines: Arrows On draws arrows along the line, pointing the way it was drawn — a pipe's flow, a one-way street. Their colour is the line's. Marks of another kind set in Studio, such as ticks, show neither On nor Off; choosing one replaces them.
- Shape, for points: a circle, a square, a triangle, a thin Plus (+), as survey plans mark a spot height, or Icon, which opens the icon library — your workspace's own symbols first, where it has them, then utilities, water, electricity, gas, wells and geology, topography. Type in Find an icon to look one up by name, or browse the groups, and click one. The colour and Size apply to the icon as to a shape, and it is drawn the same in the legend, in print and in the mobile app. The icon's button shows the chosen one; click it to choose another.
- Icon of a value, for points coloured By a field: open a value and choose its own icon, so each value can have its own symbol as well as its own colour. As the layer — the default — draws the value with the layer's shape or icon, in the value's colour.
- Label on the map: a field whose value is written beside each feature.
Studio's style editor has the rest — hatching, signs of a standard, labels built from several fields (see Styles and layouts). A layer coloured by ranges of a number, as styles brought from ArcGIS often are, keeps its ranges: Style on the map says so and leaves them as they are, and so does Studio's style editor. To change the ranges, apply an ArcGIS layer file (.lyrx) to the app in Studio with From an ArcGIS file (see Styles from an ArcGIS layer file), or ask the people who look after your apps.
The full style editor, for a client's owners. A client's owners have the whole style editor for a layer of their client's apps — hatching, signs of a standard, labels and their placement, classes by a field's values — without Studio: Edit style in the layer's information on the map opens it, beside a preview of the layer. Save and go back returns to the map, on the same view. The style is saved for this app's layer only: another app that shows the same data keeps its look. The editor offers only the fields the client's people see. A layer whose style came as it was delivered (an imported SLD) is not changed there; ask the workspace's team. Nor is a layer whose style or label draws by a field shown to the workspace's team only, or by a field the app does not show: the page names the field, and the workspace's team can open it to everyone. Studio warns the team when a label or a class draws by a team-only field, and when a field a style draws by is made team only. Where the workspace keeps its editors to their data, a client's administrators do not change styles; the client's owners do.
Adding a layer from the workspace's data
A layer that is already in the workspace's data can be put into the app from the map by the app's administrators: the workspace's owners, administrators and editors, and a client's owners and administrators in the client's apps. It does not need the app's editing to be on, since it changes the app, not its data.
- Open Layers and choose Add from data (the database button beside the Find a layer or folder box).
- Find the layer: open the data's folders, or type part of its name in Search the data.
- Choose the layer, and under Put it in the folder of the app's layer list it goes to (or the top of the list).
- Choose Add to the app. It is added for everyone who opens the app, switched on, with its usual style, and the app keeps the change in its versions as any other change.
The list holds only the data you may use in this app: what you can see, as far as this app's own area goes. A shared layer that several areas or clients use — one table of parcels cut by a district code, for example — is offered marked This app's part, and only this app's part is added: the layer is cut by the same field and values as the app's other layers when it has that field (a town's app cuts it to its town), or as the client's apps already draw it. Data that belongs to another client of the workspace is never offered. To place a layer in several apps at once, or a different part of a shared layer, use Studio → Datasets.
Drawing and changing features
In Edit features, choose the layer at the top of the panel. Only that layer's features can be picked. The layer's tools and the feature's actions — Save, Reshape, Duplicate, Copy to layer…, Attach, Cancel and Delete feature — sit together in one block at the top that stays in view; the feature's fields, its Files and its History scroll under it.
- A new feature: choose Add. The panel becomes the new feature's own, Add feature and the layer's name at its head, as for a feature opened from its card: Cancel at the top (with Point from my location on a layer of points), then how to draw it. Click on the map — once for a point, point after point for a line or an area, then Finish shape, which stands at the top while you draw. The form opens with Save, Cancel, Photo and Attach at the top: fill it in and Save. The layer's own tools (Load into this layer, Undo my last edits, New layer, the choice of layer and the modes) are under Edit the whole layer at the bottom of that panel; the new feature stays in the form there.
- A rectangle or a circle: on a layer of areas, Add offers Free, Rectangle and Circle. A rectangle is dragged on the map from one corner to the opposite one, a circle from its centre outwards; the form opens when you let go.
- A shape from a drawing: when drawings are shown on the map (the Draw tool), Add lists their shapes that fit the layer — areas for an area layer, lines for a line layer, points for a point layer — under Copy a shape from a drawing. The chosen shape becomes a new feature of the layer; the drawing stays as it is.
- Snap: while you add a feature, split, reshape one or drag one whole, each corner you place or drag (or the point you hold a moved feature by) goes to the nearest corner — or else the nearest edge — of the layers shown on the map, within the distance in pixels beside Snap. A ring on the map shows where the next corner will go: filled on a corner, hollow on an edge. Snapping is on by default; switch it off to place corners freely.
- Right angles: for lines and areas, each new corner is placed square to the side before it, and Finish shape squares the last corner too — three clicks draw a rectangular building of any orientation. A corner that snapped to something is left where it snapped.
- A layer the app filters — a shared layer shown in each app only for its own area or client, by a field such as a district code — fills that field in for you on a new feature, from the app's filter (or offers its values to choose from), so what you draw stays in the app; an editable copy of such a layer keeps the filter.
- Change a feature: choose Change and click it on the map. Its attributes open in the panel; change them and Save.
- Move: after clicking a feature, drag it on the map to its new place. The whole feature moves, every corner alike, and it is saved when you let go, as one change in its history — values typed in the form and not saved yet stay in the form. With Snap on, the point you hold goes to the nearest corner or edge.
- Reshape: after clicking a feature, choose Reshape. Drag a corner to move it, drag a small midpoint to add one, drag the shape itself to move all of it, press Delete to remove the corner you hold, then Save.
- Duplicate: after clicking a feature, choose Duplicate. A copy with the same attributes is made on the same spot and opens in the panel, ready to be moved by dragging it on the map or with Reshape. Save keeps it; Cancel removes the copy again, as Undo would (and Redo brings it back).
- Dragging a feature: a feature open in the panel can be dragged whole to a new place; the move is saved when you let go. Cancel puts it back where it was when you opened it, unless you chose Save since. A copy or a feature that someone else has changed in the meantime is left as it is, and the panel says so.
- Copy to layer…, beside it, puts that one feature into another editable layer of the app, choosing which field goes where; choose Move in that dialog and the original is deleted in the same step, which moves the feature to the other layer. Several features at once: select them with the Selection tool first, then come back to Edit features — see Copying features into another layer.
- Escape and closing: Escape goes back one step at a time — a shape being drawn, a shape picked up or an open form is put down first, then the mode returns to Select, and only then does Escape leave the tool. Closing the panel with × does all of it at once: the next Edit features starts at the choice of a layer, with the layer you had still chosen. A feature's own panel — a new feature's (Add feature) or one opened from its card (Edit feature) — closes everything instead: Cancel, ×, Escape and, for a new feature, Save put the panel away (on a phone its sheet too) and leave the map clear. Layers on the rail brings the layer list back. Files picked for a new feature and not saved are given up only after you say so.
- From a feature's card: when you click a feature of a layer you may edit, its card on the map has Edit data and Move. Edit data opens a panel for that feature only: Save, Cancel, Move for a point or Reshape for a line or an area, and ⋯ with Duplicate, Copy to layer…, Attach and Delete feature, then its fields, files and history. Edit the whole layer, at the bottom, opens the full Edit features panel with the feature still open. Cancel or × closes the panel and leaves the map clear. Move on a point waits for you to tap or click its new place on the map, and saves it there at once; on a line or an area it opens Reshape. The card offers neither on a layer you may only view.
- Delete feature removes it, after asking.
- History, under the form, lists every change to the feature — who, what, when — with Restore beside each earlier version (see below).
- Saved. in the panel, after Save, says the change is kept; it is then listed in the feature's History. A change not saved is lost when the page is reloaded.
- Measures fields — the Shape_Length and Shape_Area that layers from ArcGIS and CAD carry (also length and area, and the same names in other languages) — are filled in on every save of a shape, in metres and square metres on the ground, so they never keep the old shape's value.

If someone else saved the same feature after you opened it, your save is refused with a message rather than overwriting their work: open the feature again and save yours on top.
On a phone
In a phone's browser the site adds, edits, attaches files and takes photos as on a computer, under the same rights. On a phone, where Edit features may sit under More, an Add button stands at the bottom corner of the map whenever you may add features to at least one layer. Tap it for the list of those layers, under the folders of the layer list (with a search box when there are many); tap a layer and the new feature is drawn at once — tap the map for a point, point after point for a line or an area — and its form opens in the panel below. Saving, the app's filter and every other rule are those of Edit features. With a finger, as with the mouse, you hold a corner or the shape in Reshape, and a feature opened in the form, to drag it.
The new feature has a panel of its own from the first tap, as on a computer: Cancel (and Point from my location on a layer of points) at the top while you draw, then, once the new feature is on the map, Save, Cancel, Photo and Attach stay pinned at the top while you scroll through its fields. Photo opens the camera and Attach picks files on the phone; they wait in the form and are uploaded with the feature when you save, under the same rules as a feature's Files (the kinds of file, the size limit, the workspace's storage, and only on a layer you may edit). If a file cannot be uploaded, the feature is still saved and the file is kept in its panel with the reason, for Try again. On a layer of points, Point from my location places the point where the phone is — the browser asks your permission the first time — and says how accurate the reading is; tap the map to move it before you save. After Save, and after Cancel or ×, every window of the add closes and the map is clear for the next one, with the Add button back at the corner; on a computer too, a new feature saved or cancelled closes the form, the tool and the panel.
Loading a file into a layer
A layer that already exists — one made in Cartema and still empty, or one you keep up to date — can take the features of a file. Choose Load into this layer at the top of Edit features (it loads into the layer chosen there), or on the layer's page in Studio → Datasets.
- Choose the File: a zipped shapefile, KML or KMZ, GeoJSON, GeoPackage, CSV or Excel (.xlsx, .xls, .ods), DXF or DWG. For a file that carries no coordinate system — a CAD drawing, a shapefile without its .prj — choose its Coordinate system. Choose Upload: the file is read beside the layer, and nothing is added yet.
- Part of the file: a file with several layers, a workbook with several sheets, or a drawing — its lines, areas, text and points — offers its parts; choose the one to load. It must hold the layer's kind of shape: points into a layer of points, lines into lines, areas into areas. Shapes in several parts are accepted wherever the layer takes them.
- Points from columns, for a CSV or a spreadsheet: choose the columns for X or longitude and Y or latitude (columns with the usual names are chosen for you) and their Coordinate system. Such a file loads into a layer of points.
- Fields: each field of the file goes into the layer's field of the same name or label. Change any of them, or choose — not loaded; the fields not loaded are listed under them.
- Choose Add to its features, or Replace all its features (see below), and Load.
The shapes are brought into the layer's coordinate system, and every value is converted to its field's type: numbers with a decimal point or a decimal comma, dates as 2026-10-20 or day first (20/10/2026), yes and no in English, Portuguese or Hebrew. A row is loaded when every value fits its field — the field's rules included — and the row lies inside the app.
When it is done, the window says how many features were added, how many rows were skipped (no shape, a shape of another kind, or outside the app) and how many had errors (a value that does not fit its field), and offers Download the rows not loaded: a spreadsheet with each row's number in the file and the reason. Studio → Jobs keeps the same record.
- Every loaded feature has a history row, Loaded from the file's name, and can be changed, restored or deleted like any other. Lengths, areas, who made it and when are filled in as on a save.
- In an app that shows only part of a shared layer, the app's field is filled in with the app's value where the file leaves it empty; a row with another value is not loaded.
- A layer with a definition query (see Studio: apps) takes only the rows it would show, and Replace all its features removes only the features it shows; the other rows are skipped and listed.
- Fields kept to the workspace's team are not offered to a client's people, and keep the value Cartema gives them.
- Replace all its features is for the workspace's team — its owners, administrators and editors — and for the author of a layer in My layers; a client's people, their owners and administrators included, add to a layer. It first removes the features the layer has in this app — after asking once more — then loads the file. Each removed feature keeps its history and can be restored from it. If nothing in the file can be loaded, the layer is left as it was.
- A load takes a file of up to 512 MB and up to 200,000 features.
- A file that was read but not loaded is discarded after a day; Cancel discards it at once.
Going back to an earlier version
Nothing in a feature's history is ever rewritten. Going back is a new change of its own, recorded in the history with your name like any other save, so it can itself be undone the same way. Versions are kept for 90 days (longer where your plan says so); the history lists the ones still kept.
- Undo and Redo, the two arrows at the top of the panel, take your own changes in Edit features back one step at a time, and put them back — a save, a move, a restore, a feature added or deleted, a value changed in the attribute table — since you opened the app. A change of several features at once is one step: a Split (the new pieces are removed and the features get their shape back), a field changed on all the selected features, or copies made with Duplicate. Ctrl+Z (⌘Z on a Mac) undoes and Ctrl+Shift+Z (⌘⇧Z) redoes, except while you type in a field. A step on a feature that someone else has changed since is refused and left as it is; a step of several features is refused whole if any one of them has changed.
- Restore a version: click the feature, and in its History choose Restore beside the version you want. Its shape and its values come back as a new version; the history then shows Restored version ….
- Bring back a deleted feature: right after Delete feature, choose Bring back beside the Deleted message. The feature returns as it was, with its number and its attached files.
- Undo my last edits, at the top of the panel, takes back your own latest editing session on the chosen layer: the changes you made there in the last 24 hours, back to the first pause of more than 30 minutes between two of them. The panel says how many changes to how many features it will undo, and when they were made; confirm with Undo them. Each feature goes back to what it was before your first change of the session: one you added is removed, one you deleted comes back. It works once per session — what you change afterwards is the next session.
What a restore or an undo writes follows the same rules as a save:
- Only whoever may edit the layer can use them, and not while the workspace is read-only.
- Fields you cannot see in this app keep their current values.
- In an app that shows only part of a shared layer, a version that would move the feature out of the app is refused, and a feature that is no longer in the app is left alone.
- If someone else changed the feature after you opened it, the restore is refused with the same message as a save. Undo my last edits never touches someone else's work: a feature someone changed after you is left as it is, and the panel says how many were left.
Several features at once
Select features of the layer being edited — with the Selection tool, by picking rows in the attribute table, or straight on the map in Edit features: Shift-click (or Ctrl-click, ⌘-click on a Mac) features of the chosen layer to add them to the selection, as many as you need; Ctrl-click one already selected takes it out. A plain click still opens one feature in the panel. The other features of the layer stay on the map while you select, the selected ones outlined in pink; Show only the selected on the map, under their count, hides the rest until you switch it off. Clear selection, beside the count, unselects them all — so does Escape when no feature is open in the panel. The panel shows how many are selected, with these tools:
- Duplicate them, on the same spot, into — this layer, or another editable layer of the app that takes the same kind of shape. Attributes are carried over by field name; a field the other layer does not have is left out, and a field you cannot see in this app is not carried into another layer. Each copy is a new feature: who made it and when are yours, its length or area is measured again, and in an app that shows only part of a shared layer the copy gets the app's value, as a feature drawn there does. Features of your own layers under My layers are copied within the same layer.
- Change a field on all of them — choose the field and its new value, then Apply to …. Every selected feature gets the value, each as a change of its own in its history, with the same checks as a save: a value the field does not take, or one that would move the features out of the app, is refused and nothing is written. Features that already had the value are left alone; the workspace's team is told how many those were, a client's people how many features hold the value now.
- Delete … — asks first, naming how many, then deletes every selected feature, each written in its history as a feature deleted by hand, with the same checks as deleting one. Undo brings them all back in one step. Up to 1,000 features at a time.
Copying features into another layer
Copy to layer moves surveyed work into the layer it belongs to — for example an As Made survey of new pipes, delivered as a layer of its own, copied into the water network layer — choosing for each field where its value comes from. It works on a selection, and is offered in three places:
- the attribute table's toolbar on a Selection tool's results, for the rows selected in the table or, with none selected, all the results of that tab;
- the attribute table's toolbar on a whole layer, once rows are selected;
- Edit features on Change, under the selected features, beside Duplicate — and on the one feature open in the panel, beside its Duplicate.
- Under Into the layer, choose where the copies go: the app's editable layers that take the same kind of shape (points, lines or areas) are offered.
- Check which field goes where. Each field of that layer is filled from the field of the selected features with the same name — capitals, spaces and underscores aside — or from your last choice for the same two layers, which Cartema remembers for you. For each field you can choose another field, A fixed value (the same for every copy), or Left empty. The fields that fill themselves — who made a feature and when, lengths and areas, and the app's own value in an app that shows only part of a shared layer — are not in the list.
- Read the Preview: the first features as they will be copied, and how many values will not convert to their field's type — a word in a number field, a date that cannot be read, a text longer than the field takes, a value that is not in the field's list. Those are left empty in the copy. Dates are read as year-month-day or day first (20/10/2026). If the copy would be refused — a required field left empty, a value outside the app — the preview says why, and Copy waits until it is fixed.
- Choose Copy or move: Copy keeps the originals where they were; Move deletes them from the layer they came from in the same step, so the features change layer. Moving is offered only where you may change the layer they come from.
- Choose Copy — or Move.
The copy is one step: Undo this copy in the window, or Undo in Edit features, removes the copies and brings the deleted originals back, all together. Each copy is a new feature of the layer, with its shape as it was — reprojected if the two layers came in different coordinate systems — and its length or area measured again; its history says Copied in from another layer. Studio → Activity shows the copy once, with both layers and the number of features.
What you may copy follows the same rules as everything else: you need to be able to edit the layer you copy into, and to see the features you copy. A field kept to the workspace's team, or hidden in this app, is neither offered to copy from nor to fill for those who cannot see it. Up to 500 features are copied at a time. Features of your own layers under My layers are not copied into the app's layers this way: use Submit to the workspace… on the layer instead.
Merging, splitting and clipping features
Three more tools in Edit features, as in ArcGIS: Merge joins features into one, Split cuts lines and areas in two with a line you draw, Clip cuts features with an area you draw. They work on the layer chosen at the top of the panel, keep a history of every feature they change, and either do everything or nothing.
Merge
- Choose Merge.
- Click the features to merge on the map — a second click takes one out again. Or select them first with the Selection tool and choose Use the selected features.
- Under Keep the attributes of, choose the feature whose name, land use and other attributes the result keeps.
- Choose Merge. The features become one; the others are removed.

Lines that meet end to end become one line. Points cannot be merged, and a layer that takes one part per feature (delivered data often does) refuses a merge of features that do not touch.
Split
- Choose Split and draw the cutting line on the map: click its points, and double-click the last one (or press Finish shape).
- Choose Apply split.
It splits the selected features of the layer that the line crosses, if any are selected; otherwise every feature of the layer the line crosses. For each one, the biggest piece keeps the feature — its number, its history and its attached files — and every other piece becomes a new feature with the same attributes. Lengths and areas are measured again on every piece. A feature made of several parts, or one the line only touches without cutting it from side to side, is left as it is, and the panel says how many. Draw again starts a new line. To put the pieces back together, use Merge.
Clip
- Choose Clip and draw the cutting area on the map: click each corner, and double-click the last one (or press Finish shape).
- Choose what to keep — Keep the part inside the area, or Cut the part inside away — and, under Write the result to, where the result goes:
- A new layer (this layer stays as it is) — for the people who arrange the app's layer list; give the new layer a Name, and choose the App it goes to (this app, or another app of the same client whose layer list you arrange) and its Folder: the top of the layer list, one of the app's folders, or a New folder you name. The new layer keeps the layer's fields, and a field kept to the workspace team stays so.
- This layer: cut its features — the layer's own features are changed, for everyone who uses it. Cartema asks you to confirm with Cut the layer.
- Choose Apply clip.
It cuts the features of the layer that are selected, if any are; otherwise every feature the area touches. A feature left with nothing is removed. The panel says what was done: how many features were cut and removed, or the new layer's name, where it was made and how many features it holds. After cutting the layer itself, Undo clip puts every feature back as it was. Draw again starts a new area.
Your own layers under My layers are always cut in place.


Fields in the attribute table
Open the table with Attribute table in the rail, or in a layer's menu, and choose the layer at its top left. On an editable layer the table's bar offers Add field and Calculate field. Each column's small arrow opens its menu: Sort ascending, Sort descending, Statistics, Move left, Move right, Hide column, Freeze up to this column, Reset columns, Calculate field, Delete field.

Fields are added and removed by the people who manage the app's layers — the workspace's owners, administrators and editors, a client's owners and administrators, and whoever's role on the app is Administrator — and only where they reach all of the layer's data: on a layer shared by several places, each app showing its own part, only somebody who sees every part adds one, as the new column is in all of them. A client's owners and administrators change the fields of a layer that only their client's apps show. Deleting a field removes its values; each feature's history keeps what they were.
Adding a field from the table
With Edit switched on, the last column of the table's header reads + Field. It opens the same form as Add field in Studio: the field's name, its type and, if you want a list to choose from, its allowed values. The column appears in the table at once, ready to fill in.
A layer whose data comes from a source outside Cartema — a delivery of files, or data brought over from another system — takes new fields too. Such a field is Cartema's own: when the layer is updated from its source, the field stays, with its values, row by row (rows are matched by their GlobalID or OBJECTID, or by the file's own feature ids where the file keeps them). If the source later brings a column of the same name, it arrives beside yours as name_source. Only the fields added in Cartema can be deleted on such a layer; its other fields belong to the source. Studio's page for the layer marks them Added in Cartema.
Changing values in the attribute table
On a layer you may edit — an editable layer of an app whose editing is on, when you may change its data (see Who can do what above), or a layer of My layers you may change — the table's bar has an Edit switch. Switch it on to change values in the table itself, as in a spreadsheet:
- Double-click a cell, or select it (click it, or move to it with Tab) and press Enter, to change it. Typing a letter or a digit on a selected text or number cell starts with that character.
- Enter saves the value and stays on the cell; Tab saves it and moves to the next cell you may change (Shift+Tab to the one before), on to the next row at the end of a row; Escape leaves the cell as it was. Clicking elsewhere saves it too.
- Each kind of field has its editor: text; a number, written as numbers are written in your language (a decimal comma in Portuguese, a point in English and Hebrew); a date, or a date and a time; Yes or No; and a list for a field with allowed values, or for the field the app's filter keeps to a few values. A value the field cannot take is not saved: the bar under the toolbar says why, and the cell stays open to correct it. A required field cannot be emptied.
- Some cells cannot be changed: the fields that fill themselves on every save (who made or changed a feature and when, a length or an area, the area code), the field the app's filter fixes to one value, photos, and fields the app does not show you. Who made a feature and when, and any column naming a person, are kept by the record: Edit features shows them without letting them be changed, and no change writes them.
- Each value is saved as a change of its own, exactly as a save in Edit features: it is checked by the same rules, written in the feature's history and in Studio → Activity, and it is a step of Undo and Redo — the two arrows beside the switch, or Ctrl+Z and Ctrl+Shift+Z (⌘Z and ⌘⇧Z on a Mac) in the table.
- If someone else changed the feature after the table showed it, the cell takes their value when you open it and says so. If they save while you type, your value is not saved: the cell shows theirs and the bar says what it is now, so you can decide again.
Sorting, paging and the selection work as usual while Edit is on. A double-click on a cell you may change opens it instead of going to the feature; Zoom to, or a double-click on the row's number, still goes there.
Calculating a field
Calculate field fills a field for every feature — or only for the selected ones, when features of the layer are selected on the map.
From the geometry
| Property | For | Units |
|---|---|---|
| Area | Polygons | m², ha, km², dunam, acre |
| Perimeter | Polygons | m, km, ft, mi |
| Length | Lines | m, km, ft, mi |
| X, Y | All | In a coordinate system of the app, e.g. a national grid or WGS 84 |
Areas and lengths are measured on the ellipsoid (geodesic): true on the ground whatever the map's projection. X and Y use the same coordinate definitions as the numbers under the pointer.

From an expression
| Write | Means | Example |
|---|---|---|
[field] or !field! |
A field, by column name or alias | [area_ha] * 10000 |
'text' |
Text (a quote inside is written twice) | 'Lot ' & [number] |
+ − * / |
Arithmetic (dividing by zero gives an empty value) | ([a] + [b]) / 2 |
& |
Joins text | [street] & ' ' & [house] |
$area $perimeter $length |
The feature's own measurement, in m² or m | round($area / 1000, 2) |
$x $y |
Longitude and latitude (WGS 84) | round($y, 6) |
fid |
The feature's number | 'P-' & fid |
Functions:
- Numbers:
round(x)round(x, n)·absfloorceil·sqrt(x)·power(x, n). - Text:
upperlowertrim·lenleft(t, n)right(t, n)·mid(t, start)mid(t, start, n)(the first character is 1) ·replace(t, find, with)(every occurrence; capitals count) ·concat(…)·coalesce(…). - Dates:
today()now()·year(d)month(d)day(d)·dateadd(d, days)(a negative number goes back) ·datediff(d1, d2)(the days from d2 to d1). For exampledatediff(today(), [survey_date])is the age of a survey in days.

The result is written as the field's type takes it: into a whole number it is rounded, into text it is written as text. A value the field cannot take stops the calculation with a message, and nothing is written. A feature whose value was already right is left alone.
Messages you may see
| Message | What to do |
|---|---|
| editing is switched off in this app | Ask your workspace owner to switch editing on in Studio |
| this layer is not editable; make an editable copy of it first | Make a copy and work on the copy |
| fields can be added only to layers made in Cartema | The layer is delivered: add the field to a copy |
| there is no field “…” in this layer | Check the spelling; use the buttons under the expression box |
| changed by somebody else | Open the feature again and save your change on top |
| nothing of yours to undo on this layer | You made no changes there in the last 24 hours, or they were undone already: restore single features from their history |
| you have changed this layer since; look again | Choose Undo my last edits again to see the session as it is now |
| a copy goes into a layer of the same kind of shape | Choose a layer of points, lines or areas as the features are |
| the line does not cut across any of these features from side to side | Draw the line so that it crosses the feature completely |
| some of the chosen features are not in this layer any more | Select the features again: someone changed or removed some of them |
| this part of the file holds no points (lines, areas), which is what this layer takes | Choose another part of the file, or load it into a layer of that kind |
| replacing a layer's features is for the workspace's team; you can add to its features | Choose Add to its features, or ask the workspace's team |