Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Feature Types can be configured and added in nVIRO. They can also be used within forms in nFORM to automatically categorize features on a site.

Configuring Feature Types in nVIRO

Only a system administrator can modify or add new Feature Types. In the Admin left-hand navigation menu, click the Lookups selection. To view and edit the Feature Types, click Feature Types in the Lookup selection list.

These configuration changes will affect all features, including those in other program areas.

There are several default Feature Types in nVIRO, shown below.

When looking up the features type. The user will see the feature type description, default shape type, label, and status.

The user should have the ability to filter the feature types.

Setting

Description

Lookup Code

Once this code is added, it cannot be changed. The code must be uppercase, have no spaces, and can include numbers.

Lookup Description

This is the description shown on the site map as a general description for all outfalls of this type.

Program Area

These can be selected if specific outfalls should only be available for certain Program Areas.

Site Plan Label

3 character descriptive label (UPPERCASE only).

Site Plan Label Color

Each feature type has a color associated with it. Any color change will affect all the features of this type.

Feature Number Prefix

The number prefix is created on the backend for use with the feature types. If a feature type control is configured on a form where a feature will be input, it will auto-number the feature.

***Note: if you have a label on a control in the same section as your feature that resembles any of the other feature types, it may try to auto-number using that feature type’s prefix. A control labeled like 'Other' will pick up the auto-numbering for the other feature type.

ICIS Permitted Feature Type Code

This code should match the ICIS feature type code.

On this page

Sub-Topics

  • No labels