X query (Excel) - Revision history

Maxim@tygron.com: /* Multi X queries */

2026-06-16T08:39:00Z

Multi X queries

← Older revision		Revision as of 08:39, 16 June 2026
Line 83:		Line 83:
	{{clear}}		{{clear}}

	===Multi X queries===		===Multi X queries (not recommended)===
	[[File:XXquery.jpg\|thumb\|right\|x150px\|The generated queries go through all Areas for one Neighborhood first, then for the next Neighborhood, until all combinations have been made. The output is the amount of overlap between each combination of specific Neighborhood and specific Area.]]		[[File:XXquery.jpg\|thumb\|right\|x150px\|The generated queries go through all Areas for one Neighborhood first, then for the next Neighborhood, until all combinations have been made. The output is the amount of overlap between each combination of specific Neighborhood and specific Area.]]
	It is possible to have multiple clauses with an X (multiple queries with a Y) in the same query. In these situations, both X's are expanded in the same direction. Both (or all) clauses resolves to their first applicable ID. For the next generated query, only one of the generated queries resolves to the next ID, while the other(s) remain set to their first ID. This continues until the all applicable IDs of that clause have been used. Then, the other clause's ID is advanced by one, and the first clause starts at its first ID again, progressing until all its applicable IDs are exhausted.		It is possible to have multiple clauses with an X (multiple queries with a Y) in the same query. In these situations, both X's are expanded in the same direction. Both (or all) clauses resolves to their first applicable ID. For the next generated query, only one of the generated queries resolves to the next ID, while the other(s) remain set to their first ID. This continues until the all applicable IDs of that clause have been used. Then, the other clause's ID is advanced by one, and the first clause starts at its first ID again, progressing until all its applicable IDs are exhausted.

Frank@tygron.nl: /* XC queries */

2026-05-20T14:29:25Z

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

Frank@tygron.nl: /* XA queries */

2026-05-15T13:11:34Z

XA queries

← Older revision		Revision as of 13:11, 15 May 2026
Line 94:		Line 94:
	The X syntax can be expanded to be more selective on which [[Item]]s to generate queries for, using the XA syntax. For example, rather than generating queries for all [[Area]]s in a [[Project]], which may all serve a wildly different purpose, it is possible to retrieve only the [[Area]]s with a specific [[Attribute]].		The X syntax can be expanded to be more selective on which [[Item]]s to generate queries for, using the XA syntax. For example, rather than generating queries for all [[Area]]s in a [[Project]], which may all serve a wildly different purpose, it is possible to retrieve only the [[Area]]s with a specific [[Attribute]].

	A query which would retrieve the names only of [[Area]]s which have a [[Sewer storage (Water Overlay)\|~~SEWER_STOARGE~~]] [[Attribute]], marking them as [[Sewer area (Water Overlay)\|Sewer Area]]s for use with the [[Water Overlay]], could be constructed as follows:		A query which would retrieve the names only of [[Area]]s which have a [[Sewer storage (Water Overlay)\|SEWER_STORAGE]] [[Attribute]], marking them as [[Sewer area (Water Overlay)\|Sewer Area]]s for use with the [[Water Overlay]], could be constructed as follows:

	<code>SELECT_NAME_WHERE_AREA_IS_XA_SEWER_STORAGE</code>		<code>SELECT_NAME_WHERE_AREA_IS_XA_SEWER_STORAGE</code>

Frank@tygron.nl: /* XA queries */

2026-05-15T12:54:22Z

XA queries

← Older revision		Revision as of 12:54, 15 May 2026
Line 103:		Line 103:
	The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query after the item that is being queried (Building in our case).		The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query after the item that is being queried (Building in our case).

	<code>~~SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304~~</code>		<code>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304_AND_KEY_IS_WEIR_HEIGHT</code>

	====SORTed queries====		====SORTed queries====

Frank@tygron.nl: /* XK queries */

2026-05-15T09:58:02Z

XK queries

← Older revision		Revision as of 09:58, 15 May 2026
Line 103:		Line 103:
	The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query after the item that is being queried (Building in our case).		The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query after the item that is being queried (Building in our case).

	<code>~~SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304_AND_KEY_IS_WEIR_HEIGHT~~</code>		<code>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304</code>

	====SORTed queries====		====SORTed queries====

Maxim@tygron.com: /* SORTed queries */

2025-11-28T14:04:32Z

SORTed queries

