CARTEMA
Open Cartema

For editors and owners

Building apps in Studio

Create apps, file them in folders, find a layer across apps, set who opens them and each person's role, set their map, add external map services, arrange their layers and who sees and edits each one, allow editing, build field packs, and go back to an earlier version.

Updated 2026-11-13For editors and owners of a workspace

Studio is where apps are built. It opens from the Studio button on the apps page, for editors, administrators and owners. Its menu on the left: People, Apps, Datasets, Styles, Orthophotos, Plan sheets, Jobs, and for administrators and owners Usage, Activity, Work log, Plan and usage and Invoices (and Branding where it is turned on).

Apps and folders

Studio → Apps lists the workspace's apps with their address, visibility, version and dates.

  • New folder makes a folder where you are; open a folder by clicking it, go back up with the path at the top.
  • Tick apps and folders, choose a destination in Move to (or Top level) and Move — many at once.
  • A folder's Rename and Delete folder are in its row. Deleting a folder moves what was in it up one level; no app is ever deleted with a folder.
  • Find an app or a layer searches every folder: the apps whose name has what you type, and below them Layers in your apps — every app's layers whose name, folder, dataset or table has it. Show in the app's list opens the app's page at that layer; Open layer opens its fields and style.
  • New app, at the bottom: a Name, an Address (lower-case letters, digits and hyphens — it becomes part of the app's link) and a Visibility. A new app is filed in the folder you are in.

Visibility: Private — the workspace's members; Public — anyone with the link, without signing in.

An app's page

Open an app in Studio to set it up. Open shows it as users see it.

Each section of the page folds: click or tap its heading (or press Enter or Space on it) to collapse or expand it, and Collapse all or Expand all at the top does every section at once. Your choice is kept in this browser for each section, on every app's page. A long section starts collapsed until you open it — 3D models with more than 8 models, Who can open it with more than 12 people, Field packs with more than 8 packs — and shows how many rows it holds beside its heading.

On a long page, once you scroll down, a small bar at the foot of the panel says where you are: the section, and in the layer tree the folder you are in, with the folders it is in. Click it for the list of the page's sections and go straight to one (it opens if it was collapsed); Back to top returns to the top of the page.

Name, address, visibility

At the top. Save keeps the change.

Who can open it

A private app is open to everyone in the workspace, or to only these people: a list of the workspace's members, each a Member or an Administrator of the app. An administrator also changes the app's settings and this list, adding people from the apps they already share with them; opening an app to the whole workspace is for the workspace's owners and administrators. Owners and Cartema support open every app whatever the list says. Once a workspace keeps one app to listed people, every new app starts that way too, with whoever made it as its administrator; open it to the whole workspace afterwards if it is meant for everyone. An app that belongs to a client is opened by that client's people and the workspace people assigned to it, whatever its list; see Clients.

Under People, each person is listed with their role on this app, and the heading counts them — 12 people · 2 administrators · 3 editors · 7 viewers. A person's role can differ from app to app, and is changed here for this app alone:

  • On an app kept to listed people, a workspace Viewer can be made Editor or Administrator of this app only; As their role makes them a viewer of it again. The workspace's editors and administrators are a Member or an Administrator of the app: choose one and Save.
  • On a client's app, the client's editors and viewers can be made Viewer, Editor or Administrator of this app; their client role is the default. The client's owners and administrators, and the workspace's team, show their role as a word: they manage every app of the client. People of the client opens the client's People.

What each role can do, and who may change whose role, is in Roles per app.

Access until a date. On an app kept to listed people, a person's access can end on a day you choose — for someone trying the app for a fortnight, a visiting consultant, a contractor. Access until… beside the person sets the last day they can open the app (or 14 days from today at one press); the row then shows until 24 Nov. From the next day the app no longer opens for them, and Cartema takes them off it by itself, as Remove would: the change is in Studio → Activity, an invitation of theirs to the app that is still open is revoked, and if this was the only app of a workspace Viewer, they are taken out of the workspace too (never an owner, an administrator, an editor, a client's person or Cartema support). Three days before the date, the workspace's owners get one e-mail listing whose access ends when, with a link to each app's people; the person is not e-mailed. +14 days moves the date on by 14 days, and No end takes it away. Who may set it is whoever may remove the person from the app: the app's administrators (not over another administrator of it, nor over their own access), the workspace's owners and administrators. It is not offered on a client's app, whose people open it through their client. The date can also be set when inviting someone; see Inviting people to an app.

