Obliquo
For public administration, territory and smart cities

Publish urban 3D models and territorial data without building your own infrastructure.

Turn CityGML, 3D Tiles, GIS, LiDAR, orthophotos, meshes, BIM and urban data into shareable web viewers with permissions, APIs and integration with your systems.

From isolated technical deliverables and portals to a living web layer for digital territory.

We review your urban data, formats, users, permissions and integrations to define a viable workflow.

Urban data

CityGML · 3D Tiles · GIS · LiDAR · Orthophotos · BIM · Meshes

Obliquo

  • City
  • Cloud
  • Certify
  • Reality

Digital territory

  • Web viewer
  • APIs
  • Controlled access
  • Digital twin
  • Traceability

The problem

The problem is not having urban data. It is getting it used.

Public bodies accumulate high-value data: orthophotos, GIS layers, 3D models, cadastre, BIM, LiDAR, inventories, meshes and project deliverables. But if each dataset lives in a different portal, folder or vendor, digital territory does not scale.

Scattered urban data

GIS, orthophotos, 3D models, cadastre, BIM and technical deliverables spread across systems and vendors.

Isolated portals

Every project ends with its own viewer, delivery or portal that is hard to maintain and reuse.

Low reuse

Data is created for one contract but is not always ready for future projects, analysis or digital twins.

Limited governance and traceability

It is hard to know which version is current, who has access, what was updated and what can be reused.

Before and after

From isolated urban deliverables to an interoperable territorial layer.

Before

With Obliquo

Urban models in files or one-off viewers

Urban 3D models published on the web

GIS, BIM, LiDAR and orthophotos kept separate

2D/3D data connected in one layer

Custom portals per project

Reusable viewers for multiple projects

Data hard to reuse across departments

APIs and integration with existing systems

Manual access and permissions

Controlled access by role or department

Versions with unclear traceability

Traceable versions and deliveries when needed

How it works

A web layer for digital territory.

Obliquo turns urban and geospatial data into reusable web assets for administration, citizens, technical teams, integrators and partner companies.

01

Connect or publish your data

CityGML, 3D Tiles, GIS, orthophotos, LiDAR, point clouds, BIM/IFC, meshes, DSM/DTM, 360 or urban models.

02

Organise, govern and distribute

Obliquo structures datasets, permissions, projects, layers and APIs so data can be shared and maintained.

03

Activate urban use cases

Publish web viewers, integrate data into portals, feed digital twins or share information with departments, vendors and authorised users.

When the integrity of a version or delivery matters, Obliquo Certify can add fingerprints, manifests and verifiable traceability.

Urban data

Built for real city and territory data.

Urban 3D models

CityGML, 3D Tiles, LOD1/LOD2, meshes and data prepared for viewers or digital twins.

GIS and territorial layers

Parcels, networks, mobility, green areas, facilities, risks, planning and sector layers.

LiDAR and point clouds

Aerial, terrestrial or mobile captures for inventory, inspection, updates and analysis.

Orthophotos and raster

Orthomosaics, georeferenced imagery, DSM/DTM, elevation models and territorial context.

BIM / IFC

Public buildings, infrastructure, facilities and projects connected to the urban environment.

360 and reality capture

Walkthroughs, inspections and visual documentation for remote review or asset updates.

Use cases

Where a 3D city stops being a demo and starts operating.

Urban digital twin

Build a 2D/3D base for planning, analysis, simulation, publishing and evolution of the digital city.

Urban planning

Publish urban models, territorial layers, regulations, projects and 3D context for technical review and coordination.

Mobility and infrastructure

Connect networks, corridors, assets, orthophotos and 3D models for territorial analysis and cross-department coordination.

Environment and risk

Integrate elevation, vegetation, water, sensitive zones, 3D models and GIS layers for analysis and communication.

Citizen-facing publication

Share public or private web viewers to make territory and urban projects easier to understand.

Procurement and deliverables

Turn vendor technical deliverables into reusable, governed and traceable assets within the administration.

Value for the administration

Fewer isolated portals. More reuse of urban data.

Common territorial base

Technical teams, vendors and integrators can work from a shared layer.

Less dependence on one-off projects

Data does not die when a contract closes. It stays ready for reuse.

Web publishing without own infrastructure

3D models, GIS, orthophotos and territorial data accessible from the browser.

Interoperability

APIs, geospatial formats and workflows compatible with existing systems.

Governance and permissions

Control over who accesses, what they see and what data is published.

Basis for traceability

Versions, deliveries and updates can be certified when the case requires it.

Products

City, Cloud, Certify and Reality for digital territory.

Obliquo City

Urban 3D models, City Data Packs and territorial data ready for analysis, publishing and digital twins.

Request City Data Pack

Obliquo Cloud

Publish, govern and distribute 2D/3D data with permissions, APIs, catalogue and web access.

Explore Cloud

Obliquo Certify

Add fingerprints, manifests and verifiable traceability to deliveries, versions or critical datasets.

Evaluate Certify

Obliquo Reality

Turn LiDAR, SLAM, 360 and territory captures into navigable web deliverables.

See Reality

Assessment

Assess your city, territory or urban model.

We review with you what urban data you have, which formats you use, which departments need access and how to publish a first interoperable web layer without building infrastructure from scratch.

Includes

  • Initial dataset inventory
  • Format and service review
  • Users and access profiles
  • Priority use cases
  • Required integrations
  • Product recommendation
  • Pilot workflow
  • Traceability or certification opportunities

No commitment. The best demo starts from your real data and institutional workflow.

Comparison

One-off portal vs reusable territorial layer.

One-off portal

  • Solves one specific contract.
  • Hard to maintain.
  • Data separated by vendor.
  • Limited integration.
  • Poor scale across departments.
  • Data is rarely reused.

Obliquo layer

  • Serves multiple projects.
  • Reusable web publishing.
  • Data organised by territory, layer or project.
  • APIs and integration with existing systems.
  • Scales across departments, vendors and use cases.
  • Data becomes an urban asset.

FAQ

Frequently asked questions

Municipal GIS, urban models, digital twins, permissions, integration and vendor data.

Does Obliquo replace our municipal GIS?

Not necessarily. Obliquo can act as a 2D/3D web layer to publish, share and govern urban data, integrating with existing GIS systems.

Can we publish urban 3D models?

Yes. Obliquo works with urban models, CityGML, 3D Tiles, meshes, LOD1/LOD2 and other 3D assets depending on the project workflow.

Is it suitable for digital twins?

Yes. Obliquo can act as a publishing, viewing and data governance layer to support or complement digital twin initiatives.

Can we control which departments or users access data?

Yes. The platform supports permissions, private spaces and controlled access by profile or project.

Can it integrate with existing portals or systems?

Yes. Obliquo is designed to integrate via APIs, geospatial formats and workflows compatible with existing stacks.

What about vendor data?

Obliquo helps turn vendor technical deliverables into reusable, governed assets ready for new uses.

When does Obliquo Certify apply?

When a delivery, version or urban dataset needs traceability, integrity or verifiable evidence.

What do we need to get started?

An initial inventory or sample: GIS, CityGML, 3D Tiles, orthophoto, LiDAR, BIM or urban model. From there we define the first pilot.