XC (TQL)

Instead of specifying a clause parameter with a particular Item ID, it is possible to use the 'XC' characters for its value. Using 'XC' automatically creates a TQL statement for every Item ID in that clause parameter that overlaps the Search Polygon. Both the generated TQL statements and their results are handled internally as arrays.

This Search Polygon is determined by the linked content item. Since content item linkage is currently limited to Template Text and Excel Panels, XC should only be used there.

Example

Neighborhoods in an example project

Areas in an example project

Consider the following (simplified) Neighborhood data of a project:

[ {
  "id" : 0,  "name" : "East Side",
  "polygons" : { "type" : "MultiPolygon", "coordinates" : [ [ [ [ 250.0, -500.0 ], [ 500.0, -500.0 ], [ 500.0, 0.0 ], [ 250.0, 0.0 ], [ 250.0, -500.0 ] ] ] ]  }
}, {
  "id" : 1,  "name" : "West Side",
  "polygons" : {  "type" : "MultiPolygon", "coordinates" : [ [ [ [ 0.0, -500.0 ], [ 250.0, -500.0 ], [ 250.0, 0.0 ], [ 0.0, 0.0 ], [ 0.0, -500.0 ] ] ] ]  }
} ]

and the Area data:

[ {
  "id" : 0,  "name" : "Upper Left",  
  "polygons" : {    "type" : "MultiPolygon",    "coordinates" : [ [ [ [ 110.0, -110.0 ], [ 110.0, -100.0 ], [ 100.0, -100.0 ], [ 100.0, -110.0 ], [ 110.0, -110.0 ] ] ] ]  }
  }, {
  "id" : 1,  "name" : "Upper Right",  
  "polygons" : {    "type" : "MultiPolygon",    "coordinates" : [ [ [ [ 435.0, -95.0 ], [ 425.0, -95.0 ], [ 425.0, -105.0 ], [ 435.0, -105.0 ], [ 435.0, -95.0 ] ] ] ]  }
  }, {  
  "id" : 2,  "name" : "Lower Left",  
  "polygons" : {    "type" : "MultiPolygon",    "coordinates" : [ [ [ [ 165.0, -425.0 ], [ 165.0, -415.0 ], [ 155.0, -415.0 ], [ 155.0, -425.0 ], [ 165.0, -425.0 ] ] ] ]  }
  }, {  
  "id" : 3,  "name" : "Lower Right",  
  "polygons" : {    "type" : "MultiPolygon",    "coordinates" : [ [ [ [ 315.0, -395.0 ], [ 325.0, -395.0 ], [ 325.0, -385.0 ], [ 315.0, -385.0 ], [ 315.0, -395.0 ] ] ] ]  }
} ]

For example, a TQL statement in a Template Text Panel applied to neighborhoods creates separate instances for 'East Side' and 'West Side'.

The TQL statement

SELECT_NAME_WHERE_AREA_IS_XC

for the Text Panel linked to Neighborhood "East Side" is internally replaced with a list of TQL statements, separated by commas,

[ SELECT_NAME_WHERE_AREA_IS_1, SELECT_NAME_WHERE_AREA_IS_3 ]

Its result will be a list of names, separated by commas; for example:

[ "Upper Right", "Lower Right" ]

Notes

• The following variants on XC exist:
  • XCA: A combination between XC and XA.
  • XCK: A combination between XC and XK.
• The result of an XC-queries are array of values without the brackets when the Setting TQL_PANEL_BRACKETED is set to 'false'.

See also

• YC (TQL)
• X (TQL)
• XA (TQL)
• XK (TQL)

API Endpoints

• Api session event editor building query

---

TQL Clause parameters

Spatial

Area • Area with attribute • Buffer • Layertype • Map • Neighborhood • Neighborhood with attribute • Terrain • Terrain with attribute • Zone • Zone with attribute

Attribute

Attribute • Attribute max • Attribute min • Attribute mult • Index

Grid

Grid • Grid with attribute • Gridtype • Gridvalue • Maxgridvalue • Mingridvalue • Overlay • Resulttype • Timeframe

Item

Address • Building • Building with attribute • Function • Global • Indicator • Levee • Measure • Panel • Relation • Scenario • Stakeholder

Net

Net line • Net type • Net function • Net load • Net cluster

Property

Category • Categorymult • Crs • Functionmult • Layertype • Iteration • Key • Map • Name • Residence • Road system • Stakeholdertype • State • Term

Replacement

X • XA • XC • XK • Y • YA • YC • YK • ID • Relation • Sort

Other

Select • Update