A person kept to some apps sees only those apps on the apps page, and in Studio only those apps' data and their own: the datasets they imported and their private layers. Of a table that several apps share, each showing part of it through a layer filter, they see only the rows their apps show — in the table, its CSV, the map preview, exports and counts — and changing the table itself (its name, its fields, deleting or replacing it) is left to whoever sees all of it. Administrators are kept to their apps like anyone else; to use Studio at all, an administrator of an app needs the Editor role in the workspace.

Editing in this app

Off or On — whether the app's data can be changed from its map. It decides first: while it is Off, nobody changes the app's data from the map, whatever the people's roles, the layers' Editable boxes, Who edits it and the named editors say. See Layers and editing.

3D models

Shown for an app that has 3D models on its map. At the top, The app's triio project links the whole app to its project in triio: paste the project's link and Save, and the viewer's rail gets a triio button for the app — beside the map for a public link, in a new tab for a members' link; empty the field and save to take it off. The same links are accepted as for a model (below). A model whose own link is that same project then shows no triio button of its own in the app; one linked to another project keeps it.

The models are listed in the order of the app's 3D panel, numbered. A model added to the app goes in by its date, newest on top; the arrows on each row move a model one place up, one down or to the top, and Sort by date (newest first) puts the whole panel in date order again (models without a date last). The viewer's 3D panel shows the same order. Locate in Find content opens this section on a model.

