Working with spatial data (geo location)
Since v.4.5
Introduction
Objects have the capability to store optional location coordinates, which can be provided during import and subsequently utilized in a variety of scenarios such as display on a map, proximity search, or point cloud navigation.
The system offers a translation mechanism that enables the provision of coordinates in any valid spatial reference system. Subsequently, the data can be retrieved in either the same reference system or any other specified system.
To locate the appropriate EPSG number, you can utilize the https://spatialreference.org website.
Data Import
Supported formats
Import of location data (point) is supported in the following formats:
Import format | is supported |
---|---|
IFC | No (planned) |
XLS (Objectdata) | Yes |
XLS (Document) | No |
Fi2 | No (planned) |
HDRep | No |
Docnavet | No |
Import domain (EID)
Below is a simple example of a domain that will be used to import coordinates from an Excel file.Â
We have added external columns that contain location data (X, Y, Z).Â
These coordinates must be mapped in Coordinates section for every object class. In this case the name of the coordinates match, but it could be any name in the source package.
Import profile
It's important to provide correct SRID (Spatial Reference System ID) during the import, if coordinates are imported.Â
It must be a correct reference system that the data is represented in. It is not relevant for later use (e.g. when we need coordinates in another system, like WGS84) but its critical for proper registration of coordinates.Â
Sample data package
This is a simple data package for import via Excel. Please note the class name (1), columns with coordinates (2) and a GUID/ID field for matching of objects (3).
System settings
The only system setting for this functionality is the default SRID that can be set in main section:
Accessing Data
Data is access by the system in various scenarios, but can also be accessed via system data API.
api/object/json/108/608128?location=true&srId=4326
api/perspective/metadata/json/11?childClassId=108&offset=0&limit=30&location=true&srId=4326
Two query parameters can be used to control location data returned:
parameter | values |
---|---|
location | true/false |
srId | SRID (Spatial Reference System ID) Supported values: https://spatialreference.org |
Example of return data when SRID 4326 is given as argument:
Values are expressed in WGS84 (World Geodetic System)Â https://spatialreference.org/ref/epsg/wgs-84/
Example of return data when SRIDÂ 3011 is given as argument:
(Data is presented in EPSG projection 3011 - sweref99 18 00)
Proximity Search
planned
Ability to search object with one of the criteria being distance from given point or another object.
Display on a map
planned
Ability to display symbols representing objects in given map area.Â
Using data for pointcloud navigation
 Viewing point-cloud requires a separate account at Navvis Ivion.
Configuration
Enable point cloud viewer in System settings:
Using the viewer
When the viewer is enabled, a new view type preference will become available: PC (PointCloud)
When this view type is enabled, a system will attempt to fetch Geo location of the object.Â
If the location data is available, a system will search for a nearby site in Navvis system. When the site is located and opened, a navigation to scan position will be performed: