TQL Examples - Revision history

Maxim@tygron.com at 14:43, 4 March 2026

2026-03-04T14:43:27Z

← Older revision		Revision as of 14:43, 4 March 2026
Line 54:		Line 54:
	Green buildings can be found by their green [[function value]]. The value is the amount of green in square meters, per square meter of building. Green can be in a neighborhood, but can also be within a certain range near a neighborhood (say, 20 meters) and still have an effective presence.		Green buildings can be found by their green [[function value]]. The value is the amount of green in square meters, per square meter of building. Green can be in a neighborhood, but can also be within a certain range near a neighborhood (say, 20 meters) and still have an effective presence.

	<code>SELECT_LOTSIZE_WHERE_NEIGHBORHOOD_IS_1_AND_BUFFER_IS_20.~~0_AND_FUNCTIONMULT_IS_GREEN_M2~~</code>		<code>SELECT_LOTSIZE_WHERE_NEIGHBORHOOD_IS_1_AND_BUFFER_IS_20.0_AND_FUNCTIONMULT_IS_VEGETATION_FRACTION</code>

	* <code>SELECT_LOTSIZE</code>: The end result must be area taken up by buildings; some amount in square meters.		* <code>SELECT_LOTSIZE</code>: The end result must be area taken up by buildings; some amount in square meters.
	* <code>NEIGHBORHOOD_IS_1</code>: We want the greenery in a particular neighborhood.		* <code>NEIGHBORHOOD_IS_1</code>: We want the greenery in a particular neighborhood.
	* <code>BUFFER_IS_20.0</code>: We don't just want to look at buildings in the neighborhood itself, but also buildings within 20 meters of the neighborhood		* <code>BUFFER_IS_20.0</code>: We don't just want to look at buildings in the neighborhood itself, but also buildings within 20 meters of the neighborhood
	* <code>~~FUNCTIONMULT_IS_GREEN_M2~~</code>:The end result must be multiplied by the green value of the respective buildings found.		* <code>FUNCTIONMULT_IS_VEGETATION_FRACTION</code>:The end result must be multiplied by the green value of the respective buildings found.

	{{Article end		{{Article end

Rudolf@tygron.nl at 10:09, 24 April 2023

2023-04-24T10:09:53Z

← Older revision		Revision as of 10:09, 24 April 2023
Line 63:		Line 63:
	{{Article end		{{Article end
	\|seealso=		\|seealso=
	* TQL		* [[TQL]]
	* Select (TQL)		* [[Select (TQL)]]
	* Update (TQL)		* [[Update (TQL)]]
	}}		}}

	{{TQL nav}}		{{TQL nav}}

Frank@tygron.nl at 13:25, 28 February 2023

2023-02-28T13:25:45Z

← Older revision		Revision as of 13:25, 28 February 2023
Line 68:		Line 68:
	}}		}}

	{{~~tql~~ nav}}		{{TQL nav}}

Frank@tygron.nl at 13:25, 28 February 2023

2023-02-28T13:25:36Z

← Older revision		Revision as of 13:25, 28 February 2023
Line 60:		Line 60:
	* <code>BUFFER_IS_20.0</code>: We don't just want to look at buildings in the neighborhood itself, but also buildings within 20 meters of the neighborhood		* <code>BUFFER_IS_20.0</code>: We don't just want to look at buildings in the neighborhood itself, but also buildings within 20 meters of the neighborhood
	* <code>FUNCTIONMULT_IS_GREEN_M2</code>:The end result must be multiplied by the green value of the respective buildings found.		* <code>FUNCTIONMULT_IS_GREEN_M2</code>:The end result must be multiplied by the green value of the respective buildings found.

			{{Article end
			\|seealso=
			* TQL
			* Select (TQL)
			* Update (TQL)
			}}

			{{tql nav}}

Frank@tygron.nl: /* Examples for common use-cases */

2023-02-28T13:24:55Z

Examples for common use-cases

← Older revision		Revision as of 13:24, 28 February 2023
Line 1:		Line 1:
	~~==Examples for common use-cases==~~

	A number of use-cases come up frequently across various projects. Queries of the following forms often provide a firm basis for using TQL to obtain required data.		A number of use-cases come up frequently across various projects. Queries of the following forms often provide a firm basis for using TQL to obtain required data.

Frank@tygron.nl: Created page with "==Examples for common use-cases== A number of use-cases come up frequently across various projects. Queries of the following forms often provide a firm basis for using TQL to obtain required data. ====Function values (selecting)==== '''Parking requirements of social housing''' The parking demand is based on a function value of each function, and is defined as "parking places per m2". Parking demand is not based on the footprint of a building, but..."

2023-02-28T13:24:46Z

Created page with "==Examples for common use-cases== A number of use-cases come up frequently across various projects. Queries of the following forms often provide a firm basis for using TQL to obtain required data. ====Function values (selecting)==== '''Parking requirements of social housing''' The parking demand is based on a function value of each function, and is defined as "parking places per m2". Parking demand is not based on the footprint of a building, but..."

New page

==Examples for common use-cases==

