Design rule purpose

The purpose of this design rule is pretty simple: count the number of parcels entered by the route and give users a quick calculation of how many individual land owners they might have to deal with. This information isn't used by Optioneer engine in any clever way (at this stage) but it nonetheless provides a useful metric which can be used to assess how feasible a given option is.

How to configure

This design rule only needs being enabled and fed appropriate data. For every route evaluated, the design rule will return a total number of land parcels bisected.

Important notes

  1. Dataset is rasterized to project resolution (default is 30m). This means that slender, complex shape parcels can sometimes go 'missing' as they are not picked up by the rasterizer. Similarly, on rare occasions the rasterization might cause a parcel to 'encroach' on another one.

  2. Optioneer expects that the dataset uploaded contains vector parcel data, where parcels do not overlap with one another.

  3. Feature ID returned on the vertical chart is based on internal numbering of parcels within a geodata layer. Numbers returned by Optioneer should correspond to feature IDs that were originally included in the dataset (but this is not guaranteed).

Input / output summary

Input parameters

There is no input parameters required for this design rule.

This design rule requires a dedicated dataset (see section above) to run correctly.

Output parameters


Example value


Total number of land parcels bisected



ID of parcel crossed at every point of the route

Plot on vertical chart

ID of feature within the GIS dataset

Did this answer your question?