Geo Plugin: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
mNo edit summary
Line 47: Line 47:
| Source(s)
| Source(s)
|}
|}
===Sources===
{{main|Project Source}}
Each Geo Plugin must obtain its data from a source. Sources are defined as [[Project Source]]s in the {{software}}. For vector data, only one source can be added. For grid data, multiple sources can be added.


===Geolink===
===Geolink===
Line 62: Line 66:
: A list of [[Attributes]] which are renamed on import. If the specified [[Attribute]] is present in a feature in the data, the resulting [[Item]] will have an [[Attribute]] with the specified mapped name with the same value.
: A list of [[Attributes]] which are renamed on import. If the specified [[Attribute]] is present in a feature in the data, the resulting [[Item]] will have an [[Attribute]] with the specified mapped name with the same value.


===Sources===
{{main|Project Source}}
Each Geo Plugin must obtain its data from a source. Sources are defined as [[Project Source]]s in the {{software}}. For vector data, only one source can be added. For grid data, multiple sources can be added.


{{article end
{{article end

Revision as of 11:21, 16 December 2021

This article is a stub.

A Geo Plugin is a definition for a connection which should be established when a new Project is created. One or more Geo Plugins can be defined in a Project Template. When that Template is used to create a new Project, the connections defined in the Geo Plugins are established, and data within the new Project's extent is imported. Depending on the Geo Plugin's configuration, various types of data can be added to the new Project automatically.

Types

A Geo Plugin can be used to import the following types of data:

Geo Plugin type Feature type Effect Configurations
AREA Vector Geolink:
  • Matching Attributes
  • Mapped Attributes
BUILDING Vector Function

Geolink:

  • Function
  • Matching Attributes
  • Mapped Attributes
ROAD Vector Function

Geolink:

  • Function
  • Matching Attributes
  • Mapped Attributes
TERRAIN_HEIGHT Grid The elevation model is updated with data from all sources. Data from earlier sources take precedence over later sources. Source(s)
WATER_BOTTOM Grid The elevation model is updated with data from all sources, but only in location with a Water Terrain. Data from earlier sources take precedence over later sources. Source(s)

Sources

Main article: Project Source

Each Geo Plugin must obtain its data from a source. Sources are defined as Project Sources in the Tygron Platform. For vector data, only one source can be added. For grid data, multiple sources can be added.

Geolink

A Geolink is a subdefinition for a Geo Plugin. It provides a specific filter and operation to perform on data found in the source of the Geo Plugin. A Geo Plugin can have multiple Geolinks, each of which can hold a definition for which features to import and how to interpret them.

Geolinks are used for importing vector data.

A Geolink provides the following linkage options:

Type definition
The data matching the Geolink's filter will be imported as Items with the selected definition. For example, when the Geo Plugin is for Buildings, features matched by the Geolink are added to the Project with that specified Function.
Matching Attributes
A list of Attributes which a feature should have in order to be imported. Each attribute can be configured to merely be present, or to need to match one of a list of values. This allows for filtering on a specific group of features only.
Mapped Attributes
A list of Attributes which are renamed on import. If the specified Attribute is present in a feature in the data, the resulting Item will have an Attribute with the specified mapped name with the same value.


Notes

  • When mapping Attributes, and importing a feature which has an Attribute targeted by the mapping, the imported Item will have only the mapped Attribute with the origina Attribute's value, and not the original Attribute. Attributes which are not mapped are included with the Item as is.
  • When a Geolink uses multiple sources for grid data, only locations with NO_DATA values can be further enriched by following sources. Locations where the value is 0 will not be overwritten, as 0 can be a valid value.

How-to's

See also