Assign GeoTAX Info Summary Report

A pre-configured report can be generated for a job. This is supported for a job run through either the Assign GeoTAX Info or the Reverse GeoTAX Info Lookup stage. The report summarizes general information about the job, such as the settings, number of records processed, performance statistics, and the database used. It also contains detailed statistics about the results of the job.

The summary report contains the following sections for Assign GeoTAX Info and Reverse GeoTAX Info Lookup except where noted.

Job Summary

This section contains information about the software and databases used for the job.

• Software Version—The version of the underlying software used by AssignGeoTAXInfo. Note that this is not the same as the Spectrum™ Technology Platform version number.
• Input Mode—The type of input data.
  • Address Input— Indicates the data was generated from a job using the AssignGeoTAXInfo stage.
  • Latitude-Longitude Input—Indicates the data was generated from a job using the ReverseGeoTAXInfo Lookup stage.
• Street Database Vendor—The street database vendor used for matching.
• Street Database Version—The version of the Street portion of the Master File database. For information on the Master File, see Enterprise Tax Databases.
• Cross Reference Database Version—The version of the cross-reference database used in this job. Cross-reference databases are used to determine jurisdiction codes for use with third-party tax software. For information on the Cross Reference databases, see Enterprise Tax Databases.

Address Matching Summary

This section describes the input address match counts.

• Total Match Attempts—Address matches attempted in this job.
• Total Records Matched—Input addresses that were matched to known locations.
• Total Unmatched Records—Input addresses that could not be matched to known addresses.

Address Matching Levels

This section lists the counts and percentages of the types of address matches performed by Assign GeoTAX Info.

• User-Defined Auxiliary File Matches—The number of address matches made to the user-defined auxiliary file. For information on a user-defined auxiliary file, see Enterprise Tax Module.
• GeoTAX Auxiliary File Matches—The number of address matches made to the GeoTAX Auxiliary file. For information on the GeoTAX Auxiliary file, see Enterprise Tax Module.
• State File Matches—The number of address matches made to a state-supplied files.
• Landmark Auxiliary Matches—The number of address matches made to the Landmark Auxiliary file.
• Point-Level Matches—The number of address matches made using point-level data.
• Address-Level Matches—The number of addresses matches made to an approximate location on a street segment.
• Street Intersection-Level Matches—The number of address matches made to a street intersection.
• Street-Centroid Level Matches—The number of address matches that were made along the matched street segment.
• ZIP + 4-Level Matches—The number of address matches made to an area defined by a ZIP + 4 Code.
• ZIP-Level Matches—The number of address matches made to an area defined by a 5-digit ZIP Code.
• Fallback Geographic Matches—The number of address matches that were made to a city or state centroid.

Standardized Address Quality

This section describes the changes that were made to addresses in order to validate them.

• Original Address Unchanged—None of the address elements were changed to obtain a match.
• Original Last Unchanged—The last line (city, state, ZIP Code) was unchanged but other elements were changed to obtain a match.
• Corrected state abbreviation—The state abbreviation was corrected to obtain a match. For example, ROCHESTER NY changed to ROCHESTER MN.
• Corrected prefix direction—The predirectional of a street name was changed to obtain a match. For example, E MAIN ST changed to W MAIN ST.
• Corrected street name—The name of the street was changed to obtain a match. For example, MAIN ST changed to MAINE ST.
• Corrected street suffix—The street suffix was changed to obtain a match. For example, MAIN ST changed to MAIN AVE.
• Corrected city name—The name of the city was corrected to obtain a match. For example, LOS ANGLES changed to LOS ANGELES.
• Corrected postfix direction—The postdirectional of a street was changed to obtain a match. For example, MAIN ST NW changed to MAIN ST SW.
• Corrected ZIP code—The ZIP Code as corrected to obtain a match. For example: 1071 MAPLE LN BATAVIA IL 49423 Changed to: 1071 MAPLE LN BATAVIA IL 60510.
• Corrected ZIP + 4 code—The four digits that appear after the "-" in a ZIP + 4 were corrected to obtain a match. For example, 60510 changed to 60510-1135.

Unmatched Address Records

This section lists the number of unmatched addressees and the reasons why the addresses were not matched. For information about these codes, see Match Codes for No Match - Definitions for "Ennn" return codes.

Latitude/Longitude Matching

This section lists the counts and percentages of the types of geocodes determined by Assign GeoTAX Info. This section describes how precisely AssignGeoTAXInfo determined latitude/longitude coordinates of an address. These counts are based on match codes. For more information, on match codes, see Latitude/Longitude.

