X query (Excel) - Revision history

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

Frank@tygron.nl at 09:59, 1 March 2023

2023-03-01T09:59:56Z

← Older revision		Revision as of 09:59, 1 March 2023
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_STOARGE]] [[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 at 17:43, 27 January 2023

2023-01-27T17:43:00Z

← Older revision		Revision as of 17:43, 27 January 2023
Line 161:		Line 161:
	\|seealso=		\|seealso=
	* [[Excel]]		* [[Excel]]
			* [[TQL]]
	}}		}}

Frank@tygron.nl: /* How X queries are resolved */

2023-01-27T17:42:04Z

How X queries are resolved

← Older revision		Revision as of 17:42, 27 January 2023
Line 42:		Line 42:
	* The originally uploaded [[Excel]] file remains unaltered. This means when it is downloaded, either normally or as a debug file, the generated queries will not be visible.		* The originally uploaded [[Excel]] file remains unaltered. This means when it is downloaded, either normally or as a debug file, the generated queries will not be visible.
	* The queries are ''only'' (re)generated when an Excel file is uploaded/updated, or [[Calculation_panel#Update_Indicators_and_Reset_Excel_X-Queries\|Excel X queries are explicitly reset]]. This means that if additional [[Item]]s are added to a [[Project]] which would match a clause with an X, queries for those [[Item]]s are not automatically (re)generated.		* The queries are ''only'' (re)generated when an Excel file is uploaded/updated, or [[Calculation_panel#Update_Indicators_and_Reset_Excel_X-Queries\|Excel X queries are explicitly reset]]. This means that if additional [[Item]]s are added to a [[Project]] which would match a clause with an X, queries for those [[Item]]s are not automatically (re)generated.
	* In a [[Project]] in which [[Item]]s have been deleted, the [[ID]] of that [[Item]] would no longer make a valid query, and is therefor skipped while generating specific queries. IF this happens in a sequence, e.g. 4 [[Neighborhood]]s with [[ID]]s 0 through 3, of which those with [[ID]] 1 and 2 have been deleted, the first generated query would be for the[[Neighborhood]] with [[ID]] 0, followed directly in the next row by a query for the[[Neighborhood]] with [[ID]] 3.		* In a [[Project]] in which [[Item]]s have been deleted, the [[ID]] of that [[Item]] would no longer make a valid query, and is therefor skipped while generating specific queries. IF this happens in a sequence, e.g. 4 [[Neighborhood]]s with [[ID]]s 0 through 3, of which those with [[ID]] 1 and 2 have been deleted, the first generated query would be for the [[Neighborhood]] with [[ID]] 0, followed directly in the next row by a query for the [[Neighborhood]] with [[ID]] 3.
	* If a query generated from an X query resolves to the exact same query which already exists elsewhere in the [[Excel]], even if that query is also generated, only one of those queries will actually function. The cell where the other would have led to an inserted value will remain empty.		* If a query generated from an X query resolves to the exact same query which already exists elsewhere in the [[Excel]], even if that query is also generated, only one of those queries will actually function. The cell where the other would have led to an inserted value will remain empty.
	* Although X queries tend to serve as a header for an entire column of values; if there are already values in the column, and there are not sufficient queries generated to overwrite them all, then the cells which have a value but do not have a generated query will retain their cell value. They will not be emptied.		* Although X queries tend to serve as a header for an entire column of values; if there are already values in the column, and there are not sufficient queries generated to overwrite them all, then the cells which have a value but do not have a generated query will retain their cell value. They will not be emptied.

Frank@tygron.nl at 17:41, 27 January 2023

2023-01-27T17:41:47Z

← Older revision		Revision as of 17:41, 27 January 2023
Line 158:		Line 158:
	{{article end		{{article end
	\|notes=		\|notes=
	* Because X-queries are processed as an explicit operation in the Editor mode, the exact set of [[Item]]s which are retrieved as a result of an X query will not change after a [[Session\|non-editing Session]] or [[Test Run]] is started. This means that, for example, [[Building]]s added as an [[Action]] ~~to the~~ [[~~3D World~~]] will not be retrieved.		* Because X-queries are processed as an explicit operation in the Editor mode, the exact set of [[Item]]s which are retrieved as a result of an X query will not change after a [[Session\|non-editing Session]] or [[Test Run]] is started. This means that, for example, [[Building]]s added as an [[Action]] during a [[Session\|Single, Multi or Test-run Session]] will not be retrieved.
	\|seealso=		\|seealso=
	* [[Excel]]		* [[Excel]]
	}}		}}

Maxim@tygron.com at 15:33, 7 October 2022

2022-10-07T15:33:02Z

← Older revision		Revision as of 15:33, 7 October 2022
Line 158:		Line 158:
	{{article end		{{article end
	\|notes=		\|notes=
	* Because X-queries are processed as an explicit operation in the Editor mode, the exact set of [[Item]]s which are retrieved as a result of an X query will not change after a [[Session\|non-editing Session]] or [[Test Run]] is started. This means that, for example, [[~~Construction~~]]s added as an [[Action]] to the [[3D World]] will not be retrieved.		* Because X-queries are processed as an explicit operation in the Editor mode, the exact set of [[Item]]s which are retrieved as a result of an X query will not change after a [[Session\|non-editing Session]] or [[Test Run]] is started. This means that, for example, [[Building]]s added as an [[Action]] to the [[3D World]] will not be retrieved.
	\|seealso=		\|seealso=
	* [[Excel]]		* [[Excel]]
	}}		}}