Tygron Support wiki - Recent changes [en]

YC (TQL)

Frank@tygron.nl — Wed, 20 May 2026 14:39:59 GMT

Example

← Older revision		Revision as of 14:39, 20 May 2026
Line 29:		Line 29:
	} ]		} ]
	</pre>		</pre>
			Also Consider the situation where a TQL statement is present in the Text Body of a Template Text Panel. This Template Panel is applied on neighborhoods, creating two Text Panel instances, one automatically linked to Neighborhood 'East Side' and one to 'West Side.

	The TQL statement		The TQL statement
	<pre>SELECT_NAME_WHERE_AREA_IS_YC_AND_NEIGHBORHOOD_IS_0</pre> is internally replaced with a list of TQL ~~statement arrays~~, separated by comma's,		<pre>SELECT_NAME_WHERE_AREA_IS_YC_AND_NEIGHBORHOOD_IS_0</pre>
			for the Text Panel linked to Neighborhood "East Side" is internally replaced with a list of TQL statements, separated by comma's,
	<pre>[SELECT_NAME_WHERE_AREA_IS_1_AND_NEIGHBORHOOD_IS_0], [SELECT_NAME_WHERE_AREA_IS_3_AND_NEIGHBORHOOD_IS_0]</pre>		<pre>[SELECT_NAME_WHERE_AREA_IS_1_AND_NEIGHBORHOOD_IS_0], [SELECT_NAME_WHERE_AREA_IS_3_AND_NEIGHBORHOOD_IS_0]</pre>
	Its result will be an array of name arrays, separated by comma's, for example:		Its result will be an array of name arrays, separated by comma's, for example:

XC (TQL)

Frank@tygron.nl — Wed, 20 May 2026 14:37:12 GMT

← Older revision		Revision as of 14:37, 20 May 2026
(One intermediate revision by the same user not shown)
Line 32:		Line 32:
	</pre>		</pre>

	The TQL statement		Also Consider the situation where a TQL statement is present in the Text Body of a Template Text Panel. This Template Panel is applied on neighborhoods, creating two Text Panel instances, one automatically linked to Neighborhood 'East Side' and one to 'West Side.
	<pre>~~SELECT_NAME_WHERE_AREA_IS_XC_AND_NEIGHBORHOOD_IS_0~~</pre> is internally replaced with a list of TQL statements, separated by comma's,
	<pre>~~SELECT_NAME_WHERE_AREA_IS_1_AND_NEIGHBORHOOD_IS_0~~, ~~SELECT_NAME_WHERE_AREA_IS_3_AND_NEIGHBORHOOD_IS_0~~</pre>		The TQL statement
			<pre>SELECT_NAME_WHERE_AREA_IS_XC</pre> for the Text Panel linked to Neighborhood "East Side" is internally replaced with a list of TQL statements, separated by comma's,
			<pre>SELECT_NAME_WHERE_AREA_IS_1, SELECT_NAME_WHERE_AREA_IS_3</pre>
	Its result will be a list of names, separated by comma's, for example:		Its result will be a list of names, separated by comma's, for example:
	<pre>"Upper Right", "Lower Right"</pre>		<pre>"Upper Right", "Lower Right"</pre>

X query (Excel)

Frank@tygron.nl — Wed, 20 May 2026 14:29:25 GMT

XC queries

← Older revision		Revision as of 14:29, 20 May 2026
Line 167:		Line 167:
	* [[Excel]]		* [[Excel]]
	* [[TQL]]		* [[TQL]]
			* [[Select (TQL)]], [[Update (TQL)]] and [[Clause (TQL)]]
	}}		}}

XC (TQL)

Frank@tygron.nl — Wed, 20 May 2026 13:25:07 GMT

