Request a demo
CULTURAL AND NATURAL HERITAGE · CATALOGUING AND TERRITORIAL DATA

Catalogue. Understand. Decide.

ISORIZE brings records, geometry, metadata and relationships from different disciplines into one catalogue, each with its own schema and its own vocabularies.

  • Cultural heritage
  • Nature and habitats
  • Fauna and species
  • Trails and access
  • Digital documentation

For heritage authorities, museums, local government, protected-area bodies, research institutions and professionals commissioned to catalogue.

a map computed from a survey, not drawn elevations relative to the lowest point in the extract absolute coordinates removed
DISCIPLINARY READINGS

Multi-level, multi-discipline readings of the territorial catalogue.

A structure sits inside a habitat, beside a trail, within a designated area. In ISORIZE each of these relationships is recorded as data, with its own type, the source that attests it, its verification status and an accountable person.

protected site · habitat cultural site · rock-cut colony · fauna trail vegetation on the wall
RECORDED RELATIONSHIP Select a reading: its layer and its relationships with the others are highlighted.
Back to top
THE PLATFORM

Record structure and data life cycle.

The functions described below are in operation; which of them are activated, and with what configuration, is settled with the organisation when the project starts.

TERMINOLOGY

Controlled vocabularies, extensible per domain

Each domain has its own controlled vocabularies. An authorised user adds a term from the administration panel. Superseded terms stay in the vocabulary marked «deprecated», and the records that use them stay readable.

GEOMETRY

Accuracy class and location reliability

Geometry is entered from the record: drawn on the map, typed as coordinates, or deposited as a file. The accuracy class, the acquisition method and, where elevation matters, the vertical reference system stay attached to it. Measurement accuracy and identification reliability remain two distinct fields: a coordinate surveyed to the centimetre may refer to an asset whose identification is still uncertain.

WORKFLOW

States, transitions and server-side permission checks

Draft, registered, published, archived: that is the minimum path. Where the project requires it, review by the scientific lead is added. Permissions are checked on the server at every transition; hiding a control in the interface does not count as a check.

SCOPE

Multi-domain with per-organisation data isolation

Each domain has its own records, vocabularies, permissions and validation rules, and shares with the others the map, the validation path and the change log. One organisation's data is not reachable from another's.

Cultural heritage Nature and habitats Fauna and species Trails and access Digital documentation
The active domains are agreed project by project.
IDENTITY

Invitation-only access, roles per domain, audited operations

There is no self-registration. Accounts begin with an invitation, with roles and domains of competence set by the project, and relevant operations are recorded with author and date. Data belonging to different organisations stays separate, including for administrators.

REVISIONS

Non-destructive record versioning

Every change creates a revision with author, date and content. The register is append-only: no line is ever overwritten. Editing a published record opens a new revision in draft; the published version stays readable and exportable until the new one replaces it.

Interface preview: a catalogue record is assembled field by field — name, condition, accuracy class, location reliability — the point appears on the map and the record's status advances from draft to published.

ISORIZE screen: the header of a catalogue record. Identifier PMM-RU-2026-0101, name “Cappella rurale”, status PUBLISHED version 1, discipline “rock-cut religious architecture”, 100% of 17 required fields completed. ISORIZE screen: the “Identification of the item” section of a record, with the fields for principal name, alternative names, suggested catalogue record type and item typology, each with its own contextual help.
ISORIZE running, on a sample record. The field names — DENOMINAZIONE_PRINCIPALE, TIPO_SCHEDA_ICCD_SUGGERITA, COMPLESSO_DI_APPARTENENZA — are those of the disciplinary schema. Above them, the asset identifier, the review status and the required fields still to be completed.
Back to top
STANDARDS AND INTEROPERABILITY

Metadata, disciplinary schemas, OGC services.

The references below concern how data leaves ISORIZE and is read elsewhere.

  1. origin
  2. acquisition
  3. cataloguing
  4. validation
  5. publication
  6. revision
  7. export and reuse

Every step leaves a trace. Provenance, transformations, responsibilities and conditions of use accompany the data together with its metadata.