A number of use-cases come up frequently across various projects. Queries of the following forms often provide a firm basis for using TQL to obtain required data.

====Function values (selecting)====
'''Parking requirements of social housing'''

The parking demand is based on a [[function values | function value]] of each function, and is defined as "parking places per m2". Parking demand is not based on the footprint of a building, but the size of a building. i.e. a building 4 floors high needs more parking than a building with the same footprint 2 floors high.

<code>SELECT_FLOORSIZE_WHERE_CATEGORY_IS_SOCIAL_AND_CATEGORYMULT_IS_PARKING_LOTS_DEMAND_PER_M2</code>

* <code>SELECT_FLOORSIZE</code>: What we are basically looking for is the floorsize of the building.
* <code>CATEGORY_IS_SOCIAL</code>: We only want to look at buildings which are of the [[Function Category|category]] social housing. For that, a category clause is added.
* <code>CATEGORYMULT_IS_PARKING_LOTS_DEMAND_PER_M2</code>: Lastly, we are not looking directly for the floorsize, but for the parking demand as a result of that floorsize.

====Function values (updating)====
'''Traffic intensity on roads'''

The traffic intensity is a function value which affects calculations related to [[Traffic Model|traffic]]. Some use-cases require these values to be updated dynamically. This can be done per neighborhood. (In this example, the [[neighborhood]] in question has the ID 1.)

<code>UPDATE_BUILDING_TRAFFIC_FLOW_WHERE_CATEGORY_IS_ROAD_AND_NEIGHBORHOOD_IS_1</code>

* <code>UPDATE_BUILDING</code>: We're changing an attribute of a building.
* <code>TRAFFIC_FLOW</code>: The attribute we are changing is the TRAFFIC_FLOW, which is the technical name of a function value.
* <code>CATEGORY_IS_ROAD</code>: We only want to update this value on roads.
* <code>NEIGHBORHOOD_IS_1</code>: We are updating only in this specific neighborhood. Nothing outside the neighborhood is updated by this statement.

====Grid average====
'''Quality of livability in a neighborhood'''

The [[livability (Overlay)|livability overlay]] calculates, for each [[grid overlay|grid cell]], the average livability. The best indication of how well a certain region performs in terms of livability would be to average these values out. That way, its possible to compare places which are not the same size. (In this example, the [[neighborhood]] in question has the ID 1, and the [[grid overlay|grid]] of [[livability (Overlay)|livability]] has the ID 4.)

<code>SELECT_GRIDAVG_WHERE_NEIGHBORHOOD_IS_1_AND_GRID_IS_4</code>

For any given neighborhood, different points of a [[grid overlay|grid]] may score differently.

* <code>SELECT_GRIDAVG</code>: We're looking for the average score across the entire neighborhood.
* <code>NEIGHBORHOOD_IS_1</code>: We don't need the average of the entire map, but only of a specific neighborhood.
* <code>GRID_IS_4</code>: We need to specify the grid we wish to use the values of.

====Grid values====
'''The area of open water which is flooded by more than 20 cm of water'''

The [[Rainfall (Overlay)|rainfall overlay]] calculates what amounts of water ends up where. The overlay's results are in meters. If we wish to provide some minimum value, it must be in meters as well. 20 cm is 0,2 meters. The [[project]] can also contain multiple types of [[terrain|water]]. All types of have one thing in common, namely that they all have the WATER attribute, which can be tested against. (In this example, the grid of [[Rainfall (Overlay)|inundation]] has the ID 4, and has its result type set to water stress.)

<code>SELECT_LANDSIZE_WHERE_MINGRIDVALUE_IS_0.2_AND_GRID_IS_4_AND_TERRAIN_WITH_ATTRIBUTE_IS_WATER</code>

* <code>SELECT_LANDSIZE</code>: The end result must be some area; some amount of square meters.
* <code>MINGRIDVALUE_IS_0.2</code>: We only want to count the area where the value calculated is at least 0.2 (meters).
* <code>GRID_IS_4</code>: We need to specify the grid we wish to use the values of.
* <code>TERRAIN_WITH_ATTRIBUTE_IS_WATER</code>: We are only looking for the water which ends up on [[terrain|water]], identified by the "WATER" attribute.

====Buffers====
'''The amount of green in or near a neighborhood'''

Green buildings can be found by their green [[function value]]. The value is the amount of green in square meters, per square meter of building. Green can be in a neighborhood, but can also be within a certain range near a neighborhood (say, 20 meters) and still have an effective presence.

<code>SELECT_LOTSIZE_WHERE_NEIGHBORHOOD_IS_1_AND_BUFFER_IS_20.0_AND_FUNCTIONMULT_IS_GREEN_M2</code>

* <code>SELECT_LOTSIZE</code>: The end result must be area taken up by buildings; some amount in square meters.
* <code>NEIGHBORHOOD_IS_1</code>: We want the greenery in a particular neighborhood.
* <code>BUFFER_IS_20.0</code>: We don't just want to look at buildings in the neighborhood itself, but also buildings within 20 meters of the neighborhood
* <code>FUNCTIONMULT_IS_GREEN_M2</code>:The end result must be multiplied by the green value of the respective buildings found.