Data Sources

Introduction

One of the first things we do in a project is to import base data and establish base models. However, before we do this, we can get an overview of the project area by using available free services such as WMS and WCS. With these services, we can display background maps (WMS) and elevation models (WCS, for example, 1×1 m grid) for the area.

Procedure for creating WMS or WCS application layers

1. Zoom to the project area with Navigate to area...
2. Create WMS or WCS application layers using the Create... option on the context menu in the application layer list

Tip

In this context, it is useful to know about the function for navigating to an area using place names and addresses, which can be found on the toolbar. Note that the coordinate system must be set in Settings Gemini Terrain... - Project - General for this function to be active.

Base Data and Base Models

The most commonly used base data can be imported directly using the Import... option on the File menu. This is a common import for application layers and models, and the program typically determines where the data should be placed.

You can read more about importing data to application layers in Import and Export Data.

Info

Data from field equipment, surveyed data, and scan data must be imported from the application layer dialog under the Import/export tab.

In the property dialogs for application layers and models, we also find all available functions for importing data.

Base data is data we need to perform tasks within planning, design, and execution. What base data we need will therefore depend on what job we are performing, whether we are planning, designing, or executing.

Typical Base Data Can Be

• Elevation data for terrain surface model
• Underground installations
• Thematic geodata
• Ground layers
• Plans

From the base data, we establish base models that we use as a starting point for designing discipline models. The base models collectively provide a description of the current reality.

Typical Base Models Are

• Terrain surface model
• Ground conditions model
• Existing objects
• Administrative conditions

Discipline Models

Discipline models are designed by various professional environments and show planned interventions in the project area. In Gemini Terrain, we have modules for several disciplines including:

• Roads
• Water and Sewage
• Tunnel
• Excavation
• Planning and regulation areas

Note

We can also import or insert discipline models designed in other systems and use them in tasks related to execution.

Applicable Formats for Base Data and Discipline Models

The table below summarizes the most important formats supported in Gemini Terrain.

Data Type	Format	Import	Export	Note
Drawings	DXF/DWG	x	x
	IFC	x	x
Application Layer Data	SOSI	x	x
	DXF	x	x
	DWG	x
	QUADRI	x
	SHAPE	x	x
	KOF	x	x
	LandXML	x
	LAS	x
	GEO	x	x
	GML	x	x
	Field Books	x	x	All on the market
	LAS/LAZ	x	x
	PTS	x
	DBX	x		Scan data Leica MS50/60
	GeoTIFF	x		Elevation model
	JPG	x		Geotagged photo
	XML	x		IREDES drilling plan and bolt log
Road Models	VIPS	x
	ANPAKKE	x	x
	LandXML cross sections	x
	LandXML 3D lines	x
	Leica DBX database	x
	Trimble DC10	x
	Trimble RXL	x
	Trimble Earthworks	x
	Trimble GCS900	x
	Visual Digger LandXML	x
	Topcon LandXML	x
	NorskInfraGML	x	x
Tunnel Models	IREDES	x	x
	LandXML	x	x
	Leica DBX	x
	Trimble TXL	x

Requirements for Base Data

When exchanging data, there are several requirements that the base data must satisfy:

• Datum/Projection
  In Norway, data exists in several coordinate systems: local, NGO, and EUREF. The industry is moving towards using EUREF89 UTM for administration and EUREF89 NTM for design.

• Metadata
  Data about data, for example, mapping method and year, construction year, type, and material.

• Format
  Which formats should be used for exchange in the project, such as SOSI, XYZ-files, LandXML.