Glossary

The words on this page are the product's own. Where this site and the product disagree, the product is right and this page is a bug.

Organisation

The tenant: the survey firm that holds an account on GISweaver. Not "company" — organisation is the word every screen uses, from "Create your organisation" at sign-up to the Console's own group heading.

Cell

A complete, self-contained regional deployment of GISweaver, bound to that region's data-residency and compliance rules. The first cell is India (in-mumbai-1).

Release

One processed version of a survey inside a project. A release is draft, then published, and may later be superseded.

Published release

The immutable thing you read on the map. Publishing a release fixes it: it is not edited afterwards, and a correction is issued as another release.

Delivery

Not the published release. A delivery is the hand-off of a published release to another organisation — a survey firm handing files to its client — with three properties that define it:

• a period it stays open for, chosen by the sender (90, 180, 365 or 730 days; 365 by default, 730 the maximum);
• a receipt, written when the recipient has taken every file;
• the ability for the recipient to clone it into their own account, where their plan allows it — a copy that becomes theirs, rather than a link to somebody else's.

The Console's Deliveries section has Received and Sent tabs — the same boundary, seen from each side.

Share

Giving another organisation access to a release inside GISweaver, with per-tool grants. Different from a delivery: a share is access to something that stays yours, a delivery is a hand-off. The receiving organisation sees shares under Shared with you.

Saved work

Your organisation's own measurements, marks and objects, drawn over the published release. It is a separate layer: it does not alter the release, and the release does not alter it.

Workspace

The survey surface: the map, and its eight rail sections — Survey, Find, Coordinates, Objects, Analyse, Design, Review, Export.

Console

Your organisation's business-management surface, on different routes in the same signed-in shell: Projects, Shared with you, Deliveries, Clients, Team, Branches, Settings, Billing, Preferences and Help.

Control Plane

The internal Alonstech staff console, on its own hostname. Not a customer surface and not part of the customer application.

Team

The people in your organisation, and what each of them may do. The Console section is called Team; "roster" is not a word the product uses.

Clients

The directory of the clients your work is done for. The Console section is called Clients.

Preferences

Your own settings — units, the converter, your profile, and the Security tab that holds your second factor, your recovery codes and your signed-in devices. Yours rather than the organisation's, which is why it is not under Settings.

Base map

Optional map ground the viewer can draw a survey over. It is not carried inside the product build, and none is switched on by default — a person chooses one, and until they do the map shows Survey layers only.

Build version

One SemVer for the whole stack, compiled into every image of a release. It is shown on both signed-in surfaces — in the Workspace's account menu and at the foot of the Console's rail — and it is the first thing support will ask you for.