Tygron Query Language: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 90: | Line 90: | ||
|- | |- | ||
| GRIDTYPE | | GRIDTYPE | ||
| It must fall within this type of grid. | | It must fall within this type of grid. | ||
| It must be data of this type of grid, not a specific "instance" of this grid. | | It must be data of this type of grid, not a specific "instance" of this grid. | ||
| Technical name indicating a type of grid overlay. | | Technical name indicating a type of grid overlay. | ||
| Line 96: | Line 96: | ||
Note that each grid automatically covers the entire map, unless a minimum gridvalue or maximum gridvalue is defined. For queries such as GRIDAVG, this can be acceptable. However, for example, a query of SELECT_LANDSIZE_WHERE_GRID_IS_2 is functionally the same as SELECT_LANDSIZE. | Note that each grid automatically covers the entire map, unless a minimum gridvalue or maximum gridvalue is defined. For queries such as GRIDAVG, this can be acceptable. However, for example, a query of SELECT_LANDSIZE_WHERE_GRID_IS_2 is functionally the same as SELECT_LANDSIZE. | ||
Also note that when a GRIDTYPE is selected but multiple [[overlays]] of that type exist in the [[project]], there are no guarantees on which overlay is used specifically. | |||
Revision as of 13:54, 26 July 2017
This article is a stub.
Queries
Clauses
The following groups of clauses exist:
Specific polygons
| Clause | As a polygon | As an item | Type |
|---|---|---|---|
| AREA | The requested data must intersect with this area. | It must be data of this area specifically. | ID indicating a specific area. |
| NEIGHBORHOOD | The requested data must intersect with this neighborhood. | It must be data of this neighborhood specifically. | ID indicating a specific neighborhood. |
| ZONE | The requested data must intersect with this zone. | It must be data of this zone specifically. | ID indicating a specific zone. |
| TERRAIN | The requested data must intersect with this terrain type. | It must be data of this type of terrain. There are no specific "instances" of terrain. | ID indicating a type of terrain. |
Unspecific polygons
| Clause | As a polygon | As an item | Type |
|---|---|---|---|
| AREA_WITH_ATTRIBUTE | The requested data must intersect with at least one area with this attribute. | N/A | Attribute name of one or more areas. |
| NEIGHBORHOOD_WITH_ATTRIBUTE | The requested data must intersect with at least one neighborhood with this attribute. | N/A | Attribute name of one or more neighborhoods. |
| ZONE_WITH_ATTRIBUTE | The requested data must intersect with at least one zone with this attribute. | N/A | Attribute name of one or more zones. |
| TERRAIN_WITH_ATTRIBUTE | The requested data must intersect with terrain with this attribute. | N/A | Attribute name of one or more terrains. |
Grids
| Clause | As a polygon | As an item | Type |
|---|---|---|---|
| MAXGRIDVALUE | It must have at least this value on a grid overlay. | N/A | Decimal number. |
| MINGRIDVALUE | It must have at most this value on a grid overlay. | N/A | Decimal number. |
| GRID | It must fall within this grid. | It must be data of this grid overlay specifically. | ID indicating a specific zone. |
| GRIDTYPE | It must fall within this type of grid. | It must be data of this type of grid, not a specific "instance" of this grid. | Technical name indicating a type of grid overlay. |
Note that each grid automatically covers the entire map, unless a minimum gridvalue or maximum gridvalue is defined. For queries such as GRIDAVG, this can be acceptable. However, for example, a query of SELECT_LANDSIZE_WHERE_GRID_IS_2 is functionally the same as SELECT_LANDSIZE.
Also note that when a GRIDTYPE is selected but multiple overlays of that type exist in the project, there are no guarantees on which overlay is used specifically.