For editors and owners
Raster collections
Many orthophotos as one layer — every flight and every sheet over the years — with a date to choose in the layer list instead of a layer for each image.
An area flown many times over the years soon holds hundreds or thousands of images: each flight is cut into sheets, and each sheet would otherwise be a layer of its own. A raster collection puts them all in one layer. The map draws only the sheets in view, with the newest flight on top where flights overlap, and the layer list offers the date (or the year) to show, in place of a switch for every image.
In the map
Switch the collection's layer on in Layers. A collection is the ground of the map: it is always drawn under the app's other layers, wherever it stands in the list, and a 3D model stands on it. Under its name:
- Imagery of — one flight's date, the newest when the app opens, or one year when the collection is grouped by year. Each date says how many sheets it holds.
- 3D and triio — beside the date when the app has a 3D model flown the same day over the same place: 3D shows it on the map, triio opens it in triio.
Click the map over the imagery to see which sheet and flight lie there, with the date flown and the older dates under it.
When the map is zoomed far out, a collection draws only its sheets' outlines and says Zoom in to see the imagery: a view that would put together hundreds of sheets at once is left to the outlines until you come closer.
Making a collection
Import the orthophotos as usual (Studio → Datasets → Import); each becomes a raster. A sheet's plain white or black border is made see-through, so sheets side by side never hide each other. Then, in Studio → Datasets:
- Select the rasters — for example everything in the Imagery view or in a folder.
- Right-click, or use the bar above the list, and choose Add to a raster collection….
- Choose A new collection and give it a name, or An existing collection.
- Choose the Date of each raster: From each raster's name (2024-05-12, 2024_05_12 or 20240512 in the name) or The same date for all. A raster without a date in its name stops the whole step and is named, so nothing is added half-way.
- Optionally name the flight, then Add.
The same rasters added again change nothing, so the step can be repeated safely when a flight arrives in parts.
A collection holds one client's imagery: rasters shown in apps of different clients cannot go into the same collection, and a raster cannot join a collection that is already in an app which may not show it. A raster no app shows yet belongs to no client: to add it to a collection that is in a client's app, place the raster in one of that client's apps first. Make one collection per client.
The collection's page
Studio → Datasets, then the collection's Settings, shows:
- How the layer shows it — whether the layer offers each flight's date or each year; which flight lies on top where they overlap (the newest or the oldest); and from which zoom the imagery is drawn (Imagery from zoom) — worked out from the sheets' size unless you set it. The layer shows one date (or year) at a time, and opens on the newest.
- Dates — every flight's date and how many sheets it holds.
- Rasters — the collection's sheets, newest first. Tick some and Remove from the collection to take them out; their files stay.
- Use in place of the rasters — in every app you may change that shows all of these rasters one by one, the collection takes their place: the first of them becomes the collection, the others leave the tree, and folders left empty go too. Apps that show only some of them are left as they were and named. Each app changed gets a new version, so Versions can put the previous one back.
To add the collection to an app by hand, add it like any dataset (Add to app…, or the app's layer editor).
Limits
- A collection holds up to 5,000 rasters by default. For more, split them — by area or by period.
- An app shows up to 100 raster collections.
- One tile of the map puts together at most 12 sheets; where more meet, the map shows the outlines until you zoom in.
Larger limits for a workspace can be arranged with Cartema support.
Good to know
- The rasters a collection reads are kept while it uses them: deleting one of those rasters' own datasets leaves its image in the collection.
- Field packs for the iPhone do not take raster collections yet; take the single rasters you need instead.
- For very large deliveries (many hundreds of gigabytes), Cartema support can build the collection for you directly from the converted files.