Geo Plugin: Difference between revisions
m (→Geo Link) |
|||
| Line 70: | Line 70: | ||
{{article end | {{article end | ||
|notes= | |notes= | ||
* When mapping [[Attribute]]s, and importing a feature which has an [[Attribute]] targeted by the mapping, the imported [[Item]] will have only the mapped [[Attribute]] with the | * When mapping [[Attribute]]s, and importing a feature which has an [[Attribute]] targeted by the mapping, the imported [[Item]] will have only the mapped [[Attribute]] with the original [[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. | * 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. | ||
|seealso= | |seealso= | ||
Revision as of 09:09, 10 January 2022
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 | Adds Areas. | Geolink:
|
| BUILDING | Vector | Adds Buildings, except roads. | Function
Geolink:
|
| ROAD | Vector | Adds Buildings, specifically roads. | Function
Geolink:
|
| 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) |
Configuration
When a Geo Plugin is created, a number of additional configurations can be entered to define how the source data is to be interpreted. Note that the availability of different configuration options are related to the kind of data the Geo Plugin is configured to import.
- Layer id
- If the data source structures its data in multiple layers of features, which layer should be used.
- CRS
- If the data source does not define its CRS properly, or does not define a CRS at all, which CRS to use (instead).
- Name attribute
- Which Attribute's value should be used to name the imported features.
- Id attribute
- An Attribute which can uniquely identify features in the data source. This is used to detect duplicates of data being retrieved when the data from the data source must be retrieved in multiple passes.
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.
Geo Link
- Main article: Geo Link
A Geolink is a subdefinition for a Geo Plugin. It provides a further definition of which data to import, and how to remap the Attributes.
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 original 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.
