Geo Data Wizard

The Geo Data Wizard

The Geo Data Wizard or in short Data Wizard is a series of steps to guide you through the process of importing Geo data in the Engine. There are several different Data Wizards which each guide you through different processes for importing Geo data in the Engine. The different wizards are for importing data as:

• Constructions (Constructions placed based on the shapes defined in the file)
• Construction values (Constructions are modified based on the attributes in the file)
• Terrain
• Neighborhoods
• Zoning (Zones placed based on the shapes defined in the file)
• Areas Areas placed based on the shapes defined in the file)
• Stakeholders
• Measures

Each of these wizards contain comparable steps which are described below.

When to use your own Data

You need the Data Wizard when you want to import own data in the Tygron Engine. This may be for a number of reasons:

• The project takes place in a location for which there are no data sources available to create the project
• The default data sources are not accurate or up-to-date enough
• The default datasets are not detailed enough
• To do a more extendend analysis in the Engine
• To use in combination with an Excel Indicator or Panel
• For creating more overview in your project, for example by highlighting areas

In these situations, data in the Tygron Engine can be overwritten or supplemented by the user.

Methods for importing Geo Data

There are three methods for importing geo data.

1. Through a GeoJSON file
2. Through a Web Feature Service
3. Through a Catalogue Service for the Web

These methods can be divided into two: uploading data from a file to the Engine and the other is downloading data through an URL to the Engine.

Requirements on Geo Data

There are several requirements for loading in Geo Data. The Data Wizard helps you to transform your data to the proper format for importing.

1. Geo Data in the Engine are always polygons. Line and point features are not allowed by the Engine. The wizards helps you by buffering the line and point features to polygons.
2. All desired attributes must be numerical, so that they can be loaded as valid attribute values. Non-numeric attributes are ignored when attempting to load them as attributes.