← Older revision		Revision as of 14:04, 28 November 2025
Line 106:		Line 106:

	====SORTed queries====		====SORTed queries====
	Expanding on the XA syntax, it is also possible to sort the resulting [[Area]]s by the value of a specific attribute. This attribute may or may not be the same attribute as indicated in the first part of the XA syntax. For example:		Expanding on the XA and XK syntax, it is also possible to sort the resulting [[Area]]s by the value of a specific attribute. This attribute may or may not be the same attribute as indicated in the first part of the XA syntax. For example:

	<code>SELECT_NAME_WHERE_AREA_IS_XA_SEWER_STORAGE_SORT_SEWER_PUMP_SPEED</code>		<code>SELECT_NAME_WHERE_AREA_IS_XA_SEWER_STORAGE_SORT_SEWER_PUMP_SPEED</code>

Maxim@tygron.com: /* XK queries */

2025-11-28T14:02:59Z

XK queries

← Older revision		Revision as of 14:02, 28 November 2025
Line 100:		Line 100:
	This will generate only queries for [[Area]]s which have an [[Attribute]] SEWER_STORAGE, in which "XA_SEWER_STORAGE" is in its entirety replaced by the relevant [[Area]]'s [[ID]]. [[ID]]s of [[Area]]s which do not have the specified [[Attribute]], or of which the [[Attribute]]'s value is 0, are skipped in the same way that the [[ID]]s of deleted [[Item]]s are skipped.		This will generate only queries for [[Area]]s which have an [[Attribute]] SEWER_STORAGE, in which "XA_SEWER_STORAGE" is in its entirety replaced by the relevant [[Area]]'s [[ID]]. [[ID]]s of [[Area]]s which do not have the specified [[Attribute]], or of which the [[Attribute]]'s value is 0, are skipped in the same way that the [[ID]]s of deleted [[Item]]s are skipped.

	===XK queries===		====XK queries====
	The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query after the item that is being queried (Building in our case).		The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query after the item that is being queried (Building in our case).

Maxim@tygron.com: /* XK queries */

2025-11-28T14:02:32Z

XK queries

← Older revision		Revision as of 14:02, 28 November 2025
Line 101:		Line 101:

	===XK queries===		===XK queries===
	The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query.		The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query after the item that is being queried (Building in our case).

	<code>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304_AND_KEY_IS_WEIR_HEIGHT</code>		<code>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304_AND_KEY_IS_WEIR_HEIGHT</code>

Maxim@tygron.com: /* XK queries */

2025-11-28T14:01:28Z

XK queries

← Older revision		Revision as of 14:01, 28 November 2025
Line 101:		Line 101:

	===XK queries===		===XK queries===
	The XK Query is an extension to the XA query that resolves the attribute name used in XA via a Key value defined in an Grid Overlay. For example the Water Overlay key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query.		The XK Query is an extension to the XA query that resolves the attribute name used in XA via a [[Overlay Key]] value defined in an Grid Overlay. For example the [[Water Overlay]] key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query.

	<code>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304_AND_KEY_IS_WEIR_HEIGHT</code>		<code>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304_AND_KEY_IS_WEIR_HEIGHT</code>

Maxim@tygron.com: /* XA queries */

2025-11-28T14:00:02Z

XA queries

← Older revision		Revision as of 14:00, 28 November 2025
Line 99:		Line 99:

	This will generate only queries for [[Area]]s which have an [[Attribute]] SEWER_STORAGE, in which "XA_SEWER_STORAGE" is in its entirety replaced by the relevant [[Area]]'s [[ID]]. [[ID]]s of [[Area]]s which do not have the specified [[Attribute]], or of which the [[Attribute]]'s value is 0, are skipped in the same way that the [[ID]]s of deleted [[Item]]s are skipped.		This will generate only queries for [[Area]]s which have an [[Attribute]] SEWER_STORAGE, in which "XA_SEWER_STORAGE" is in its entirety replaced by the relevant [[Area]]'s [[ID]]. [[ID]]s of [[Area]]s which do not have the specified [[Attribute]], or of which the [[Attribute]]'s value is 0, are skipped in the same way that the [[ID]]s of deleted [[Item]]s are skipped.

			===XK queries===
			The XK Query is an extension to the XA query that resolves the attribute name used in XA via a Key value defined in an Grid Overlay. For example the Water Overlay key: WEIR_HEIGHT resolves to a custom set attribute "STUW_HOOGTE" can then be executed without prior knowledge that the weir height has this specific attribute name. For this to work you also need to include the specific overlay in the query.

			<code>SELECT_ATTRIBUTE_WHERE_BUILDING_IS_XK_WEIR_HEIGHT_AND_GRID_IS_304_AND_KEY_IS_WEIR_HEIGHT</code>

	====SORTed queries====		====SORTed queries====