← Older revision		Revision as of 13:25, 20 May 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	Instead of specifying a clause parameter with a particular [[Item ID]], it is possible to use the 'XC' characters for its value. The result of using 'XC' for the clause value, is the automatic creation of multiple TQL statements, one with each Item ID for that Clause Parameter, but only the Items that are covered by the ~~calculated~~ ''Search Polygon'' of the TQL statement. ~~The~~ ''Search Polygon'~~' is calculated by overlapping the clause polygon. Per clause type it is indicated if it limits the 'Search Polygon~~'. Internally, the resulting TQL statements are placed in a single array; Similarly the result will be an array of TQL results.		Instead of specifying a clause parameter with a particular [[Item ID]], it is possible to use the 'XC' characters for its value. The result of using 'XC' for the clause value, is the automatic creation of multiple TQL statements, one with each Item ID for that Clause Parameter, but only the Items that are covered by the ''Search Polygon'' of the TQL statement. Items are only included if they are overlapped by the ''Search Polygon''. Internally, the resulting TQL statements are placed in a single array; Similarly the result will be an array of TQL results.

			This ''Search Polygon'' is determined by the linked content item. Currently content item linkage only occurs with Template Text and Excel Panels and therefore XC should only be used for this Panels.

	==Example==		==Example==

YK (TQL)

Frank@tygron.nl — Wed, 20 May 2026 13:14:17 GMT

Example

← Older revision		Revision as of 13:14, 20 May 2026
Line 28:		Line 28:
	The TQL statement to obtain the names of the Culverts used by the Water Overlay is:		The TQL statement to obtain the names of the Culverts used by the Water Overlay is:
	<pre>SELECT_NAME_WHERE_BUILDING_IS_YK_CULVERT_DIAMETER_AND_GRID_IS_6</pre>		<pre>SELECT_NAME_WHERE_BUILDING_IS_YK_CULVERT_DIAMETER_AND_GRID_IS_6</pre>
	which internally is replaced with a list of TQL ~~statements~~, separated by comma's,		which internally is replaced with a list of TQL statement arrays, separated by comma's,
	<pre>[SELECT_NAME_WHERE_BUILDING_IS_0_AND_GRID_IS_6], [SELECT_NAME_WHERE_BUILDING_IS_2_AND_GRID_IS_6], [SELECT_NAME_WHERE_BUILDING_IS_5_AND_GRID_IS_6]</pre>		<pre>[SELECT_NAME_WHERE_BUILDING_IS_0_AND_GRID_IS_6], [SELECT_NAME_WHERE_BUILDING_IS_2_AND_GRID_IS_6], [SELECT_NAME_WHERE_BUILDING_IS_5_AND_GRID_IS_6]</pre>
	Its result will be a list of arrays of names, separated by a comma:		Its result will be a list of arrays of names, separated by a comma:

YA (TQL)

Frank@tygron.nl — Wed, 20 May 2026 13:13:42 GMT

Example

← Older revision		Revision as of 13:13, 20 May 2026
Line 20:		Line 20:
	The TQL statement to obtain the names of the monumental Buildings is:		The TQL statement to obtain the names of the monumental Buildings is:
	<pre>SELECT_NAME_WHERE_BUILDING_IS_YA_MONUMENTAL</pre>		<pre>SELECT_NAME_WHERE_BUILDING_IS_YA_MONUMENTAL</pre>
	which internally is replaced with a list of TQL ~~statements~~, separated by a comma:		which internally is replaced with a list of TQL statement arrays, separated by a comma:
	<pre>[SELECT_NAME_WHERE_BUILDING_IS_1], [SELECT_NAME_WHERE_BUILDING_IS_2], [SELECT_NAME_WHERE_BUILDING_IS_4]</pre>		<pre>[SELECT_NAME_WHERE_BUILDING_IS_1], [SELECT_NAME_WHERE_BUILDING_IS_2], [SELECT_NAME_WHERE_BUILDING_IS_4]</pre>
	Its result will be a list of arrays with names, separated by a comma:		Its result will be a list of arrays with names, separated by a comma:

YC (TQL)

Frank@tygron.nl — Wed, 20 May 2026 13:13:00 GMT

Example

