Tygron Query Language

This article is a stub.

Clauses

The following groups of clauses exist:

Specific polygons

Clause	As a polygon	As an item
AREA	The requested data must intersect with this area.	It must be data of this area specifically.
NEIGHBORHOOD	The requested data must intersect with this neighborhood.	It must be data of this neighborhood specifically.
ZONE	The requested data must intersect with this zone.	It must be data of this zone specifically.
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.

Unspecific polygons

Clause	As a polygon	As an item
AREA_WITH_ATTRIBUTE	The requested data must intersect with at least one area with this attribute.	N/A
NEIGHBORHOOD_WITH_ATTRIBUTE	The requested data must intersect with at least one neighborhood with this attribute.	N/A
ZONE_WITH_ATTRIBUTE	The requested data must intersect with at least one zone with this attribute.	N/A
TERRAIN_WITH_ATTRIBUTE	The requested data must intersect with terrain with this attribute.	N/A

Grids

Clause	As a polygon	As an item
MAXGRIDVALUE	It must have at least this value on a grid overlay.	N/A
MINGRIDVALUE	It must have at most this value on a grid overlay.	N/A
GRID	It must fall within this grid.	It must be data of this grid overlay specifically.
GRIDTYPE	It must fall within this type of grid. (If multiple grids of the same type exist this behavior is uncertain.)	It must be data of this type of grid, not a specific "instance" of this grid.

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.