Post processing from raw mission data to a measurable dataset

On almost every mobile mapping system, what happens after the survey determines the quality of the end result. GEORIZON takes that step over from your raw mission data: trajectory, point cloud and imagery in a single automated run, sensor independent and typically within 24 hours. If you have already computed the trajectory yourself, we take it over unchanged.

  • Trajectory post-processing by 360GEO, or processing based on your own SBET
  • Point cloud, imagery and trajectory in a single automated run, typically within 24 hours
  • Sensor independent: the same route for Trimble, Leica, Topcon, RIEGL and other platforms
  • Results immediately available in the viewer, API, WMTS and download
From raw data to actionable geospatial information

From raw GNSS and IMU observations to a measurable dataset

The trajectory describes the position and orientation of the mapping system at every instant of the mission, which makes it decisive for where every point and every image ends up. GEORIZON performs that computation: we combine the raw IMU and GNSS observations with base station data or a correction service, solve the trajectory and assess the result against the estimated accuracy per section, so you can see where the solution is weak and where it is not. The trajectory is then linked to the scan observations and camera frames through their timestamps and the dataset is built: thinning on point density, filtering out noise and passing traffic, colourisation from the imagery, structuring into tiles, and stitching the camera frames into measurable panoramas along the driven line. For platforms running on Applanix POSPac we compute a Smoothed Best Estimate of Trajectory as part of this, with a choice of Single Base, SmartBase or PP-RTX without a base station of your own.

Next Generation Geospatial Infrastructure

One processing chain for systems from different manufacturers

Anyone running more than one platform knows the problem: each make has its own processing environment and its own publication route, while the trajectory step is shared. GEORIZON connects at that common point and takes over from the raw observations onwards. Whether the mission was driven with a Trimble MX, a Leica Pegasus, a Topcon IP-S3 or a RIEGL system, the route to viewer, API and download is identical. That saves licences and workstations, and it also makes datasets from different years and different systems comparable, because they end up in the same frame and the same environment. Where you prefer to keep computing the trajectory yourself, for instance because survey accountability sits with your organisation, we work from your own SBET.

Beyond WMTS: viewer, API and download

Publish straight to viewer, API, WMTS and download

Once processing is complete, the dataset is waiting in your own GEORIZON tenant. Colleagues, clients and partners open the point cloud and imagery in the browser without an installation or a licence per user, measure distances and heights, and share a location through a direct link. To use the data in your own environment, connect to the open API, add a WMTS layer in QGIS or ArcGIS, or download the point cloud in common formats such as LAZ or E57. Faces and number plates are automatically blurred in line with the GDPR, single sign-on and an on-premises deployment are supported, and AI detection and vectorisation can optionally be applied to extract objects from the dataset. Organisations including ProRail (SpoorInBeeld), the municipality of Nijmegen and Kempkes Landmeten work with their geodata this way.

Test GEORIZON with your own mission data

See what GEORIZON does with your own dataset. Bring every kind of geospatial data together in the cloud, always within reach. Request a demo account and take your projects a step further.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.