Step 4: Define the Layout & Content of Output Record Elements - GeoTAX_Premium - 7 - 7.7

GeoTAX Premium for Windows, UNIX/Linux, and z/OS

Product type
Software
Portfolio
Verify
Product family
Geo Addressing
Product
GeoTAX Premium
Version
7.7
Language
English
Product name
GeoTAX Premium
Title
GeoTAX Premium for Windows, UNIX/Linux, and z/OS
Copyright
2023
First publish date
1998
ft:lastEdition
2023-10-19
ft:lastPublication
2023-10-19T16:49:54.924301

The next type of information you define is the layout and content of the records that GeoTAX writes to the output files. You specify locations, lengths, and sometimes formats for the following types of data elements:

  • Latitude and longitude information

  • Core Based Statistical Area codes (CBSAs) and names

  • Minor Civil Divisions (MCDs)/Census County Divisions (CCDs) codes and names

  • Census codes, such as state, county, place, Census Tract, Block Group, and Block ID

  • Tax rate data such as state, county and municipality sales and use tax rates when using the optional Precisely Tax Rate reference file

  • User-defined information stored in the Landmark Auxiliary or User Auxiliary files

You define some or all of these parameter records, as shown in the highlighted area in the example screenshot below, depending on your processing requirements.

Parameter Record

Description

AEOUT

Post output (normalized or standardized) Address Elements to your output records.

ALOUT

Post output Address Lines and Last Line elements to your output records.

ARCOUT

Specifies the data elements to post in the GTBMARC file other than latitude and longitude coordinates (for import to a mapping application).

AUXOUT

Specifies the location and length of data to post (on the output record) from the user-defined Auxiliary file.

BF2OUT

Set the buffering distance and post the buffering information from the user-defined boundary file to your output records.

BUFOUT

Set the buffering distance and post buffering information from a boundary file (PAY, SPD, and IPD) to your output records.

CBSOUT

Post CBSA names and codes to your output records.

CNFOUT

Calculate and post Confidence Codes, Place Code status and distance to your output records.

DISTIT

Calculate and post the distance between two sets of latitude/longitude coordinates.

GEOOUT

Post the matched geographic codes to your output records, including FIPS state and county codes, Census Tract, Block Group, Block ID, state abbreviation, and county name.

IPDOUT

Post matched data from the optionally-licensed Insurance Premium District (IPD) file to your output records.

IPROUT

Allows GeoTAX to provide a way to specify the posting of additional Insurance Premium Tax District (IPD) data to your output records to enhance tax jurisdiction assignment.

LLOUT

Post the matched latitude/longitudes to your output records. Also allows you to set latitude/longitude formats and matching levels (street level or postal level).

MCDOUT 

Post the MCD/CCD names and codes to your output records.

MOVE O

Allows you to rearrange pieces of the output record before it is written to the output file.

PAYOUT

Post matched data from the optionally-licensed Payroll Tax District (PAY) file to your output records.

PCOUT

Post Place Codes and names to your output records.

PTCOUT

Post matched data from the Payroll Tax Correspondence (PTC) file to your output records.

SPDOUT

Post matched data from the optionally-licensed Special Purpose Tax District (SPD) file to your output records.

STEOUT

Post additional data from the State-supplied database (either Florida-native or TS-158 format) to your output records.

TAXOUT

Post tax rate data from the optionally-licensed Precisely Sales and Use Tax Rate file to your output records.

USROUT

Post district information from the User-Defined Boundary file to your output records.

Note: GeoTAX creates output records by first copying the input record to the output area then reading all output parameter records and writing the data elements they describe to the desired locations.When defining output locations for your data elements, it is easy to accidentally overwrite input data you want to preserve with output data. Unless you intentionally want to overwrite input data, you should specify locations for your output elements beyond the input data.