Because there may be more address points in an area than are practically useful, you can reduce the number of plotted address points by specifying an SQL WHERE clause to limit the points displayed. The database columns available are:
| SQL column name | contents of column | OSM tags |
|---|---|---|
| isway | 1 for OSM Way, 0 for OSM Node. | - |
| id | ID number of Way or Node a negative ID indicates a Relation converted into a Way, or an extremely tiny Way converted into a Node. | id attribute of Node, Way, or Relation |
| latitude | Millionths of degrees North latitude. | latitude attribute of Node, centroid latitude of Way |
| longitude | Millionths of degrees East longitude | longitude attribute of Node, centroid longitude of Way |
| housenumber | Postal building number or building name for countries that use that, e.g. "Government House". | addr:housenumber addr:housename |
| street | Localized name of the street the address is located on. | addr:street addr:place |
| city | Localized name of the city, town, or village the address is located in. Depending on local post office conventions, this may be the name of a town next to a rural address. | addr:city addr:town addr:village |
| state | Localized name of the state or province of the country. This may be a country-specific abbreviation (e.g., "PA" for the United States' state of Pennsylvania. | addr:state addr:province ISO3166-2 |
| postcode | Country-specific postal service routing code (such as the United States' zipcode). | addr:postcode |
| country | ISO-3166 2-character country code. | addr:country ISO3166-2 |
For example, if you were on a non-straight-line part of the border between the United States and Canada,
you could specify the clause
COUNTRY = 'US'
to only get address points on the US side of the border (of course, this is applicable for any
country-to-country border).
If the SQL WHERE clause syntax you provide is invalid, you will not see any address points, as the search will fail with the syntax error before any records are looked up. Errors will be logged in the YAAC.out log file, which can be seen on the "Error Log" tab of the Help->About dialog, or accessed directly in your configured log file directory.