• Total Lat/Long Matches—Addresses that AssignGeoTAXInfo determined latitude/longitude coordinates. Addresses included in this count have any value other than null in the LatLong.MatchCode output field.
• Total Lat/Long Unmatched—Addresses that AssignGeoTAXInfo was unable to determine latitude/longitude. Addresses included in this count have a value of null in the LatLong.MatchCode output field.
• GeoTAX Auxiliary-level Matches—The count of geocodes determined using the GeoTAX Auxiliary File.
• Landmark-Level Matches—The count of geocodes determined using the Landmark Auxiliary File.
• Point-level Matches—The count of geocodes that represent the actual location of the address using point-level data. This is the most accurate type of geocode.
• Address-Level Matches—The count of geocodes made to the actual location of the address. Addresses included in this count have a value of R in the LatLong.MatchCode output field.
• ZIP + 4-Level Matches—The count of geocodes made that represent the center of the ZIP + 4 code in which the address is located. Addresses included in this count have a value of 4 in the LatLong.MatchCode output field.
• Census Block Group-Level Matches—The count of geocodes that represent the center of the address's Census block group. Addresses included in this count have a value of B in the LatLong.MatchCode output field.
• ZIP + 2-Level Matches—The count of geocodes that represent the center of the address's ZIP + 2 code. Addresses included in this count have a value of 2 in the LatLong.MatchCode output field.
• Census Tract-Level Matches—The count of geocodes that represent the center of the address's Census tract. Addresses included in this count have a value of T in the LatLong.MatchCode output field.
• ZIP Code-Level Matches—The count of geocodes that represent the center of the ZIP Code in which the address is located. Addresses included in this count have a value of Z or 5 in the LatLong.MatchCode output field.
• City-Centroid Level Matches—The count of geocodes that represent the center of a city.
• State-Centroid Level Matches—The count of geocodes that represent the center of a state.

Census Matching

This section describes how precisely AssignGeoTAXInfo determined an address location within the statistical areas defined by the U.S. Census.

• Census Tracts Determined—Addresses that AssignGeoTAXInfo determined a census tract. Addresses included in this count have a value in the Census.Tract output field.
• Census Tracts Not Determined—Addresses that AssignGeoTAXInfo was unable to determine a census tract. Addresses included in this count have no value in the Census.Tract output field.
• State Codes Determined—Addresses that AssignGeoTAXInfo determined a state. Addresses included in this count have a value in the StateCode output field.
• State Codes Not Determined—Addresses that AssignGeoTAXInfo did not determine a state. Addresses included in this count have no value in the StateCode output field.
• County Codes Determined—Addresses that AssignGeoTAXInfo determined a county. Addresses included in this count have a value in the County.Code output field.
• County Codes Not Determined—Addresses that AssignGeoTAXInfo did not determine a county. Addresses included in this count have no value in the County.Code output field.
• Census Block Group Determined—Addresses that AssignGeoTAXInfo determined a block group. Addresses included in this count have a value in the Census.BlockCode output field.
• Census Block Groups Not Determined—Addresses that AssignGeoTAXInfo was unable to determine a block group Addresses included in this count have no value in the Census.BlockCode output field.
• CBSA Codes Determined—Addresses that AssignGeoTAXInfo determined a core based statistical area (CBSA). Addresses included in this count have a value in the CBSA.Code output field.
• CBSA Codes Not Determined—Addresses that AssignGeoTAXInfo did not determine a core based statistical area (CBSA). Addresses included in this count have no value in the CBSA.Code output field.
• MCD/CCD Codes Determined—Addresses that AssignGeoTAXInfo determined a Minor Civil Division/Census County Division code. Addresses included in this count have a value in the MCD.Code output field.
• MCD/CCD Codes Not Determined—Addresses that AssignGeoTAXInfo was unable to determine a Minor Civil Division/Census County Division code. Addresses included in this count have no value in the MCD.Code output field.

Tax Jurisdiction Matching

This section describes how accurately AssignGeoTAXInfo determined an address place. The place information is used to determine tax jurisdictions.

• Place Codes Determined—Addresses that AssignGeoTAXInfo determined a place code. Addresses included in this count have a value in the Place.Code output field.
• Place Codes Not Determined—Addresses that AssignGeoTAXInfo was unable to determine a place code. Addresses included in this count have no value in the Place.Code output field.
• Place Names Determined—Addresses that AssignGeoTAXInfo determined a place name. Addresses included in this count have a value in the Place.Name output field.
• Place Class Codes Determined—Addresses that AssignGeoTAXInfo determined a place code. Addresses included in this count have a value in the Place.ClassCode output field.
  • Incorporated Places—Addresses that reside in an incorporated municipality. Addresses included in this count have a value of Inc in the Place.IncorporatedFlag output field.
  • Unincorporated Places—Addresses that reside in a place that is not an incorporated municipality. Addresses included in this count have a value of Uninc in the Place.IncorporatedFlag output field.