← Older revision		Revision as of 13:13, 20 May 2026
(3 intermediate revisions by the same user not shown)
Line 31:		Line 31:

	The TQL statement		The TQL statement
	<pre>~~SELECT_NAME_WHERE_AREA_IS_XC_AND_NEIGHBORHOOD_IS_0~~</pre> is internally replaced with a list of TQL ~~statements~~, separated by comma's,		<pre>SELECT_NAME_WHERE_AREA_IS_YC_AND_NEIGHBORHOOD_IS_0</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,
	<pre>[SELECT_NAME_WHERE_AREA_IS_1_AND_NEIGHBORHOOD_IS_0], [SELECT_NAME_WHERE_AREA_IS_3_AND_NEIGHBORHOOD_IS_0]</pre>		<pre>[SELECT_NAME_WHERE_AREA_IS_1_AND_NEIGHBORHOOD_IS_0], [SELECT_NAME_WHERE_AREA_IS_3_AND_NEIGHBORHOOD_IS_0]</pre>
	Its result will be an array of name arrays, separated by comma's, for example:		Its result will be an array of name arrays, separated by comma's, for example:
Line 37:		Line 37:

	==Clause Parameters==		==Clause Parameters==
	The XC value can be used in the following TQL Clause parameters:		The YC value can be used in the following TQL Clause parameters:
			<div style="column-count:3">
			*[[Address (TQL Param)]]
			*[[Area (TQL Param)]]
			*[[Building (TQL Param)]]
			*[[Neighborhood (TQL Param)]]
			*[[Zone (TQL Param)]]
			*[[Net load (TQL Param)]]
			*[[Net line (TQL Param)]]
			</div>

	{{article end		{{article end
Line 44:		Line 53:
	**YCK: A combination between [[YC (TQL)\|YC]] and [[YK (TQL)\|YK]].		**YCK: A combination between [[YC (TQL)\|YC]] and [[YK (TQL)\|YK]].
	\|seealso=		\|seealso=
	*[[YC (TQL)]]		*[[XC (TQL)]]
	*[[X (TQL)]]		*[[Y (TQL)]]
	*[[XA (TQL)]]		*[[YA (TQL)]]
	*[[XK (TQL)]]		*[[YK (TQL)]]

	}}		}}

XC (TQL)

Frank@tygron.nl — Wed, 20 May 2026 13:11:22 GMT

Clause Parameters

