What Is a 3D Data Repository?

A category that's showing up more often in construction and infrastructure software conversations, and often gets confused with a plain viewer.

What is a 3D data repository?

The term describes a category, not one specific product — the shared trait is scope. A 3D data repository typically covers point cloud scans captured by laser scanners, drones, or 360° cameras, BIM models, and the documents and imagery tied to a site or project, kept in one place instead of split across specialist tools.

That matters because site data does not arrive in one format. A single project might generate a laser scan one week, a BIM update the next, and a stack of 360° walkthroughs in between. The value sits in seeing them together, not in maintaining three separate logins for three separate tools.

Picture a mid-size contractor running four active sites. Site A generates a laser scan every two weeks. Site B has a BIM model updated whenever a change order lands. Site C has a stack of 360° walkthroughs from a site engineer's phone. Without a shared home for that data, each format lives with whoever captured it — and anyone trying to answer a question about the project ends up asking three different people for three different files.

How is it different from a point cloud viewer?

A point cloud viewer opens one kind of file — a scan — and shows it well. That is useful on its own, but it usually stops there: no BIM model to compare against, no document trail, no way to line up two scans from different dates in the same view.

A 3D data repository includes viewing as one capability among several. The point cloud is still there and still viewable, but it sits next to the BIM model it is meant to be checked against, alongside the annotations and issues raised while someone was looking at it.

Put another way: a viewer answers "what does this scan look like." A repository answers "what does this scan look like, what did it look like six weeks ago, does it match the model, and who flagged the crack in the third bay." The viewer is one component of that second answer, not the whole of it.

How is it different from a document management system, like a shared drive or Procore?

A document management system is built around files — PDFs, spreadsheets, photos — organised in folders with permissions and version history. It does that job well, and most projects already have one running.

A 3D data repository is built around spatial data specifically. A point cloud or BIM model is not just a file to store; it is something you open, measure, and compare inside the platform itself. A document system can hold a copy of a scan file. It generally cannot let you overlay that scan against a BIM model and measure the gap between them.

There is also a practical difference in who can use the data once it is stored. A shared drive assumes the person opening the file already has software that understands it — a scan sitting in a folder is still unusable to someone without a point cloud viewer installed. A 3D data repository removes that assumption: the data is viewable the moment the link opens, in whatever browser the recipient already has.

What file types does a 3D data repository typically handle?

The core formats are point clouds and BIM models, since those are the two data types a construction or infrastructure site produces that general-purpose tools handle worst. Point cloud formats commonly supported include LAS, LAZ, E57, and PCD. BIM formats commonly supported include IFC and RVT.

Beyond those two, 360° imagery and project documents round out the picture — the same repository holding the scan and the model can also hold the photo walkthrough and the report that references both.

Format breadth matters because a project rarely settles on one capture method for its whole life. A site might start with a terrestrial laser scanner producing E57 files, bring in drone photogrammetry for a later phase, and finish with an as-built check against a BIM model exported as IFC. A repository that only reads one of those formats forces the team back into the fragmented workflow it was meant to fix.

Why do construction and infrastructure teams need one?

Because the alternative is reconstructing context by hand every time someone asks a question. "Does the built column line up with the model" or "what did this corridor look like in March" should not require opening three applications and comparing screenshots between them.

Teams handling scan-to-BIM verification, progress documentation, or dispute records feel this most directly — the data already exists, scattered across tools, and the real cost is time spent hunting for it rather than time spent using it.

Take scan-to-BIM verification as a concrete example. Someone needs to check whether a completed structural bay matches the approved model. Without a shared repository, that means finding the right scan file, finding the right BIM export, opening each in separate software, and comparing them across two monitors by eye. With one, the two are already loaded against each other, and the answer is a measurement, not a guess.

What should I look for when choosing one?

A few criteria apply regardless of vendor: how many file formats it actually reads natively, whether it runs in a browser or requires a desktop install, whether it supports comparing the same site across two points in time, and whether someone outside your organisation can open a shared link without creating an account first.

Worth checking too: how issues or annotations get tracked once someone has spotted something in the data, and whether the tool treats point clouds and BIM models as first-class citizens or bolts one of them on as an afterthought.

It also helps to ask how the tool handles the recipient side of sharing, not just the person doing the capturing. A repository that requires every viewer to hold a paid seat just to look at a scan reintroduces the original problem — someone outside your organisation, without a licence, locked out again.

How does SpatialSense fit this category?

SpatialSense is a browser-native 3D data repository built by Kodifly Limited for construction and infrastructure teams. It unifies point clouds (LAS, LAZ, E57, PCD), BIM models (IFC, RVT), 360° imagery, and documents in one platform, with cross-timestamp comparison, in-browser measurement, annotations, and issue tracking built in — nothing to install for anyone opening a shared link.

It also includes document search within projects and a free companion capture app, Trace, so a 360° site walkthrough becomes a GPS-tagged, timestamped record in the same repository — not a separate folder of photos to cross-reference by hand.