For engineering and design firms
Put your standards into the catalogue. Crews record field data against them.
What changes
Feature types and fields you define
A catalogue holds your points, lines and polygons in categories, each with its own symbol, colours and line style. Each carries the fields you place on it: text with an entry mask or pattern, numbers measured as a length, an area or a count, dates, yes/no and pick lists. A field is required or optional, can carry a default, and can be locked so the crew cannot change it.
Catalog StudioConnections recorded, not guessed
Connection rules say which lines may end on which points and which points may be attached to which. A line records the feature it connects to at each end, so a connection is a fact in the data, not two coordinates that happen to touch. A connection the rules forbid cannot be made.
Catalog StudioChecks at the severity you choose
Quality rules flag required fields left empty, lines left unconnected, stacked points, near misses within a distance you set, overlapping polygons and polygons whose border crosses itself, each as a warning or an error. At the strictest setting a line left unconnected or of zero length, or a polygon crossing itself, is not recorded at all, and the crew sees the explanation you wrote.
Quality & automationChange the standard once
Projects use their catalogue live, so a change made in Catalog Studio reaches every linked project at once. A project that needs its own version can be detached: it gets a copy of the catalogue as it stands, and takes later changes only through a reviewed sync.
Catalog Studio
Questions
The parts of the product this uses
See it against your own build
A demo runs on your data shape: your tools, your attributes, one of your projects. Thirty minutes, no slide deck.