• Place Last Annexed Date Found—Places that AssignGeoTAXInfo determined the last date of annexation. Addresses included in this count have a value in the Place.LastAnnexedDate output field.
• Place Last Verified Date Found—Places that AssignGeoTAXInfo determined the last date that the place data was verified by the data provider. Addresses included in this count have a value in the Place.LastVerifiedDate output field.
• Place Last Updated Date Found—Places that AssignGeoTAXInfo determined the date that the place data was last updated by the data provider. Addresses included in this count have a value in the Place.LastUpdatedDate output field.

GeoTAX Key Matching

This section describes how accurately AssignGeoTAXInfo determined GeoTAX keys. A GeoTAX key is used in conjunction with software from a third party to determine tax rates. If you do not choose to return a GeoTAX key, this section is blank.

• GeoTAX Cross Reference Match Attempts—Addresses that AssignGeoTAXInfo attempted to match to an cross reference file. These files are used to determine codes for use with third party tax software.
• Unsuccessful GeoTAX Cross Reference Matches—Addresses that AssignGeoTAXInfo attempted to determine a code but was unable.
• Successful GeoTAX Cross Reference Matches—Addresses that AssignGeoTAXInfo determined a code using a cross reference file. Addresses included in this count have a value in the GeoTAXKey output field.
  • Exact Matches Achieved—Addresses matched exactly to a GeoTAX key. For more information about GeoTAX key match levels, see the description of the GeoTAXKey.MatchCode output field under Tax Jurisdiction.
  • Partial Matches Achieved—Addresses partially matched to a GeoTAX key. For more information about GeoTAX key match levels, see the description of the GeoTAXKey.MatchCode output field under Tax Jurisdiction.
  • Alternate Matches Achieved—Addresses matched to a GeoTAX key using an alternate, less accurate, method. For more information about GeoTAX key match levels, see the description of the GeoTAXKey.MatchCode output field under Tax Jurisdiction.
  • Default Matches Achieved—Addresses matched to a GeoTAX key only at the state level. For more information about GeoTAX key match levels, see the description of the GeoTAXKey.MatchCode output field under Tax Jurisdiction.

Tax District Matching

This section describes the number of matches to specific types of tax districts. The specific type of tax districts displayed in this section vary based the district type selected in the Tax district field.

• Successful Payroll Tax File Matches—Addresses that AssignGeoTAXInfo determined a payroll tax code using the Payroll Tax District boundary file. For more information on Payroll Tax Districts, see Payroll Tax Districts.
• Unsuccessful Payroll Tax File Matches—Addresses that AssignGeoTAXInfo was unable to determine a payroll tax code using the Payroll Tax District boundary file. For more information on Payroll Tax Districts, see Payroll Tax Districts.
• Locations in Special Purpose Districts—Addresses that reside in at least one Special Purpose District. For more information on Special Purpose Districts, see Special Purpose Tax Districts.
• Locations in 1 Special Purpose District—Addresses that reside in a single Special Purpose District. Addresses included in this count have a value of 1 in the NumberSPDsFound output field.
• Locations in 2 Special Purpose Districts—Addresses that reside in two overlapping Special Purpose Districts. Addresses included in this count have a value of 2 in the NumberSPDsFound output field.
• Locations in 3 or 4 Special Purpose Districts—Addresses that reside in three or four overlapping Special Purpose Districts. Addresses included in this count have a value of 3 or 4 in the NumberSPDsFound output field.
• Locations in 5+ Special Purpose Districts—Addresses that reside in five or more overlapping Special Purpose Districts. Addresses included in this count have a value of 5 or greater in the NumberSPDsFound output field.
• Locations in User-Defined Districts—Addresses that reside in at least one user-defined district. For more information on user-defined districts, see User-Defined Boundary File.
• Locations in 1 User District—Addresses that reside in one user-defined district. Addresses included in this count have a value of 1 in the NumberUserBoundariesFound output field.
• Locations in 2 User Districts—Addresses that reside in two overlapping user-defined districts. Addresses included in this count have a value of 2 in the NumberUserBoundariesFound output field.
• Locations in 3+ User Districts—Addresses that reside in three or more overlapping user-defined districts. Addresses included in this count have a value of 3 in the NumberUserBoundariesFound output field.