← Older revision		Revision as of 13:11, 20 May 2026
(One intermediate revision by the same user not shown)
Line 38:		Line 38:
	==Clause Parameters==		==Clause Parameters==
	The XC value can be used in the following TQL Clause parameters:		The XC value can be used in the following TQL Clause parameters:
			<div style="column-count:3">
			*[[Address (TQL Param)]]
			*[[Area (TQL Param)]]
			*[[Building (TQL Param)]]
			*[[Neighborhood (TQL Param)]]
			*[[Zone (TQL Param)]]
			*[[Net load (TQL Param)]]
			*[[Net line (TQL Param)]]
			</div>

	{{article end		{{article end

Update (TQL)

Frank@tygron.nl — Wed, 20 May 2026 12:44:56 GMT

Composition of an Update Query======Composition of a Select Query

← Older revision		Revision as of 12:44, 20 May 2026
(3 intermediate revisions by the same user not shown)
Line 2:		Line 2:

	===Composition of an Update Query===		===Composition of an Update Query===
			An Update TQL query provides a means to update an attribute to one or more values for a selection of data of a [[session]].
			The 'Update' statement is consists of the <code>UPDATE</code> word followed by the context, for example <code>AREA</code>. Next the [[attribute]] to update is stated, followed by the word <code>WHERE</code>. Depending on the context, one or more [[Clause (TQL)\|clause]]s can be added. Clauses are separated with the <code>AND</code> word. All of these parts are separated by an underscore <code>_</code>.

			An example of a TQL select statement is: <code>UPDATE_AREA_WATER_LEVEL_M_WHERE_AREA_IS_0</code>. In this example:
			* <code>UPDATE</code> is the statement
			* <code>AREA</code> is the context
			* <code>WATER_LEVEL_M</code> is the attribute
			* <code>AREA__IS_0</code> is the first clause.

			This adds or updates the attribute WATER_LEVEL_M for the area with ID 0 to a particular value. The particular value is supplied separately and the way it is supplied depends on the situation in which this statement is executed.

	===Executing an Update Query===		===Executing an Update Query===
	TQL Queries can be executed using:		TQL Queries can be executed using:
	* [[Query Tool]] in the {{software}}; For creating and testing TQL queries.		* [[Query Tool]] in the {{software}}; For creating and testing TQL queries. Update value can be supplied using the corresponding field.
	* [[Excel Indicator#Naming Cells\|Names in Excel]]s; Used for [[Indicator]] and [[Panel]]s and supports more complex queries.		* [[Excel Indicator#Naming Cells\|Names in Excel]]s; Used for [[Indicator]] and [[Panel]]s and supports more complex queries. The update value is obtained from the Excel cell to which the TQL statement is [[TQL (Excel)\|linked]].
	* [[API]]'s query endpoint; Using <code>api/session/query/<TQLQUERY></code>		* [[API]]'s query endpoint; Using <code>api/session/query/<TQLQUERY></code> with an additional parameter for the update value.

	===List of Update types===		===List of Update types===

Select (TQL)

Frank@tygron.nl — Wed, 20 May 2026 12:27:36 GMT

Executing a Select Query

← Older revision		Revision as of 12:27, 20 May 2026
(One intermediate revision by the same user not shown)
Line 13:		Line 13:
	* [[Excel Indicator#Naming Cells\|Names in Excel]]s; Used for [[Indicator]] and [[Panel]]s and supports more complex queries.		* [[Excel Indicator#Naming Cells\|Names in Excel]]s; Used for [[Indicator]] and [[Panel]]s and supports more complex queries.
	* [[API]]'s query endpoint; Using <code>api/session/query/<TQLQUERY></code>		* [[API]]'s query endpoint; Using <code>api/session/query/<TQLQUERY></code>
			* [[Text Panel]]s and [[Template Text Panel]]s; TQL statements must be preceded by a dollar sign; for example: <code>$SELECT_NAME_WHERE_NEIGHBORHOOD_IS_X</code>

	===List of Select types===		===List of Select types===

Update (TQL)

Frank@tygron.nl — Wed, 20 May 2026 12:26:07 GMT

Executing an Update Query

← Older revision		Revision as of 12:26, 20 May 2026
Line 6:		Line 6:
	TQL Queries can be executed using:		TQL Queries can be executed using:
	* [[Query Tool]] in the {{software}}; For creating and testing TQL queries.		* [[Query Tool]] in the {{software}}; For creating and testing TQL queries.
	* [[Global]]s; Executed every calculation.
	* [[Excel Indicator#Naming Cells\|Names in Excel]]s; Used for [[Indicator]] and [[Panel]]s and supports more complex queries.		* [[Excel Indicator#Naming Cells\|Names in Excel]]s; Used for [[Indicator]] and [[Panel]]s and supports more complex queries.
	* [[API]]'s query endpoint; Using <code>api/session/query/<TQLQUERY></code>		* [[API]]'s query endpoint; Using <code>api/session/query/<TQLQUERY></code>

Template:TQL nav

Frank@tygron.nl — Wed, 20 May 2026 12:25:39 GMT

← Older revision		Revision as of 12:25, 20 May 2026
Line 57:		Line 57:
	}}		}}
	{{nav-group\|postappend= (TQL) \| Other		{{nav-group\|postappend= (TQL) \| Other
			\| Select
	\| Update		\| Update
	\| Clause		\| Clause
	}}		}}
	}}		}}

XK (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:54:24 GMT

← Older revision		Revision as of 14:54, 19 May 2026
Line 1:		Line 1:
	The 'XK' clause value is a variation on the [[XA (TQL)\|'XA']] clause value. The characters 'XK' should be followed by an underscore and the name of a [[Key]]; for example '''XK_CULVERT_DIAMETER'''~~. Also see the [[#Example\|example ]]below~~.		The 'XK' clause value is a variation on the [[XA (TQL)\|'XA']] clause value. The characters 'XK' should be followed by an underscore and the name of a [[Key]]; for example '''XK_CULVERT_DIAMETER'''.

	This Key is used to obtain the name of an Attribute, given a Grid Overlay. This Grid Overlay is obtained from the same TQL statement, which should contain one of the following clause parameters:		This Key is used to obtain the name of an Attribute, given a Grid Overlay. This Grid Overlay is obtained from the same TQL statement, which should contain one of the following clause parameters:

YK (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:54:17 GMT

← Older revision		Revision as of 14:54, 19 May 2026
Line 1:		Line 1:
	The 'YK' clause value is a variation on the [[YA (TQL)\|'YA']] clause value. The characters 'YK' should be followed by an underscore and the name of a [[Key]]; for example '''YK_CULVERT_DIAMETER'''~~. Also see the [[#Example\|example ]]below~~.		The 'YK' clause value is a variation on the [[YA (TQL)\|'YA']] clause value. The characters 'YK' should be followed by an underscore and the name of a [[Key]]; for example '''YK_CULVERT_DIAMETER'''.

	This Key is used to obtain the name of an Attribute, given a Grid Overlay. This Grid Overlay is obtained from the same TQL statement, which should contain one of the following clause parameters:		This Key is used to obtain the name of an Attribute, given a Grid Overlay. This Grid Overlay is obtained from the same TQL statement, which should contain one of the following clause parameters:

YA (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:54:10 GMT

← Older revision		Revision as of 14:54, 19 May 2026
Line 1:		Line 1:
	The 'YA' clause value is a variation on the [[Y (TQL)\|'Y']] clause value. The characters 'YA' should be followed by an underscore and the name of an [[Attribute]]; for example '''YA_MONUMENTAL'''~~. Also see the [[#Example\|example ]]below~~.		The 'YA' clause value is a variation on the [[Y (TQL)\|'Y']] clause value. The characters 'YA' should be followed by an underscore and the name of an [[Attribute]]; for example '''YA_MONUMENTAL'''.

	The result of using 'XA' for the clause value, is the automatic creation of multiple TQL statements, one with each Item ID for that Clause Parameter that can be found in the project data. Items are only taken into account of they have a non zero value for the specified attribute.		The result of using 'XA' for the clause value, is the automatic creation of multiple TQL statements, one with each Item ID for that Clause Parameter that can be found in the project data. Items are only taken into account of they have a non zero value for the specified attribute.

XA (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:54:00 GMT

← Older revision		Revision as of 14:54, 19 May 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	The 'XA' clause value is a variation on the [[X (TQL)\|'X']] clause value. The characters 'XA' should be followed by an underscore and the name of an [[Attribute]]; for example '''XA_MONUMENTAL'''~~. Also see the [[#Example\|example ]]below~~.		The 'XA' clause value is a variation on the [[X (TQL)\|'X']] clause value. The characters 'XA' should be followed by an underscore and the name of an [[Attribute]]; for example '''XA_MONUMENTAL'''.

	The result of using 'XA' for the clause value, is the automatic creation of multiple TQL statements, one with each Item ID for that Clause Parameter that can be found in the project data. Items are only taken into account of they have a non zero value for the specified attribute.		The result of using 'XA' for the clause value, is the automatic creation of multiple TQL statements, one with each Item ID for that Clause Parameter that can be found in the project data. Items are only taken into account of they have a non zero value for the specified attribute.

YK (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:51:54 GMT

← Older revision		Revision as of 14:51, 19 May 2026
Line 34:		Line 34:
	Similarly, the TQL statement to obtain the culvert Diameters of the Culverts used by the water Overlay is:		Similarly, the TQL statement to obtain the culvert Diameters of the Culverts used by the water Overlay is:
	<pre>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_YK_CULVERT_DIAMETER_AND_GRID_IS_6_AND_KEY_IS_CULVERT_DIAMETER</pre>		<pre>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_YK_CULVERT_DIAMETER_AND_GRID_IS_6_AND_KEY_IS_CULVERT_DIAMETER</pre>
	Its result will be ~~a list~~ of arrays ~~of values~~, separated by a comma:		Its result will be an array of value arrays, separated by a comma:
	<pre>[0.2], [1.0], [2.0]</pre>		<pre>[0.2], [1.0], [2.0]</pre>

YC (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:51:18 GMT

← Older revision		Revision as of 14:51, 19 May 2026
Line 33:		Line 33:
	<pre>SELECT_NAME_WHERE_AREA_IS_XC_AND_NEIGHBORHOOD_IS_0</pre> is internally replaced with a list of TQL statements, separated by comma's,		<pre>SELECT_NAME_WHERE_AREA_IS_XC_AND_NEIGHBORHOOD_IS_0</pre> is internally replaced with a list of TQL statements, separated by comma's,
	<pre>[SELECT_NAME_WHERE_AREA_IS_1_AND_NEIGHBORHOOD_IS_0], [SELECT_NAME_WHERE_AREA_IS_3_AND_NEIGHBORHOOD_IS_0]</pre>		<pre>[SELECT_NAME_WHERE_AREA_IS_1_AND_NEIGHBORHOOD_IS_0], [SELECT_NAME_WHERE_AREA_IS_3_AND_NEIGHBORHOOD_IS_0]</pre>
	Its result will be ~~a list~~ of ~~names~~, separated by comma's, for example:		Its result will be an array of name arrays, separated by comma's, for example:
	<pre>["Upper Right"], ["Lower Right"]</pre>		<pre>["Upper Right"], ["Lower Right"]</pre>

Y (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:50:56 GMT

← Older revision		Revision as of 14:50, 19 May 2026
Line 16:		Line 16:
	<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,		<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_Y</pre> is internally replaced with a list of TQL statement arrays, separated by comma's,
	<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_1 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_4 ]</pre>		<pre> [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_1 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_2 ], [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_3 ] , [ SELECT_NAME_WHERE_NEIGHBORHOOD_IS_4 ]</pre>
	Its result will be ~~a list~~ of ~~names~~, separated by comma's, for example:		Its result will be an array of name arrays, separated by comma's, for example:
	<pre>["De Manege"], ["De Lancaster"], ["De Landstreken"], ["De Kruidentuin"], ["Golfresidentie"]</pre>		<pre>["De Manege"], ["De Lancaster"], ["De Landstreken"], ["De Kruidentuin"], ["Golfresidentie"]</pre>

ID (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:42:47 GMT

← Older revision		Revision as of 14:42, 19 May 2026
Line 7:		Line 7:
	<pre>		<pre>
	[		[
	{ "id" : 0, "name" : "East Side", "attributes": { "INHABITANTS": 600.0 } },		{ "id" : 0, "name" : "East Side", "attributes": { "INHABITANTS": [ 600.0 ] } },
	{ "id" : 1, "name" : "West Side", "attributes": { "INHABITANTS": 200.0 } }		{ "id" : 1, "name" : "West Side", "attributes": { "INHABITANTS": [ 200.0 ] } }
	]		]
	</pre>		</pre>

TQL name

Frank@tygron.nl — Tue, 19 May 2026 14:21:07 GMT

← Older revision		Revision as of 14:21, 19 May 2026
Line 1:		Line 1:
	~~{{stub}}~~

	A [[TQL]] name is a name which fits a specific set of restrictions, allowing it to be used unambiguously in [[TQL\|TQL queries]]. [[Attribute]]s and [[Global]]s must always have a name conforming to those restrictions, because queries use those names verbatim.		A [[TQL]] name is a name which fits a specific set of restrictions, allowing it to be used unambiguously in [[TQL\|TQL queries]]. [[Attribute]]s and [[Global]]s must always have a name conforming to those restrictions, because queries use those names verbatim.

ID (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:12:19 GMT

← Older revision		Revision as of 14:12, 19 May 2026
(11 intermediate revisions by the same user not shown)
Line 12:		Line 12:
	</pre>		</pre>

	And a Template Text Panel applied on Neighborhoods:		And a Template Text Panel applied on Neighborhoods, resulting in two Text Panel instances:
	<pre>		<pre>
	[		[
	{		{
	"id" : 2,		"id" : 2, "mapLink" : "NEIGHBORHOODS", "name" : "Template Text Panel", "type" : "TEMPLATE_TEXT_PANEL",
	"mapLink" : "NEIGHBORHOODS",		"text" : "Name: $SELECT_NAME_WHERE_NEIGHBORHOOD_IS_ID<br>Inhabitants: $SELECT_ATTRIBUTE_WHERE_NEIGHBORHOOD_IS_ID_AND_NAME_IS_INHABITANTS"
	"name" : "Template Text Panel",		} , {
	"text" : "Name: $SELECT_NAME_WHERE_NEIGHBORHOOD_IS_ID<br>Inhabitants: $SELECT_ATTRIBUTE_WHERE_NEIGHBORHOOD_IS_ID_AND_NAME_IS_INHABITANTS",		"contentID" : 0, "contentMapLink" : "NEIGHBORHOODS", "id" : 3, "name" : "Template Text Panel: East Side", "parentID" : 2, "type" : "TEXT_PANEL"
	~~"type" : "TEMPLATE_TEXT_PANEL",~~		} , {
	},		"contentID" : 1, "contentMapLink" : "NEIGHBORHOODS", "id" : 4, "name" : "Template Text Panel: West Side", "parentID" : 2, "type" : "TEXT_PANEL"
	{		}
	"contentID" : 0,
	"contentMapLink" : "NEIGHBORHOODS",
	"id" : 3,
	"name" : "Template Text Panel: East Side",
	"parentID" : 2,
	"type" : "TEXT_PANEL",
	},
	{
	"contentID" : 1,
	"contentMapLink" : "NEIGHBORHOODS",
	"id" : 4,
	"name" : "Template Text Panel: West Side",
	"parentID" : 2,
	"type" : "TEXT_PANEL",
	}
	]		]
	</pre>		</pre>

	~~The~~ TQL statement		Since each panel is linked to a particular Neighborhood, through the ''contentID'' and ''contentMaplink'' parameters, the TQL statement <code>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_ID</code> is internally replaced with:
	<~~pre~~>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_ID</~~pre~~> is internally replaced with		:<code>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0</code> for the first Text Panel
	<~~pre~~>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0/~~pre~~> for the first Text Panel ~~and~~ <~~pre~~>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_1/~~pre~~> for the second Text Panel~~, as these are the Neighborhoods each panel is linked to (using the ''contentID'' and ''contentMaplink'' parameters).~~		:<code>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_1</code> for the second Text Panel

	The result of each query will be:		The result of each query will be:
	<~~pre~~>"East Side"</~~pre~~> and <~~pre~~>"West Side"</~~pre~~>		<code>"East Side"</code> and <code>"West Side"</code>

	Similarly, the value of the attribute INHABITANTS of the linked Neighborhood can be obtained using		Similarly, the value of the attribute INHABITANTS of the linked Neighborhood can be obtained using
	<~~pre~~>SELECT_ATTRIBUTE_WHERE_NEIGHBORHOOD_IS_ID_AND_NAME_IS_INHABITANTS</~~pre~~>.		<code>SELECT_ATTRIBUTE_WHERE_NEIGHBORHOOD_IS_ID_AND_NAME_IS_INHABITANTS</code>.

	==Clause Parameters==		==Clause Parameters==

ID (TQL)

Frank@tygron.nl — Tue, 19 May 2026 14:03:37 GMT

Created page with "Instead of specifying the value of a clause parameter with a particular Item ID, it is possible to use the 'ID' characters for its value. The result of using 'ID' for the clause value, is that is automatically filled in using the Item that contains the TQL statement. ID clause values are often used in combination with Template Panels; For example: Consider A Template Text Panel applied on Neighborhoods ==Example== Consider the following (simplified) Neighborho..."

New page

Instead of specifying the value of a clause parameter with a particular [[Item ID]], it is possible to use the 'ID' characters for its value. The result of using 'ID' for the clause value, is that is automatically filled in using the Item that contains the TQL statement.

ID clause values are often used in combination with [[Template Panel]]s; For example: Consider A Template Text Panel applied on Neighborhoods

==Example==
Consider the following (simplified) Neighborhood data of a project:
<pre>
[
{ "id" : 0, "name" : "East Side", "attributes": { "INHABITANTS": 600.0 } },
{ "id" : 1, "name" : "West Side", "attributes": { "INHABITANTS": 200.0 } }
]
</pre>

And a Template Text Panel applied on Neighborhoods:
<pre>
[
{
"id" : 2,
"mapLink" : "NEIGHBORHOODS",
"name" : "Template Text Panel",
"text" : "Name: $SELECT_NAME_WHERE_NEIGHBORHOOD_IS_ID<br>Inhabitants: $SELECT_ATTRIBUTE_WHERE_NEIGHBORHOOD_IS_ID_AND_NAME_IS_INHABITANTS",
"type" : "TEMPLATE_TEXT_PANEL",
},
{
"contentID" : 0,
"contentMapLink" : "NEIGHBORHOODS",
"id" : 3,
"name" : "Template Text Panel: East Side",
"parentID" : 2,
"type" : "TEXT_PANEL",
},
{
"contentID" : 1,
"contentMapLink" : "NEIGHBORHOODS",
"id" : 4,
"name" : "Template Text Panel: West Side",
"parentID" : 2,
"type" : "TEXT_PANEL",
}
]
</pre>

The TQL statement
<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_ID</pre> is internally replaced with
<pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_0/pre> for the first Text Panel and <pre>SELECT_NAME_WHERE_NEIGHBORHOOD_IS_1/pre> for the second Text Panel, as these are the Neighborhoods each panel is linked to (using the ''contentID'' and ''contentMaplink'' parameters).
The result of each query will be:
<pre>"East Side"</pre> and <pre>"West Side"</pre>
Similarly, the value of the attribute INHABITANTS of the linked Neighborhood can be obtained using
<pre>SELECT_ATTRIBUTE_WHERE_NEIGHBORHOOD_IS_ID_AND_NAME_IS_INHABITANTS</pre>.

==Clause Parameters==
The X value can be used in the following TQL Clause parameters:

{{article end
|notes=
|seealso=
*[[Y (TQL)]]
*[[XA (TQL)]]
*[[XC (TQL)]]
*[[XK (TQL)]]

}}

{{TQL param nav}}

XC (TQL)

Frank@tygron.nl — Tue, 19 May 2026 13:00:10 GMT

Clause Parameters

← Older revision		Revision as of 13:00, 19 May 2026
Line 40:		Line 40:

	{{article end		{{article end

			\|notes=*The following variants on XC exist:
			**XCA: A combination between [[XC (TQL)\|XC]] and [[XA (TQL)\|XA]].
			**XCK: A combination between [[XC (TQL)\|XC]] and [[XK (TQL)\|XK]].
	\|seealso=		\|seealso=
	*[[YC (TQL)]]		*[[YC (TQL)]]

XK (TQL)

Frank@tygron.nl — Tue, 19 May 2026 12:57:41 GMT

← Older revision		Revision as of 12:57, 19 May 2026
(One intermediate revision by the same user not shown)
Line 42:		Line 42:
	{{article end		{{article end
	\|notes=*In case no Grid is specified by any of the other clauses of the original TQL statement, the result will be 0 generated TQL statements; an empty array.		\|notes=*In case no Grid is specified by any of the other clauses of the original TQL statement, the result will be 0 generated TQL statements; an empty array.
			*The following variants on XK exist:
			**XCK: A combination between [[XC (TQL)\|XC]] and [[XK (TQL)\|XK]].
	\|seealso=		\|seealso=
	*[[YK (TQL)]]		*[[YK (TQL)]]

XA (TQL)

Frank@tygron.nl — Tue, 19 May 2026 12:57:08 GMT

← Older revision		Revision as of 12:57, 19 May 2026
Line 33:		Line 33:

	{{article end		{{article end
	\|notes=		\|notes=*The following variants on XA exist:
			**XCA: A combination between [[XC (TQL)\|XC]] and [[XA (TQL)\|XA]].
	\|seealso=		\|seealso=
	*[[YA (TQL)]]		*[[YA (TQL)]]

YK (TQL)

Frank@tygron.nl — Tue, 19 May 2026 12:56:16 GMT

Clause Parameters

← Older revision		Revision as of 12:56, 19 May 2026
Line 42:		Line 42:
	{{article end		{{article end
	\|notes=*In case no Grid is specified by any of the other clauses of the original TQL statement, the result will be 0 generated TQL statements; an empty array.		\|notes=*In case no Grid is specified by any of the other clauses of the original TQL statement, the result will be 0 generated TQL statements; an empty array.
			*The following variants on YA exist:
			**YCK: A combination between [[YC (TQL)\|YC]] and [[YK (TQL)\|YK]].
	\|seealso=		\|seealso=
	*[[XK (TQL)]]		*[[XK (TQL)]]