Each model can be linked to the same model in triio: paste the triio project's link into triio link and Save, and the model's row in the app's layer list gets Open in triio; empty the field and save to take it off. Only a triio project link is accepted: the project's public link (https://app.triio.io/public/…), which opens for anyone, or its members' link (https://app.triio.io/project/…), which asks for a triio login. A link on triio's own address for your organisation (https://<name>.triio.io/public/…) is accepted the same way. A public app shows only public links to its visitors. A public link also gives the row Show beside the map, which opens triio's viewer next to the map in the same tab. Changing a link is a new version of the app, like any other change. See The map.

Under each model, Ground height (m) sets how far the model is lowered to stand on the map, which is flat at height 0. Left empty, it is automatic, and the field shows the value used: a model that is already on the ground is left as it is, and a model surveyed at its real height is lowered by its lowest point. Where that leaves the model floating (a deep pit or a river bed in the survey) or sunk, type the height of the ground around the model — the height you would read on site — and Save; empty the field and save to go back to automatic. It changes only where the model is drawn on the map, not the model itself. The ground height is for the flat map, and only where the model cannot be laid on the 3D ground's heights instead: while the app's 3D ground is on, the flat map lowers each part of a model by the ground's height under it, and uses this height only where the ground has no heights for the model's area or the model's heights do not stand near that ground. On the 3D ground a model stands at its own heights.

3D ground, above the models, is on unless switched off: a tilted map with a model shown then stands on the ground's real heights — a world terrain model with cells of about 30 m, and the app's own terrain models where the app has them (raster layers whose values are heights, named like a DTM or a DEM, with Everyone exports ticked; switched off in the tree still counts, a DSM does not, nor does a raster whose heights hold buildings or trees — see Use as 3D ground on the raster's page in Importing data) — and each model at its own heights. Off, the map stays flat and each model is lowered by its ground height. On, a model on the flat map (not tilted, or with a viewer's 3D ground unticked) is laid on the ground's heights part by part. With the 3D ground on, each model also has Heights: what its heights are measured from, used on the 3D ground and on the flat map alike. Automatic suits most models: a model converted by Cartema keeps its survey's heights above sea level, and any other 3D Tiles model is taken to be in ellipsoidal heights (WGS 84, as GNSS measures them), brought to sea level by the geoid (EGM2008; about 20 m in many places). If a model stands about that much above or below the ground, choose the other one. See The map.

Ground under the models (m), below the switch while it is on: where a model has data, the 3D ground is lowered by this many metres, easing out just past the model's edge, so the terrain never shows through the model where the two disagree — a world terrain model with 30 m cells is coarse, and a terrain model from another survey can be a few metres off. Only where the model has data, not over its whole rectangle: a long, narrow corridor lowers a long, narrow strip. Empty is the default, 8 m; type more if the ground still pokes through a model in places, or 0 to leave the ground as it is, and Save. It changes only how the map is drawn, not the terrain models or the heights read from them.

Easing around the models (m), below it: over how many metres past a model's edge the ground eases back up, 40 by default. Near a model, the ground may also stand only a few metres above the ground at the model's edge. This matters most in towns, where the world terrain model can still hold roofs and trees: without it, they would stand around a street's model like walls. Type more for a gentler slope, and Save. Empty is the default. Like the field above, it changes only how the map is drawn.

Map settings

  • Initial extent — the area the app opens on. It is automatic at first: it frames the layers the app opens with switched on (so a zoning plan or a regional boundary left off does not stretch it), ignores the odd feature far from the rest, and follows every change to the app's layers. Type other edges and it is set by hand, staying as typed; Use the layers' extent makes it automatic again.
  • Coordinate systems offered — those users can choose at the bottom of the map; the first is the default.
  • Basemaps — Map, Light and Satellite, and which one opens by default. A basemap from an online map service is added under Map services (below). A region's licensed orthophoto service, where an app offers one, is added to the app by Cartema support.

Map services

An app can draw an external map service — a WMS, a WMTS, or an ArcGIS MapServer or ImageServer — as layers of its tree or as one of its basemaps. The app's administrators add one: the workspace's owners and administrators, and a client's owners and administrators or the app's administrators in their own apps. The same window opens from the map, with the globe button at the top of the layer list.

  1. Add a map service, and paste the service's address. An address with credentials in it — user:password@, or a token or key in its query — is accepted: they are kept as a workspace secret, used only by Cartema's server, and never shown again in full.
  2. Read service. Cartema's server reads the service's capabilities and lists its layers, in their folders. For an ArcGIS service whose tiles are cached in Web Mercator, the service is drawn whole from its cache; otherwise its layers can be chosen one by one.
  3. Choose one or more layers, and Add as Layers (one layer in the tree for each) or Basemap (one basemap, the layers drawn together; a WMTS gives one layer to a basemap).
  4. Give it a Name, check the Attribution — when the service gives one, it is filled in and must be kept, though it may be shortened — and, if needed, the Opacity and the zooms it shows between (From zoom, To zoom). For layers, choose the Folder they go into. Add.

The coordinate system is chosen for you. The map is in Web Mercator (EPSG:3857), so a service that offers it is drawn as it is, and an ArcGIS map or image service always draws itself in it. A WMS that offers only EPSG:4326 or EPSG:2039 (EPSG:6991) is asked for in that system and reprojected by Cartema, tile by tile; the list says so beside the layer. A WMS in any other system, and tiles cut in another grid — a WMTS matrix set or an ArcGIS cache not in Web Mercator, with no picture to ask for instead — cannot be shown: the list marks such a layer as unsupported.

Every request to the service is made by Cartema's server, never by a browser: the people who open the app see the service's tiles under the app's own address, and the service's address and credentials stay on the server. Only public internet addresses are asked, on the usual web ports (80, 443, 8080, 8443, 6080 and 6443). The service's tiles are kept on the server for some hours, so a service that changes its pictures shows the change within the day. A service that does not answer leaves its layer empty; the rest of the map is unaffected.

A layer from a service is in the layer tree like any other: rename it, move it, set who sees it, take it out. Its credit is shown in the map's corner and printed at the foot of the sheet. A basemap from a service is listed under Basemaps from services, with Remove; taking it out of the app leaves the service in the workspace's data (Studio → Datasets), where it can be added to another app or deleted.

The layer tree

The app's layers, top to bottom as they are drawn over each other, in the folders the map's layer list shows them in. Folders can hold folders, as deep as you need; the arrow beside a folder's name opens and closes it here.

Finding a layer

The box above the list finds a layer by a word of its name, of a folder it is in, of its dataset's name or of its table's name; every word you type must be found. Each result shows its folders and its dataset. Show in the list opens its folders and brings its row into view; Open layer opens its fields and style (where you add a field, for example).

Arranging the tree

  • Drag a row by its handle. A line shows where it lands — above or below another row — and a folder lights up when the row would go inside it, at its top. A folder moves with everything in it. While dragging, the foot of the list takes a row to the end of the tree.
  • From the keyboard: focus a row's handle, then ↑ and ↓ move it among its neighbours, → puts it into the folder just above it and ← takes it out of its folder (the other way round when the page reads right to left). The arrow buttons beside the handle do the same: Move up, Move down, Out of the folder, Into the folder above.
  • New folder, under the tree, makes an empty folder at the top, its name ready to type. A folder's New folder inside makes one inside it.
  • A folder's name is edited in its row. Visible by default on a folder: off, its layers start switched off when the app opens. Open when the app opens: whether the folder starts open in the map's layer list.
  • Delete folder removes the folder only: what it held moves up one level, in its place. No layer is removed with a folder.

Several rows at once

  • Tick the box at the start of a row to select it; Shift+click ticks every row between it and the last one ticked. A folder ticked takes everything it holds with it.
  • With rows ticked, a bar above the tree acts on all of them: Move into… a folder (or the top level), Up together and Down together (they move as one block), On at open and Off at open, Remove from app (after asking — only the app's list changes), and Move to another app… (see Moving layers to another app). Clear selection unticks them.
  • Nothing is kept until Save: the whole change is one new version of the app. After a save, Undo beside the note puts the version before back, as long as nobody saved the app since; History keeps every version as well.

Adding layers

  • Add layer…, under the tree, adds a dataset at the top of the tree.
  • A folder's Add layer here adds a dataset straight into that folder, or New empty layer… makes a new layer to draw into and puts it in that folder (save the tree first: leaving the page drops changes not saved).

Each layer

Column What it sets
Label The name users read
Dataset The data behind the layer
Style How it is drawn (the dataset's default style if none is chosen)
Filter Show only some features: FIELD = value, value. Only those features leave the server — on the map, in the table, search, exports, copies and the phone — and a feature drawn in the app is given the filter's value, so data shared by many apps stays each app's own
Definition query Show only the features that meet a set of conditions, on top of the filter — see below
Who sees · who edits Who sees the layer and who edits it, in short, with the Rights button that sets them — see Who sees it and who edits it
Visible by default On when the app first opens
Identify Answers a click on the map. Turned off, the layer's attribute values reach only the workspace's owners, administrators and editors and the people who may edit the layer: for everyone else it shows its features without values — in identify, the attribute table and its statistics, selections, history and exports — it is left out of search, and copies of its features carry their shapes only
Editable Its features can be changed from the map, when the app's editing is on

The ✕ at the end of a layer's row takes the layer out of the app, after asking — and only out of the app: its dataset and features are kept, in Studio → Datasets and in every other app that shows it. Deleting a dataset is done from Datasets, and asks too.

Save keeps the tree as a new version of the app; the map shows the same tree. One dataset can appear several times with different filters and styles — for example one layer per block.

Some tables hold the rows of many places and are marked as shared by them — a supplier's daily feed of meters for every town, for example, each app showing its own town. Every layer on such a table must carry its Filter on the field that tells the places apart, with at least one value: without it, everybody who opens the app would see every place's rows. A tree with such a layer is not saved, and the page names the layer and the field.

Definition query

A layer's definition query shows only the features that meet a set of conditions — for example Status is "active" and Year is at least 2020 — as a definition query does in other GIS programs. In the layer's Definition query column, Add (or the number of conditions it already has) opens the editor:

  • Each condition is a Field, an Operator and a Value, written as in the attribute table's query: Is, Is not, Less than, At most, Greater than, At least, Contains, Starts with, Is empty, Is not empty or Is one of (values separated by commas, semicolons or lines). The operators offered follow the field's type.
  • Up to ten conditions with + Condition, matched All (every condition must hold) or Any (one is enough).
  • Count says how many features the layer would show, out of those its filter keeps.
  • Apply puts the query on the layer, Remove the query takes it off; Save the layers to keep the change.

The query is applied on the server together with the filter, everywhere the filter is: the map, the attribute table and its CSV, identify, selections, search, zoom to layer, the editing tools, exports, prints, field packs and Buddy's answers. A feature the query leaves out is, for that layer, not there. Its legend lists only the classes the layer can show: those its features hold, or, on a layer people edit, every class but those the query keeps out (with Status is "active", the other statuses are not listed).

The query is set in Studio by the workspace's team. The app's own people never see it or change it, and it may use fields kept to the team: the layer simply shows fewer features. The editor warns when a condition uses such a field: a client's editors cannot read it, but which features the layer shows, and which of their edits it refuses, can tell them something of its values. An edit made through the layer must keep the feature inside the query — a change that would take it out is refused — and a new feature takes the value of every is condition it leaves empty when All conditions must hold. A condition on a field the data no longer has shows nothing, and the editor says so.

A definition query chooses what the layer shows; it is not a permission — to keep rows from people, use the app's filter or clients. The same data can be added to an app again as another layer, and Studio's data pages follow the apps' filters, not their layers' queries.

Moving layers to another app

Layers that belong in another app — loaded into the wrong one, or a group that should live elsewhere — are moved there with their settings, without adding them again by hand. Move to another app… is in the bar of the rows ticked, and the arrows button at the end of each layer's and folder's row moves that one.

  1. Into which app: the apps of this workspace whose layers you may arrange. Moving needs the same rights in both apps as arranging each tree here: the workspace's owners, administrators and editors (not one kept to data), or the Owner or Manager of a client, between that client's apps.
  2. Into which folder there: by default the same folders as here — the layers land in the folders of the same names, which are made there where missing, so Insight's structure stays as it is (a new תכניות or תרשימים folder goes right before מפות רקע). Or the top level, or any folder of that app.
  3. Move or copy: a move takes them out of this app; a copy leaves them here too.
  4. Preview shows, before anything changes: what is added there and where, each layer's style, whether it is on at open, editable and exported, and who sees it; the folders made; a folder merged into one of the same name there; what leaves this app; what that app already shows (not added twice — a move still takes it out of this app); and whose rights do not carry over: people named on a layer who do not open that app are dropped from its list there, and named editors are not carried over (name them again there).
  5. Move (or Copy) writes both apps together, as a new version of each, asking every right again — and only if neither app changed since the preview.

A folder moves whole, with its layers in their order. A layer keeps the rights it had here, never wider: if the folder it lands in there is kept to other people, only the people both lists name see it.

A client's data never goes into another client's app: a layer drawn by another client's apps, or another place's part of a shared table, is not moved, and the preview names it and why; nothing moves until it is taken out of the selection. A person's private layer stays in its app.

Undo, beside the note after the move, puts both apps back as they were, as long as nobody changed either since; otherwise it says which changed, and History of each app still has every version.

Buddy Pro does it in one message too: "move the electricity layers from Northfield to Northfield Utilities". It finds the layers and folders by their names in the first app, shows the same preview, and moves them on Confirm, with the same rights and the same Undo.

Who sees it and who edits it

Each layer and each folder of the tree has rights of its own, within the app's (who opens the app, above): who sees it, who of the app's editors edits it, and who edits it by name.

Setting a layer's or a folder's rights:

  1. Open Studio → Apps → the app and go down to its Layer tree.
  2. Find the row. Its Who sees · who edits column says its rights in short: Everyone, As its folder, 3 chosen or Administrators only; a lock when it is kept to chosen people; Edits: and who, when its editing is kept to chosen editors; and a green pencil with its named editors — two first names, or a count such as 87 named editors. Hover over the cell to read all of it; on a narrow window only the lock, the pencil and the button stay.
  3. Choose Rights (the key icon) on the row — every layer and every folder has one. The window Who sees and edits · the layer (or Who sees and edits the folder · the folder) opens.
  4. Set Who sees it, Who edits it and Named editors (below), and choose Apply.
  5. Save the layers, under the tree.

In the window:

  • Who sees it: Everyone who opens the app, or Only chosen people — tick people of the app by name (Find a person narrows the list), Everybody of the app's client, Everyone who edits the app or Everyone who only views the app. With nobody chosen, only the app's administrators see it.
  • Who edits it (a layer of features, or a folder): The app's editors, or Only chosen editors — editors by name, the client as a whole, or everyone who edits the app. It narrows who of the app's editors edits the layer, and an editor chosen here edits it even when its Editable box is not ticked; it never lets a viewer edit. To let a viewer edit one layer, name them under Named editors.
  • As its folder, offered for both inside a folder, takes the folder's setting. It is where every row in a folder starts.
  • Named editors: people who edit this layer — or, for a folder, every layer in it — even if they only view the app. See Named editors.

A folder's setting is the setting of every layer in it, folders inside it included, unless a layer (or a folder inside) sets its own: a layer inside a kept folder can be opened to Everyone who opens the app again.

Apply puts Who sees it and Who edits it on the row; Save the layers to keep them, as a new version of the app (its history says “Who sees or edits changed”). Named editors are kept as soon as you choose Apply.

From the map. The same window opens from the app's map for whoever manages the app's layers there — the workspace's owners, administrators and editors, a client's owners and administrators in the client's apps, and the app's administrators: Who sees and edits… in the … menu of a layer or a folder in Layers. There Apply keeps the change at once, as a new version of the app, named editors included. This is how a client's owners and administrators, who do not use Studio, set who sees and edits their apps' layers. It is not offered while the workspace is read-only, nor while viewing as someone.

Somebody who may not see a layer gets nothing of it, anywhere: the layer is not in their layer list (a folder whose every layer is kept from them is not there either), and neither its name, style, legend nor data reach them — not on the map or the iPhone, nor through identify, the attribute table and its CSV, search, selections, statistics, exports, copies, prints, field packs, Studio's data pages or Buddy. A print or a field pack someone else made of the app is not handed to people kept from any of its layers. Somebody who may see a layer but not edit it gets it read-only: no new or changed features, no calculator, no loading a file into it, no change of its look, and a copy of it never takes its place.

Kept layers are not passed on. Somebody who sees a layer kept to chosen people — but does not manage the app's layers — cannot copy it into their own layers (My layers), nor copy or duplicate its features into another layer; Cartema says This layer is restricted; ask the app's administrator, and the buttons are not offered. A copy or a clip of it made in an app keeps it to the same people, and never to more than the folder it lands in allows: when the two differ, only the people both let in see it. A copy made beside a layer that is open to everyone inside a kept folder stays open to everyone, as its original is. Shared bookmarks, the app's starting view (framed only by layers open to everyone) and somebody else's prints and field packs say nothing of layers kept from the reader.

Exporting. Downloading a layer as a file — the table's CSV, a selection's file, Export… and a photo's original — follows one rule: the workspace's owners, administrators and editors and a client's owners and administrators download any layer they see; everybody else only the layers with Everyone exports ticked. If a restricted layer has it ticked, the people who see it can download it; untick it for that layer to prevent that.

Who is never kept out. The workspace's owners, administrators and editors — who edit the app here, in Studio, and see its whole tree — and the app's administrators (a client's owners and administrators, the administrators listed on one of the workspace's own apps) always see and edit every layer, and are not offered in the lists. So rights per layer are for the app's viewers and, in a client's app, its editors. Cartema support is never listed to anybody but Cartema.

Who may be chosen. Only people who open the app: in a client's app, its people who have the app and the workspace's viewers assigned to the client; in an app kept to listed people, the viewers listed on it; in an app open to the workspace, its viewers. Somebody removed from the app, its client or the workspace sees nothing of it from that moment, and is taken off its lists at once: added back later, they get no layer right back until somebody chooses them again. That clean-up is saved as a new version of the app by Cartema. In a public app a visitor sees only the layers open to everyone.

Rights per layer are about an app's layers. Drone flights and their photos, 3D models and 3D scenes follow who opens the app.

Saving from an old page. If somebody changes the app while its page is open in Studio — a layer added from the map, say — Save does not write over their change: the page says so and reloads with the app as it is now.

A lock beside a layer or a folder in the map's layer list tells the people who see it that it is kept to chosen people. The same data shown by another layer that someone may see is theirs through that layer: to keep data from people altogether, keep every layer that shows it.

Named editors

An app's Named editors edit one layer, or every layer of a folder, whatever their role on the app — viewers included. This is how a person who only views an app looks after one layer of it: a survey layer, the requests of their own department.

  1. Open the layer's (or the folder's) Rights, as above.
  2. Under Named editors, type part of a name or an e-mail in Find a person, and click the person. They show as a chip with their role on the app; × on the chip takes them off. The app's people are listed under the box; type to narrow a long list.
  3. Choose Apply. The names are kept at once.

When you name somebody who only views the app, the window says so: named here, they edit this layer and nothing else.

Naming only adds people, and takes editing from nobody: an Editor of the app already edits every layer whose Editable box is ticked. To let somebody edit one layer only, keep them a Viewer of the app and name them on that layer. To keep a layer's editing from the app's other editors, set its Who edits it to Only chosen editors.

Several people on several layers, or in several apps, at once: ask Buddy Pro in its window — "let Anna and Dan edit the Pipes and Meters layers in Northfield" — and confirm its preview. It follows the same rules as this window. See Who edits which layers.

  • Who can be named: the app's people who do not manage its layers — its viewers and, in a client's app, its editors. The workspace's owners, administrators and editors and the app's administrators edit every layer anyway, and are not listed.
  • A new layer or folder: Save the layers first, then name its editors. Before that, Cartema says Save the layers first, then name the editors.
  • What a named editor may do: draw new features, change and delete features, change their values in the attribute table, add attachments, go back to an earlier version and undo their edits, change several features at once, split them, 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 and clipping, and copying the layer as a new one stay with the app's editors, and changing its look with the app's administrators. See Layers you edit by name.
  • Within the app's own rules: a named editor edits only while the app's Editing in this app is On; with editing off, nobody edits, whatever the names. A named editor who only views the app also needs the layer's Editable box; one who edits the app (a client's editor, an app's editor) does not. They must see the layer (Who sees it) to edit it.
  • Seats: anyone named takes an editor seat of the plan. When none is left, Cartema says The plan has no editor seat left.
  • When people leave: somebody who no longer opens the app — taken off it, out of its client or out of the workspace — is taken off its named editors at once, and stays off if they come back until they are named again.

In Studio → People, a green pencil with a number on a person's app chip counts the layers they edit by name on that app.

Field packs

A field pack gathers an app for work where there is no network: its vector layers as map tiles for the app's starting area and a range of zooms, the imagery you choose to carry, the styles and, unless you untick it, the attribute tables that identify and search read. It is built on Cartema's server from the same tiles the map draws. Cartema for iPhone does not open field packs yet: for now it shows what you have viewed while online (see Cartema for iPhone).

  1. Under Field packs on the app's page, give the pack a Name (the app's name and the day, to begin with) and its zooms, From zoom and To zoom.
  2. Under Imagery to carry, tick the raster layers to take and, beside each, to zoom how close it goes. The line beside Build pack estimates the tiles and the size as you choose: imagery at close zooms weighs the most.
  3. Leave Attribute tables for identify and search ticked to take the layers' attributes along, and choose Build pack.

The pack is built in the background: Queued, Building, then Ready with its size, tiles and parts, or Failed with the reason. Manifest opens the list of its parts, and Delete removes it after asking. The workspace's owners, administrators and editors build and delete packs here. Packs count towards the workspace's storage (Field packs, under Storage by kind), and each pack built or deleted is a line in Studio → Activity, with its app and how many layers it carries.

A pack holds only what its author may take away, as an export does: one made by somebody who only views the app carries only the layers the app lets everyone export (Everyone exports) and says how many were left out, and files of meters stay with the workspace's team (see Exporting a layer).

Publish

Publish marks the app as published: only published apps appear in Cartema for iPhone. On the web, users always see the app as last saved.

History

Every change to an app is kept as a version: who, when and what, by name — the layers it touched (“Layers added: Roads, Rivers”, “Layers switched off: Parcels”, “Definition query changed: Wells”, “Layers moved to another folder: Wells → Block 1”), its folders (“Folders renamed: Imagery → Satellite”, “Folders moved: Block 2”), and the app's settings (“Basemap: Streets → Satellite”, “Start view changed”, “Title: Field map → District map”, “Tools added: Draw”). A folder put elsewhere is said as moved, never as deleted and made again; when two folders or layers share a name, the folder above tells them apart (“Block 1 / Imagery”). The newest 20 versions are listed; Show older versions adds more.

Restore first shows what restoring that version would change in the app as it is now, a line per change under Layers, Folders and App settings, and restores only on Restore v…. It brings back that version's layers and their settings, folders, map (basemaps, start view, zoom limits, coordinate systems) and the app's settings. Styles and data are not changed by restoring.