Which of these references enter a project, and to what extent, is settled with the organisation: the list describes how the platform is built, not a set of features active for everyone.

  • European territorial data

    reference INSPIRE

    Protected sites, habitats and biotopes, species distribution: for these themes the data and metadata structure is already defined, and ISORIZE adopts it.

  • Geographic metadata

    reference ISO 19115 / 19139

    Title, abstract, keywords, responsible party, reference system, spatial and temporal extent, quality, conditions of use, lineage.

  • Standard mapping services

    reference OGC — WMS, WFS, WMTS

    Layers are published as interoperable services and open in QGIS, ArcGIS, map portals and third-party systems.

  • National territorial-data infrastructures

    reference RNDT

    Metadata is structured for deposit into national and regional infrastructures: by the time of publication the description already exists.

  • Protected sites and territorial constraints

    reference Natura 2000

    Codes, designations and relationships between an element and its protected context are structured fields, queryable like the rest of the record.

  • Habitats and shared classifications

    reference EUNIS

    The habitat classification is recorded together with the source of the determination. Surveys from different campaigns stay comparable.

  • Species observations

    reference Darwin Core / GBIF

    Biological observations adopt the schemas in use for biodiversity-data exchange, with no remapping of fields.

  • Catalogue records for cultural heritage

    reference ICCD

    For cultural heritage the fields keep the names of the cataloguing schema. No internal renaming.

ISORIZE is built to work with shared standards and vocabularies. Which services and which export schemas to activate is defined with the organisation, and verified on the data actually exported.

Back to top
DATA QUALITY

Uncertain data handling.

A real inventory delivers values of differing quality. Each one enters the catalogue with the scale and method by which it was measured, or with the reason the measurement is missing.

STATO_CONSERVAZIONE_GENERALE fair

Measured. A graduated scale and declared vocabulary show both value and method.

STATO_CONSERVAZIONE_GENERALE undetermined

Undetermined. A dashed mark denotes a value never measured, distinct from zero and from a data-entry error.

DATING — as reported by the source “survey campaign 2018-2019”

The source wording remains readable. A normalised form may sit alongside it, used for search.

POINT CLOUDS AND 3D MODELS

Web viewer and anchored annotations.

The cloud or the model opens on the same map as the records. While viewing, you pick the attribute that colours the points: colour acquired by the survey, elevation, classification, height above ground, intensity.

Colour by
drag to rotate · scroll to zoom
3D ANNOTATION · anchored to a point Surface erosion at the base of the wall (sample data) vocabulary · deterioration: erosion
  1. select a point on the model
  2. write the note and choose the term from the vocabulary
  3. the marker remains at its coordinate while the scene rotates
colours captured by the survey

The platform derives from the deposited file a copy suited to online viewing. The original stays untouched. Where the survey carries elevations, the vertical reference system is a required field. Without that reference the cloud sits at the wrong height.

Accepted formats — point clouds: LAZ 1.4 COPC; models: glTF 2.0 / GLB. File requirements are declared and checked on upload.

Back to top
SENSITIVE SITES

Exact coordinate inside, generalised position on the way out.

People working on the project need the exact location. The question is what leaves it — through an export, an application interface, a public map.

  • Inside the platform the coordinate is the real one. People working on the project see it according to their permissions, with a padlock on the marker.
  • Outside, what comes out is an area, not the point. How wide the generalisation is, is a project parameter; whether the rule applies is not.
  • The exception requires a dedicated permission. Every row exported with the precise coordinate goes into the register, with the name of whoever asked for it.
actual coordinate circle on the grid node

Internal view: the actual coordinate, available to authorised users. The padlock on the marker signals that the site is subject to limits on the way out.

YOUR DATA

Independence from the supplier, verified at handover.

Data, metadata, relationships and declared absences come out in open, self-contained formats, readable without ISORIZE and without proprietary software. Generalised geometry carries with it the statement that applies to it.

THE DELIVERY TEST

If the package cannot be read without us, the delivery is not finished.

The check is run on the real export, before the organisation signs off. It is a project acceptance criterion.

DEMONSTRATION

A demonstration on your own material.

We start from material you already have: a spreadsheet, a map layer, archive records, a survey. On a sample chosen together we test the schema, the vocabularies, data quality and the shape of the delivery. Call us and let us talk it through.