The proportion or ratio between a map measurement and the corresponding measurement in the real world. Map scale is usually expressed as a ratio, such as 1:50,000, which means that a measurement of one unit on the map represents 50,000 units on earth.
Segment Range Geocoder
Takes the input as address information, uses the Postal Code to look up its geographic location in the form of longitude and latitude from the Postal Code point source database in the Georef, or it will use the address information to look up the centre point of the corresponding street segment from street segments based on the source database in Georef.
Site & Lot Numbers
These pieces of information are recognized and removed by GeoPinpoint Suite.
Six-digit postal code coordinates
The Six Digit Postal Code File is based on the Unique Enhanced Postal Code File, but does not contain the link to Statistics Canada’s standard census geographic areas. This file contains the postal code, longitude and latitude of each point, 1996 Census population and dwelling counts and the birth date and retire date of each postal code.
Snapping
An automatic editing operation in which points or features within a specified distance or tolerance of other points or features are moved to match or coincide exactly with each other's coordinates.
(Source: ArcGIS dictionary)
Soundex
The Soundex module for GeoPinpoint Suite Windows/ActiveX is a new function for beta release clients. This module is an algorithm which uses fuzzy logic to help geocode POI names which suffer from spelling variations, abbreviations, difference in case and/or are incomplete.
The proposed methodology for using Soundex is to geocode the records in the database with the POIgeocoder first, and then turn on Soundex functionality to try and match more records in the second pass.
Currently the Soundex module for GeoPinpoint Suite will perform the following:
Help geocode to POI names
Match one or multiple POI names simultaneously
Examples of Soundex:
Original word
Input word
Output word
Toronto City Hall
Toronto City Hall
Toronto City Hall
Toronto City Hall
City Hall of Toronto
Toronto City Hall
Toronto City Hall
Holl of Sity Toronto
Toronto City Hall
Konberg
Comperg
Konberg
Future releases of the Soundex Module for GeoPinpoint Suite will include:
Ability to match to street names
Set thresholds for Soundex matching
Include the Soundex score as part of the output
Spaghetti data
Vector data composed of simple lines with no topology, and usually no attributes. Spaghetti lines may overlap, but there are no relationships between the features.
(Source: ArcGIS dictionary)
Spatial database
A collection of spatial data and its related descriptive data, organized for efficient storage and retrieval.
(Source: ArcGIS dictionary)
Spatial join
A type of table join operation in which fields from one layer's attribute table are appended to another layer's attribute table based on the relative locations of the features in the two layers.
(Source - ArcGIS dictionary)
Spatial query
A statement or logical expression that selects geographic features based on location or spatial relationship. For example, a spatial query might find which points are contained within a polygon or set of polygons, find features within a specified distance of a feature, or find features that are adjacent to each other.
(Source - ArcGIS dictionary)
Street Alias
This option allows GeoPinpoint Suite to search the geo-reference database for alternative street names for streets that have more than one correct identifying name. For example, a road may be known as Broadway Avenue, and Highway 9. While the name Broadway Avenue may be in the geo-reference database street field, the target database table may have a record with the address on Highway 9. By selecting this option, GeoPinpoint Suite is able to make a match by finding Highway 9 in the geo-reference database Street Alias field.
Note: The Geocode to Street Alias option now includes the previously separate option Geocode to
Former Street Name. When GeoPinpoint Suite now searches the Street Alias field in the geo
-reference database, it will also search the Former Street Name field. (Former street names
are only relevant to Ontario, since many Ontario roads have changed name in recent years as a
result of infrastructure reallocation. E.g. Highway 7 in the G.T.A. is now Regional Rd 7.)
Street Direction
This heading represents a field containing geographical directions. The sample address does not contain a street direction, but an example could be N, which would indicate North. For a list of valid street direction entries, see Appendix 5.
Recognizing this is based on a direction alias table. (For a list of valid street directions, see Appendix 5.) Parsing identifies the position of a street direction within an address.
Street Level Detail
The geo-reference database used by GeoPinpoint Suite to geocode all Canadian data is based on the CanMap® streetfile. The CanMap® streetfile includes street centerlines and address ranges, and it is updated by DMTI Spatial on an ongoing basis. CanMap® contains street naming for communities down to, and in some cases, under 1,000 population and street addressing for communities down to, and in some cases, under 2,000 population.
Street Name
This heading represents the field in the target database table for the name of the street. In the sample address the field for street name would contain Laurier, or Des Laurier if there were no street prefix field.
It can be alphabetic, alphanumeric, or numeric or a set of such words. E.g. Highway 7, 10A Rd, 9th Line, Bloor St
Street Number
The Street Number heading requires a field containing numeric data, stored as a long integer, while all other headings require fields containing text data.
This heading represents a field that contains only the house/building number portion of the total address. The field should contain the number 100 from the sample address. This field must be formatted as a long integer.
It can be numeric or alphanumeric. Parsing removes alphabetic portion if it is alphanumeric. E.g. 9B 10th Line would become 9 10th Line
Street Prefix
This heading represents a field that contains words that add description to the street name, but are not a part of the street name themselves. For example, the words Des, De La, De L’, and The often proceed the actual street name. In the sample address, Des could be located in a separate field in the table to be geocoded. This field is an optional parsed field; the data could alternatively be included as part of the Street Name field.
Street Prefix Type & Street Suffix Type
This heading is used if the user’s database has 2 street type fields. To access both drop down lists, the user must select the Use Street Prefix and Suffix Type option located on the General Geocoding Options tab. This allows the user to geocode tables that have two separate street type fields. I.e. A table that has both Prefix Types (usually preceding the street name) and Suffix Types (usually following the street name).
If the user is geocoding a table with parsed data that contains two street type fields (a street prefix type and a street suffix type), enabling this option allows the user to input their two street type fields into GeoPinpoint Suite. This option eliminates the user’s need of taking their two existing street type fields and combining them into one.
Street Segment Data Model
A data model based on the geographic information of a street (series of segments). Geocoding using the street segment data model means that the address level geocoding results are all interpolated as opposed a sourced address point.
Street Type
Recognizing this is based on a street type alias table. (For a list of valid street types, see Appendix 5.) Parsing identifies the position of a street type within an address.
Suite Number
This heading represents a field that contains a number, a letter, or a combination of both that represents an apartment, a suite, or a unit of a building. In the sample address, 201 is the suite number. Although this field may contain only numbers, they must be stored as text data.
Parsing will recognize this at the beginning or ending of the unparsed field. The suite number can be preceded by defined indicators including “#, SUITE, APARTMENT, APT, and UNIT.” E.g. 90A Cordova Ave Unit # 25B, Apt 25B 100 Bloor St