2010 DMTI Spatial Inc.
Page 81
Defining Input Specifications
(cont’d)
Specifying Address Data Fields
Page 81
Geocoding an Unparsed Address
An unparsed address represents data that may contain relevant components of a street address, which may include a street number, an apartment or a suite number, street name, street type, and a street direction. This information is concatenated and stored in one column (e.g.: geoaddress)
GeoPinpoint Suite can geocode the following kinds of unparsed information:
Unparsed address
Unparsed intersection
Unparsed POI
Unparsed Postal code
Unparsed Segment (segment centroid, street segment)
Unparsed FSA
Unparsed PPN
Unparsed Muni centroid
Note: Refer to the above geocoding function sections (address, POI, etc for examples of each of
these records)
DMTI Spatial Inc. 15 Allstate Parkway, Suite 400, Markham, Ontario, Canada, L3R 5B4 www.dmtispatial.com
2010 DMTI Spatial Inc.
Page 82
Defining Input Specifications
(cont’d)
Looking at the above snapshot of GeoPinpoint Suite
– Input Specifications, geocoding unparsed address information requires the use of the following fields:
Unparsed address
Municipality
*
Province
Postal Code
*
*
*
The Municipality value must be populated when using a function which geocodes <By Municipality>.
The Postal Code value must be populated when using a function which geocodes <By FSA>.
Page 82
DMTI Spatial Inc. 15 Allstate Parkway, Suite 400, Markham, Ontario, Canada, L3R 5B4 www.dmtispatial.com
2010 DMTI Spatial Inc.
Page 83
Defining Input Specifications
(cont’d)
Unparsed Address: This heading represents data that may contain relevant components of a street address, which may include a street number, an apartment or a suite number, street prefix, street name, street type, and a street direction. This field must be represented as a text field in the target database table and currently handles only Canadian data. There is no restriction on the size of the text field.
If the address cannot match to the geo-reference database, it is possible that a component of the address is incorrect
Possible problems with unparsed address values
Address Component
Street Number
Possible problems
Problem:
Address number does not exist in the range stored in the geo-reference database for that particular street
Solution:
Use Relax/Address functions on Input Specifications tab:
Closest Address Tolerance
Opposite Side of Street
Refer to Input Specifications section to learn more information on how to use these functions.
Street Prefix
Street Name
Problem:
Street prefix is missing or is incorrect for the respective street
Solution:
Use Relax/Address functions on Input Specifications tab
Relax Matching on Street Prefix
Problem:
Street name is not spelled correctly or is incorrect
Solution:
If record does not geocode:
Examine record inside the table and verify correctness
Use Geocode to Street Alias function
– this street may have a street alias or be known by a former name
Street Type
Street Direction
Refer to Input Specifications section to learn more information on how to use these functions.
Problem:
Street type is missing or is incorrect for the respective street
Solution:
Use Relax/Address functions on Input Specifications tab
Relax Matching on Street Type
Problem:
Street direction is missing or is incorrect for the respective street
Solution:
Use Relax/Address functions on Input Specifications tab
Relax Matching on Street Direction
Note: GeoPinpoint Suite currently does not match apartment or suite numbers to the geo-reference
database.
DMTI Spatial Inc. 15 Allstate Parkway, Suite 400, Markham, Ontario, Canada, L3R 5B4 www.dmtispatial.com
Page 83
2010 DMTI Spatial Inc.
Page 84
Defining Input Specifications
(cont’d)
Municipality: This heading represents a municipality field (city, town, village) in order to refine geocoding.
This field must be represented as a text field in the target database table and currently handles only
Canadian data. There is no restriction on the size of the text field. This column must be populated when using a geocoder function <By Municipality>.
Possible problems with municipality values
Address Component
Municipality
Possible problems
Problem:
Missing or incorrect municipality value
Solution:
If the data is not present in the target database table it may be derived from postal code information using the Lookup Municipality
via Postal code option located on the General Geocoding Options tab.
Check spelling of municipality value.
Problem:
French municipality name is translated into English.
Solution:
The geo-reference database only stores municipality values as they appear in data sources. Therefore, English equivalent values to
French municipality values are not stored or used within GeoPinpoint
Suite.
Province: This heading represents a provincial field in order to refine geocoding. This field must be represented as a text field in the target database table and currently handles only Canadian data. There is no restriction on the size of the text field. This field must be populated with the correct province value because address information could be the same between provinces.
If the records within a database fall within one province, the user can utilize the Use Constant for
Province option located on the General Geocoding Options tab and input the single value of the province.
The following represents acceptable values that can be populated within the province column:
Abbreviation Full Province/Territory Name
Abbreviation Full Province/Territory Name
AB Alberta
BC
MB
NB
NL / NF
British Columbia
Manitoba
New Brunswick
Newfoundland and Labrador
NU
ON
PE
QC / PQ
SK
Nunavut
Ontario
Prince Edward Island
Quebec
Saskatchewan
NS Nova Scotia YT Yukon Territory
NT Northwest Territories
Postal Code: This heading represents a postal code field. Postal Codes may be comprised of either 6digit or 7digit string i.e.”N0N 1H0” or ”N0N1H0”. This field must be represented as a text field in the target database table and currently handles only Canadian data. There is no restriction on the size of the text field. This column must be populated when using a geocoder function <By FSA>.
Note:
The GeoPinpoint Suite also has enhanced functionality, which recognizes when a “O” is being used incorrectly when a “0” (zero) is required. GeoPinpoint Suite will still be able to geocode
these kinds of postal code records.
DMTI Spatial Inc. 15 Allstate Parkway, Suite 400, Markham, Ontario, Canada, L3R 5B4 www.dmtispatial.com
Page 84
