ISORIZE brings the heritage of a territory into a single catalogue — cultural sites, habitats, species, trails — as structured records: controlled vocabularies, metadata that follows the European standards, and every entry's position together with the accuracy it was actually measured to, including when that accuracy is low and someone needs to say so. Built for heritage authorities, local government, protected-area bodies and research institutions.
A Lascott product. Your data stays yours, in open formats.
point_cloud › a real survey · 191,664 points in the viewer
ISORIZE is not a GIS. It is a system of structured records with geometry attached, and with the metadata that makes them findable and reusable outside it: fill in, review, publish, share.
Not five separate archives: the same scene read by the cultural, natural, faunal, trail and conservation domains — with the relations between readings recorded as data, with type and verification.
The relations between readings are recorded data, not a remark in a free-text field. Whoever catalogues only the heritage site cannot see that restoration has a seasonal window; whoever catalogues only the fauna does not know that the cavity is a protected site.
Anyone who has catalogued the heritage of a territory has already tried all three. A spreadsheet accepts anything and remembers nothing. A GIS draws beautifully but has no record form. A records system has the form but not the territory. And none of the three holds a rock-cut church, a priority habitat and a species observation together — even though they sit on the same hillside. ISORIZE begins where all four meet.
Cultural sites, habitats, species, trails: different domains, with different fields and vocabularies, inside the same system. People working on nature don't have to bend an archaeological form, and people working on archaeology don't have to wait for someone to build a second system. The links between the two worlds — a site inside a protected area, a habitat crossed by a trail — stay recordable because they live in the same place.
Geometry is added from inside the record: a point on the map, coordinates typed by hand, or a file you already have. The person who knows the site enters it themselves, without going through the person who knows the software.
In a real survey the exact date is often missing, a position is sometimes approximate, and some fields simply aren't known. A rigid system rejects them, and what gets rejected ends up in a side file nobody finds again. ISORIZE takes them in as declared: how accurate the measurement is, how confident we are about the identification, and why something is missing.
An organisation receives map layers from studies, consultants and campaigns spread over years. Boundaries self-intersect, polygons come out malformed, features fall outside the working area. ISORIZE checks this as the data comes in and says why a geometry is invalid, instead of swallowing it and passing the error on to someone else two years later. It is the mirror image of the section below, and the two belong together: the uncertain is accepted by declaring it, the broken is recognised and flagged.
Fields carry the names the standards use, vocabularies are controlled from the first entry, and every dataset carries the metadata INSPIRE and ISO 19115/19139 ask for — including lineage: where it came from and what was done to it. There is no final conversion to prepare, and therefore no point at which things get translated and go wrong.
You can see who wrote what, and when. Revisions are never overwritten, and a published version stays readable and exportable while a new one is being prepared. When someone asks, the answer doesn't have to be reconstructed from memory.
Everything below already exists. No roadmap promises.
Interface preview: a catalogue record fills in field by field — name, condition on a graduated scale, accuracy class, reliability of the location — the point appears on the map and the record's state moves from draft to recorded to published.
Fields carry the names the standards use — cataloguing terms for cultural heritage, Natura 2000 and EUNIS terms for habitats and protected sites — with no convenient renaming. Each domain has its own controlled vocabularies, and an authorised user can extend one from the back office when a term is missing: no software change, and terms are never deleted, only deprecated.
Draw on the map, type coordinates by hand in either system with live conversion, or import a file. Every geometry carries the accuracy class it was obtained with and, where there is an elevation, the vertical datum that makes it readable.
Records move through states, and whoever moves them has to be allowed to: the check happens on the server, not in how the buttons look. The review path is chosen per domain — a short one, or one that goes through the scientific lead.
A thematic domain is a module: its own records, vocabularies, permissions and validation rules, switched on only if needed. A protected-area body turns on nature, habitats and trails; a heritage authority turns on cultural sites; whoever needs both keeps them in one catalogue. Each project has its own configuration, and one organisation's data is unreachable from another's.
No self-registration: accounts start from an invitation, with role and domains already decided. Multi-factor authentication for everyone, permissions checked on the server, and backups are tested by actually restoring them.
Every change adds a line; nothing is ever removed. No catalogue record is destroyed, and data already delivered can still be reproduced years later.
These aren't acronyms for the bottom of a tender document. They're why your data can talk to everyone else's — today, and in ten years.
The European directive that makes spatial data comparable across administrations. The themes that concern you are all there: protected sites, habitats and biotopes, species distribution, bio-geographical regions.
Every dataset carries its own identity card: title, abstract, keywords, custodian, reference system, spatial and temporal extent, quality, use conditions, and lineage — where it came from and what was done to it. It is what separates reusable data from a file.
Your layers can be consumed where you already work: QGIS, ArcGIS, a mapping portal, another organisation's system. Standard services, not a format to convert every time.
Metadata is already in the shape Italy's national spatial data catalogue expects. Publishing to the national node isn't a job to start over.
Site code, designation type, and the relationship between the catalogued element and the site: proper fields, not remarks in a notes box. Anyone reporting on a network site finds the data already in shape.
Habitats are named with the European classification — the same one the European Environment Agency and monitoring reports use. A habitat called by its proper name is a habitat you can compare.
The vocabulary the world uses to exchange biodiversity data. An observation recorded this way can be published and cited without remapping anything, and your surveyors' work leaves the drawer.
For cultural heritage, fields follow the structure of the catalogue records, keeping their names with no convenient renaming: that is what makes the data readable to the people who read those records for a living.
ISORIZE is built on these standards. Which services and exports to switch on is agreed project by project.
“You can't always get precise data. In fact, almost never.” Anyone who has run a field survey knows this.
A date the source gives as a season or a decade isn't forced into a calendar: it is recorded the way the source says it, and that transcription remains the authoritative one. A value nobody measured is declared unmeasured — and it looks different from a low value. Accuracy, where there is any, is written next to the data instead of assumed. This isn't permissiveness: it's the difference between a catalogue you can re-read and one that turned away half the work of the people who were actually there.
Measured. The graduated scale says how much; the vocabulary label says what.
Declared unknown. The dashed marks say “not measured”: it is not zero, it is not an error, and the record doesn't look broken.
Transcribed. The source stays authoritative. A normalised form can sit alongside it for searching — it never replaces it.
Point clouds open in the browser, with nothing to install, on the same map as the records: one at a time from the record it belongs to, or several together to understand how an area is built and how its parts hold together. Each cloud can be coloured by whichever attribute matters to whoever is looking — survey colour, elevation, height above ground, classification, intensity, return number — because an archaeologist and a forester are not looking for the same thing in the same file. 3D models open next to their record; if they are georeferenced, they sit on the map in their proper place, and they can be annotated: a click anchors a note to a precise point on the model, with a vocabulary term to name it.
Whoever uploads simply deposits the file: the web-readable copy is prepared by the platform, and the original is never rewritten. If the survey carries elevations, the platform asks which vertical datum it uses — satellite heights and national mapping heights differ by tens of metres, and a file that doesn't declare it lands at the wrong height.
Point clouds are accepted as LAZ 1.4 / COPC, models as glTF 2.0 / GLB. File requirements are written down, and checked on upload.
A vulnerable site is protected where the data leaves the platform — not by hiding it from the people working on it.
Internal view: the true coordinates, with the padlock marking the site as sensitive.
ISORIZE is adopted per project, and can be left behind. What was entered comes out in open, self-contained formats — a file that carries its own meaning, not a dump that needs our software to be read — and with its metadata, because data without its own identity card is data nobody will be able to read in five years. Declared absences come out as absences, and never turn into invented positions. No choice we made creates a dependency on us for reaching what is yours.
The delivery package opens in QGIS. Without ArcGIS, without ISORIZE, without support.
It is a product acceptance criterion, not a slogan: every delivery is checked this way.
ISORIZE is adopted per project: we start from what you already have — a survey in a spreadsheet, a map layer, records on paper — and prepare a demonstration on it. A handful of records is enough to tell whether the approach convinces you. Give us a call and let's talk.
Thank you. We've passed your request to the right person and sent you a confirmation by email. If you can't find it, check your spam folder.