Examples of filters 2

Different operators are available for each attribute. Some examples:

Filter rule	Explanation
Project name = Station	Finds attributes exactly matching this string: Station Uppercase and lowercase letters are taken into account.
Project name like station	Finds attributes exactly matching this string: station Uppercase and lowercase letters are ignored.
Project name = *station	Finds attributes that end with the term "station" (south_station, central_station) Uppercase and lowercase letters are always ignored if the string contains an asterisk (*).
Project name = station	Finds attributes that contain the term "station" (south_station_platform, central_station_terminal)
Project name <> ...	Identical to "="; the only difference is that only attributes whose occurrence is not equal are displayed.
Project name > P	Finds attributes whose occurrence comes after the capital letter P in the alphabet: for example, all projects from R on such as Riga, Southern Wales.
Project name >= R AND project name < S	Finds attributes that start with the capital letter R.

Many custom project attributes contain numerical values. The system checks whether the value entered is a numerical expression and if so, it applies numerical criteria. Example: Numerical construction volume >= 1000 finds 1000.0 but 1ABC is not found.

Filter rule	Explanation
Construction volume >= 1000	Numerical query; all numerical occurrences whose integers are greater than or equal to 1000.
Construction volume >= 1000.5	Numerical query; all numerical occurrences whose floating point numbers are greater than or equal to 1000.5.
Applies to the "=" and "<>" operators accordingly.
Construction volume like 1000	"like" is always used alphabetically; never numerically. This condition finds attributes that match the string 1000.

Description = "1000"	You can force the system to look for a numerical value alphabetically by enclosing the string in brackets ("). This condition finds attributes whose occurrence is exactly 1000 (and not 1000.0).

Note: If an attribute does not exist, it cannot be found. This also applies to the "<>" operator: description <> museum, for example, only finds projects containing the description attribute that is not equal to museum.