All Collections
Onboarding Materials
Onboarding 2.1 Creating Collections and a Basic Configuration
Onboarding 2.1 Creating Collections and a Basic Configuration
Lauren Scott avatar
Written by Lauren Scott
Updated over a week ago

Configurations allow us to "wire up the brain" of Optioneer so it gives the appropriate weighting to constraints and calculates all metrics relevant to your project.

The section is divided into two main categories. The first discusses the use of collections in Optioneer. These organise your GIS data into a format that Optioneer can understand. The second section covers the setup of the configuration.

๐Ÿ—‚ Creating a Collection

Data layers are often categorised by their source when uploaded to Optioneer. By creating a collection, we can divide them into more convenient groupings for routing. These are then directly linked to your configuration.

Collection types are pre-defined in Optioneer and have a fixed data type: polygon or line. There are three collections that should be used for every project:

  1. Constraints: A polygon dataset containing physical constraints that are usually man-made. For example, buildings, monuments and wind turbines.

  2. Environment: Polygon data layers which describe the environment. Generally, this dataset includes natural physical constraints, geology and zones with designations.

  3. Linear Features: Line data that represents linear infrastructure such as roads, utilities and networks.

Each collection can contain up to 64 layers. In the case you exceed this limit, you can utilise the Constraints Secondary and Environmental Secondary collections.

To create a collection go to the Data Window and carry out the following steps.

  1. Select the Create Collection icon from the left-hand-side toolbar.

  2. Select the collection you wish to add layers to.

  3. If you are adding layers to an existing collection 'select' the version you want to add to from the right-most drop-down menu.

  4. From the list on the left-hand side select the data layers you wish to add by scrolling through the list or using the search bar. You will notice that data layers of the incorrect type cannot be added to the collection.

  5. When you have selected all of your layers, click Add to Collection. They will now appear in the right-hand-side list.

  6. You can remove layers from the collection by selecting them from the right-hand side list and clicking Remove Layers from Collection.

  7. When you have finished defining your collection, you can add an alias to help track your versions.

๐Ÿง  What you need to know about collections!

  • Collections cannot be deleted. Collections are also a tool to help you track the development of a project. They are versioned, meaning at any point in the project you can see what previous results would have taken into account.

  • Collections can be viewed from the Collections Tab under Vector Data in the Map Controls.

  • Raster data doesn't require being added to a collection. Elevation and slope data can be directly linked to a configuration.

๐Ÿง‘โ€๐ŸŽจCreating a Basic Configuration

The details of configurations are covered in advanced modules. But if you need to set up a quick configuration, carry out the following steps.

Go to the Parameters Window. Click on the '+' icon. Name the configuration 'Evaluationcase_[your initials]'. For best practice, you should ensure that the name describes the purpose of the configuration you're making (Asset Type, specific Design Rule etc.).

Select your new configuration, it will appear in the list of configurations on the left-hand side. The next step is to activate your Design Rules.

In your configuration, you will find a list of Design Rules. Design Rules are units of logic that allow Optioneer to implement certain behaviours or carry out calculations. These are discussed more in advanced modules, but for now, toggle on the following design rules. Tip: you can use the search bar to find these.

  1. Routing Constraints - calculate penalty score

  2. Environmental Constraints - calculate penalty score

  3. Linear Feature Crossing

  4. Constraint features within catchment area of route

    1. The catchment distances are configurable in this design rule.

  5. Environmental constraint features within catchment area of route

    1. The catchment distances are configurable in this design rule.

  6. Linear features within catchment area of route

    1. The catchment distances are configurable in this design rule.

  7. Distance to nearest constraint feature

  8. Distance to nearest environmental constraint feature

  9. Distance to nearest linear feature

๐Ÿ˜ Connecting configurations to collections

Now that you have activated them, you need to connect the relevant dataset or collections.

  1. To assign your collections click on 'Dataset'. Here you will find a List of Required Datasets.

    1. ๐Ÿฆ If the dataset is greyed out, none of the active design rules require this dataset.

    2. ๐Ÿ– If the dataset has a red pen next to it, it means that there are unsaved changes to that dataset.

    3. ๐Ÿ”บIf the dataset has a red triangle next to it, it means that Optioneer is missing this dataset and the case will not run.

  2. Click on each one in turn and select the correct collection.

When you have assigned the collections, click Update Configuration and then Save Configuration. You can now carry out initiating evaluation mode.

This configuration will return the:

  1. Presence of constraints on the centreline

    1. Checks if the constraint present

    2. Total distance through the constraint of a given type

  2. Presence of constraints in the proximity of the route

    1. Distance to the nearest constraint feature

    2. Number of features within a specified distance

  3. Crossings of roads and utilities

๐Ÿง  What you need to know about configurations!

  • Optioneer has a couple of in-built tools to help you complete your configuration correctly.

    • If the red triangular warning sign shows, this indicates that something is wrong. This is common if your configuration cannot find the data layer it needs (for example, if it's been removed from a collection)

    • The red pen icon indicated that there are unsaved changes.

  • Collection versions are not updated automatically.

    • When you create a new version of a collection, you will need to assign this to the relevant configuration.

Did this answer your question?