For editors and owners
Your data
Studio's data browser — folders, views by app and by city, previews on a map, attribute tables, copying, exporting and filing every dataset.
Studio → Datasets is the workspace's data, organised like the files on a computer: every layer, image and drawing, filed in folders, with views that gather them across the folders. It has three parts:
- on the left, the folders and the views;
- in the middle, the list of what is in the folder or view you chose;
- on the right, what you chose in the list: its map, its details and everything you can do with it.
Drag the line between two parts to make one wider: the folders when names are long, the details for a bigger map. Focused, the line also moves with the arrow keys; a double click gives the part its first width back. Hide details, at the top of the right part, gives the list the room; Show details, at the end of the list's bar, brings it back. This browser remembers the widths and whether the details show.
Private layers are their people's own and are not here; they have their page under Datasets → Private layers.
Folders
New folder makes a folder in the one you are in; folders can hold folders. To file something, drag it — one dataset, or several selected — onto a folder in the tree, onto a folder in the list, or onto a folder's name in the path at the top of the list. Move to… does the same from a menu.
A folder's own menu (its …, or a right-click) has New folder, Rename, Move to… and Delete folder. Deleting a folder deletes no data: what was in it moves up one level.
Data migrated from another system is filed in the folders it had there, until you file it yourself.
Views
Below the folders, the views gather datasets from every folder:
| View | Shows |
|---|---|
| Not in any app | Data no app shows yet |
| Recently changed | Data changed in the last 30 days |
| Imagery and rasters | Orthophotos, satellite images, terrain models |
| Drawings | The drawings people saved in the apps, those you may open; Open in takes you to the drawing in its app |
| By app | Every app, with the data it shows |
| By a field | Where many places share one layer — one table of water pipes for a hundred cities, each app showing its own city — each value of the field the apps filter by (for example By City) with the apps that use it. Choosing one lists every layer that has data for it, with how many features it has there |
The list
Click a column's name to sort by it; click again to reverse. Search all data looks in every folder at once — names, tables, the file or service the data came from, and the apps that use it — and says where each result is filed.
To choose several: tick their boxes, Ctrl / ⌘-click, or click one and Shift-click another for everything between; Ctrl / ⌘ + A chooses all. With several chosen, the bar above the list offers Move to, Add to app and Delete. Delete on the keyboard deletes what is chosen; Enter opens it; the arrow keys walk the list.
A right-click on a row, or its …, opens its menu.
A dataset's details
Choosing a dataset shows it on a map — drawn as the apps draw it, and, in a By field view, only that value's share of it, zoomed to it. Under the map: its kind, number of features, fields, folder, where it came from, its table and the date it last changed; In apps, the apps that show it (the arrow opens one); and, for shared data, Shares by field — each value with its features and apps, a click away from its view.
Size and properties
The Size column shows the storage each dataset takes; a folder's is the total of everything in it and in its folders. Click Size to sort by it — the biggest first — and find what fills the workspace. With several rows chosen, the bar above the list and the panel on the right show their size together (a dataset chosen with its folder is counted once).
Choosing a dataset also shows its Properties:
- the Source file it was loaded from and its Format (GeoTIFF, AutoCAD DWG, GeoPackage…), its Extent, when it was Created and Last changed, and by whom;
- for an image: its Pixels, Bands, Resolution, Coordinate system, Overviews (the reduced copies drawn when zoomed out), whether it is Tiled and a Cloud-optimised GeoTIFF, and its Compression; for a raster collection, its Sheets;
- Storage it takes, in parts: its table in the database (indexes included), its image and model files, the original file kept — shared between the layers when one file became several, as a drawing's lines, areas and text — and its attachments and photos, with the Total.
Sizes are measured every hour, with the workspace's storage, so a dataset just imported shows its size within the hour. A dataset of which you see only part — a shared table your apps show one city of — shows no size. Work that Cartema support did for you is shown as Cartema support.
What you can do
| Action | |
|---|---|
| Open on map | The dataset on a map the size of the window. Double-clicking a row does the same |
| Attribute table | Its features as a table under its map: sort, page through, Zoom to a row, CSV downloads the whole table |
| Fields and settings | The dataset's page: field labels, what is searched and shown, rules |
| Rename | Its name everywhere it is listed |
| Move to… | Into another folder |
| Copy… | A copy that is a dataset of its own, with every attribute and the styles — the whole of it, or, for shared data, Only one value's share (one city's pipes) — filed in the folder you choose |
| Add to app… | Adds it to an app's layer list, at the top, with its default style — the whole of it or Only one value's share. The app keeps a version you can go back to |
| Export… | As GeoPackage, Shapefile, GeoJSON, KML, CSV or DXF, in the coordinate system you choose — the data's own region's systems come first. In a By field view, only that share |
| Contours… | For an elevation model: lines of equal height as a new layer — choose the Interval (m) and an Index contour every so many, drawn thicker and labelled with its height. It is made in the background (Studio → Jobs) |
| Delete… | Removes the data for good, after saying how many apps would stop showing it |
In a By field view, Open on map, Attribute table, Copy and Export start from the value in view.
Import a file at the top brings in new data; see Importing data.
Find content
Studio → Datasets → Find content lists everything of the workspace you may see, by type — so a 3D model, an orthophoto or a plan is found without knowing its folder or its name.
On the left are your apps and their folders, as each app's own tree has them, with how many places each uses what the search keeps; All content is everything, In no app what no app uses, and Filter apps… narrows the list of apps. Pick an app, or a folder of it, and the list on the right shows only what it holds. On a narrow screen the apps open from the Apps button.
Above the list:
- Type: Layers, Orthophotos and images, Terrain (DTM/DSM), 3D models, CAD drawings, Plans (what an app files under תכניות), Drawings (under תרשימים) and Files on features (photos and documents attached to a layer's features, counted per layer). Choose one or several; each says how many there are.
- Three shortcuts: Not used anywhere, Over 1 GB and Added this week.
- Name, app or folder, Added (the last day, 7 days, 30 days or year), Added by (Me, or a person), Size, and the order: Newest first, Oldest first, Largest first or By name.
With All content each row is one item, with where it is used (an app, or how many), its size and when it was added. With an app picked each row is one place the item is used in that app: its folder (or, for a 3D model, its place in the 3D panel), the switch for On at open, Open in the map, Locate and Remove from app, as far as you may change that app.
Click a row for its details: its day (a 3D model's survey day, an image's day in its name), when it was added, its size, who added it, and where it is used — each app, the folders above it there or its place in the 3D panel, and whether it is on when the app opens. Beside each place:
- Open in the map opens the app in a new tab on it: a layer shown in the list, switched on and framed; a 3D model in 3D.
- Locate opens the app's page in Studio on it: the layer in the app's list, or the model's row in 3D models.
- For a 3D model: Move up, Move down, Move to the top, and Sort the 3D panel by date (newest on top, models without a date last); On at open / Off at open.
- For a layer: On at open / Off at open, and Remove from app — its data stays in the workspace, and the app's history keeps the version before.
- Open its data, and the dataset's own Delete where it is yours to remove (as in its menu above).
Several at once
Each row has a checkbox: space ticks the row you are on, shift with the arrows or a click ticks a range, Ctrl+A (⌘A on a Mac) ticks every row, Esc clears. The row above the list ticks all the open folder or search holds; once something is ticked it shows how many, with what can be done to them all:
- On at open / Off at open and Remove from app — with an app picked, as they change where an item is used. Remove asks once, naming how many; the data stays in the workspace, and the app's history keeps the version before, so one restore takes the whole batch back.
- Open its data, for one item.
- Delete, which asks once, naming how many and in how many apps they are used; it cannot be undone.
- Ask Buddy about these, which opens Buddy with the items named in his box, for you to finish the question.
What you may never do here is not shown. What some of the ticked items do not allow is greyed, with the reason beside it. At most 500 items at a time. Every item is asked again with your rights, as the same action on its own asks them: whatever is not yours to change is not changed, and is named after the rest is done. Ticks clear when the search or the folder changes.
The same finder, for one app, is Find content at the top of the app's page in Studio. It lists only what you may see — the apps you open, the data within your reach (a table other customers share shows no size), the names of who added something as the Jobs page would show them — and every action asks your rights again, as the same action does in Studio. A 3D model added to an app goes into its 3D panel by its date, newest on top; see Your apps.
Buddy points at the finder when you ask "where is my 3D model?"; Buddy Pro moves one for you: "put the 3D model I uploaded yesterday to Cedar Valley at the top" (see Buddy Pro).
Fields only the team sees
On a dataset's page (Fields and settings), each field has a Shown to choice: Everyone, or Workspace team only. A field for the workspace team only — an internal code, a cost, a note for the office — is never shown to the people of the workspace's clients: not when they click a feature, nor in the attribute table, exports, prints, search, labels, styles, the legend or a feature's history. The workspace's own people see it as before. A field whose name looks internal is marked Looks internal: consider team only. Unless your workspace has asked Cartema support for every field to be shown to everyone, when a new layer arrives, columns that look like people's personal data (names, ID numbers, phones, e-mails, dates of birth and the like) start as Workspace team only; open any your clients need here. In a workspace that has asked for that, nothing becomes team only by itself except a column that looks like a password or another secret, and the rest of this paragraph does not apply: new columns arrive shown to everyone, and a field you set to Workspace team only here stays so. The same goes for a column that new data adds to a layer, and for a personal layer when it becomes the workspace's. Loading new data never changes what is already set for a field, and a team-only column that leaves a layer stays team-only if it comes back. While one is away, in the load it left in or any later one, the new columns of a load start as team only, in case one of them is the same column renamed. A field open to everyone whose label in the new data now reads like personal data (a Notes column now labelled as a phone) becomes team only too; the label you set stays. A level follows the label: when new data gives a column the label a team-only column had (data whose columns are numbered slots can move a meaning from one slot to another), that column becomes team only, and a label that leaves a team-only column is remembered, so a column that takes it in a later load becomes team only then. Columns are also recognised by what they hold: Cartema counts, without keeping any value, how many values of a new column look like phone numbers, e-mail addresses or ID numbers, in the first 1,000 rows of the first 200 columns, and the import's log says when a layer has more.
Fields are shown to everyone until you choose otherwise. A new layer clipped from it keeps each field's choice. A field a style of the layer draws by — its classes or its labels — is marked when you make it team only: the client's people then see the layer without those labels and classes, and cannot change its style. Studio's style editor says the same when a label or a class uses a team-only field. See Clients for who belongs to the team and who to a client.