XC (TQL) - Revision history

Frank@tygron.nl: /* Example */

2026-05-20T15:00:22Z

Example

← Older revision		Revision as of 15:00, 20 May 2026
Line 35:		Line 35:

	The TQL statement		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_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>		<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:

Frank@tygron.nl at 14:37, 20 May 2026

2026-05-20T14:37:12Z

← Older revision		Revision as of 14:37, 20 May 2026
Line 34:		Line 34:
	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.		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_XC</pre> is internally replaced with a list of TQL statements, separated by comma's,		<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>		<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:

Frank@tygron.nl: /* Example */

2026-05-20T14:36:08Z

Example

← Older revision		Revision as of 14:36, 20 May 2026
Line 31:		Line 31:
	} ]		} ]
	</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_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</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, 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>

Frank@tygron.nl at 13:25, 20 May 2026

2026-05-20T13:25:07Z

← Older revision		Revision as of 13:25, 20 May 2026
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 ''Search Polygon'' of the TQL statement. Items are only included if they are overlapped by the ''Search 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.		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.

Frank@tygron.nl at 13:24, 20 May 2026

2026-05-20T13:24:44Z

← Older revision		Revision as of 13:24, 20 May 2026
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''. 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.

			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==

Frank@tygron.nl: /* Clause Parameters */

2026-05-20T13:11:22Z

Clause Parameters

← Older revision		Revision as of 13:11, 20 May 2026
Line 46:		Line 46:
	*[[Net load (TQL Param)]]		*[[Net load (TQL Param)]]
	*[[Net line (TQL Param)]]		*[[Net line (TQL Param)]]
			</div>

	{{article end		{{article end

Frank@tygron.nl: /* Clause Parameters */

2026-05-20T13:11:10Z

Clause Parameters

← Older revision		Revision as of 13:11, 20 May 2026
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)]]

	{{article end		{{article end

Frank@tygron.nl: /* Clause Parameters */

2026-05-19T13:00:10Z

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)]]

Frank@tygron.nl: /* Example */

2026-05-19T11:49:55Z

Example

← Older revision		Revision as of 11:49, 19 May 2026
Line 4:		Line 4:
	[[File:xa_example_neigbhorhoods.png\|thumb\|right\|[[Neighborhood]]s in an example project]][[File:xa_example_areas.png\|thumb\|right\|[[Area]]s in an example project]]		[[File:xa_example_neigbhorhoods.png\|thumb\|right\|[[Neighborhood]]s in an example project]][[File:xa_example_areas.png\|thumb\|right\|[[Area]]s in an example project]]
	Consider the following (simplified) [[Neighborhood]] data of a project:		Consider the following (simplified) [[Neighborhood]] data of a project:
	<~~syntaxhighlight copy~~>		<pre>
	[ {		[ {
	"id" : 0, "name" : "East Side",		"id" : 0, "name" : "East Side",
Line 12:		Line 12:
	"polygons" : { "type" : "MultiPolygon", "coordinates" : [ [ [ [ 0.0, -500.0 ], [ 250.0, -500.0 ], [ 250.0, 0.0 ], [ 0.0, 0.0 ], [ 0.0, -500.0 ] ] ] ] }		"polygons" : { "type" : "MultiPolygon", "coordinates" : [ [ [ [ 0.0, -500.0 ], [ 250.0, -500.0 ], [ 250.0, 0.0 ], [ 0.0, 0.0 ], [ 0.0, -500.0 ] ] ] ] }
	} ]		} ]
	</~~syntaxhighlight~~>		</pre>
	and the [[Area]] data:		and the [[Area]] data:
	<~~syntaxhighlight copy~~>		<pre>
	[ {		[ {
	"id" : 0, "name" : "Upper Left",		"id" : 0, "name" : "Upper Left",
Line 28:		Line 28:
	"polygons" : { "type" : "MultiPolygon", "coordinates" : [ [ [ [ 315.0, -395.0 ], [ 325.0, -395.0 ], [ 325.0, -385.0 ], [ 315.0, -385.0 ], [ 315.0, -395.0 ] ] ] ] }		"polygons" : { "type" : "MultiPolygon", "coordinates" : [ [ [ [ 315.0, -395.0 ], [ 325.0, -395.0 ], [ 325.0, -385.0 ], [ 315.0, -385.0 ], [ 315.0, -395.0 ] ] ] ] }
	} ]		} ]
	</~~syntaxhighlight~~>		</pre>

	The TQL statement		The TQL statement

Frank@tygron.nl at 09:58, 19 May 2026

2026-05-19T09:58:48Z

← Older revision		Revision as of 09:58, 19 May 2026
Line 2:		Line 2:

	==Example==		==Example==
	[[File:xa_example_neigbhorhoods\|thumb\|right\|[[Neighborhood]]s in an example project]][[File:xa_example_areas\|thumb\|right\|[[Area]]s in an example project]]		[[File:xa_example_neigbhorhoods.png\|thumb\|right\|[[Neighborhood]]s in an example project]][[File:xa_example_areas.png\|thumb\|right\|[[Area]]s in an example project]]
	Consider the following (simplified) [[Neighborhood]] data of a project:		Consider the following (simplified) [[Neighborhood]] data of a project:
	<syntaxhighlight copy>		<syntaxhighlight copy>