This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
37 26-Nov-2021 10:22 10 KB rforbes to previous
36 26-Nov-2021 10:22 10 KB rforbes to previous | to last
35 26-Nov-2021 10:22 11 KB rforbes to previous | to last
34 26-Nov-2021 10:22 11 KB rforbes to previous | to last
33 26-Nov-2021 10:22 12 KB rforbes to previous | to last
32 26-Nov-2021 10:22 16 KB jescott to previous | to last
31 26-Nov-2021 10:22 15 KB jmyers to previous | to last
30 26-Nov-2021 10:22 15 KB jmyers to previous | to last
29 26-Nov-2021 10:22 15 KB jmyers to previous | to last
28 26-Nov-2021 10:22 15 KB jmyers to previous | to last
27 26-Nov-2021 10:22 15 KB jmyers to previous | to last
26 26-Nov-2021 10:22 15 KB jmyers to previous | to last
25 26-Nov-2021 10:22 15 KB jmyers to previous | to last
24 26-Nov-2021 10:22 15 KB jmyers to previous | to last
23 26-Nov-2021 10:22 15 KB jmyers to previous | to last
22 26-Nov-2021 10:22 15 KB jmyers to previous | to last
21 26-Nov-2021 10:22 15 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
US Load GNIS Locations
US Load GNIS Locations

Version management

Difference between version and

At line 5 changed one line
This page describes the process to load the US Geographic Names Information System (GNIS) Locations from the Symmetry Tax Server which calls the Symmetry Tax Engine (STE).
This page describes the process to load the US Geographic Names Information System (GNIS) locations from the Symmetry Tax server which calls the Symmetry Tax Engine (STE).
At line 13 changed one line
|Country|This mandatory field allows you to enter the Country Code used to filter the list of states.
|Country|This mandatory field allows you to enter the Country code used to filter the list of states.
At line 21 changed 4 lines
|Vertex Conversion|Optional, [Yes or No|X_YES_NO] lexicon available\\This toggle is used to convert IDTX entries from Vertex Format to Symmetry Format\\The old Vertex IDTX GEO entries that are not being used will be removed\\The old Vertex IDTX GEO entries that are being used will be converted to Symmetry GNIS format
|Directory Name|if Create File = 'Y', user must enter a valid Directory Name for the .csv file
|File Name|if Create File = 'Y', user must enter a File Name for the .csv file
|Exception Level|Optional, [Exception Level|X_TRACE_LEVEL] lexicon available\\This field defines the exception level (report messages) required.\\You should run with Exception Level except for Tracing\\In 'Utility Trace', the report may be quite large
|Vertex Conversion|Obsolete - set to No
|Directory Name|If the Create File field is set to <<Y>>, you must enter a valid Directory Name for the .csv file.
|File Name|If the Create File field is set to <<Y>>, you must enter a file name for the .csv file.
|Exception Level|Optional, [Exception Level|X_TRACE_LEVEL] lexicon available\\This field defines the exception level (report messages) required.\\You should run with Exception Level except for tracing\\In 'Utility Trace', the report may be quite large.
At line 29 removed one line
!UDGNIS - Processing
At line 31 removed one line
*GNIS code is the Symmetry version of the Vertex GEO code.
At line 33 changed one line
*UDGNIS is a high volume process and may take from one minute to ten minutes to process each State, loading in all Counties, Cities, Schools, Municipalities, ZIP codes and Jurisdictions. Please do not cancel the report while it is running. To see the progress of the run, you may check the size of the Output .csv file from the Output directory.
*UDGNIS is a high volume process and may take from one minute to ten minutes to process each state, loading in all Counties, Cities, Schools, Municipalities, ZIP codes and Jurisdictions. Please do not cancel the report while it is running. To see the progress of the run, you may check the size of the Output .csv file from the Output directory.
At line 35 changed one line
*The file name will be suffixed with the State code; you may attach the mex id of the run to the file name.\\e.g. File Name: cathy_gnis_mex\\- ‘mex’ will be replaced with the execution ID, then suffix with the State code
*The file name will be suffixed with the State code; you may attach the mex id of the run to the file name.\\e.g. File Name: cathy_gnis_mex 'mex' will be replaced with the execution ID, then suffix with the State code.
At line 37 changed 2 lines
*If the ‘Print Detail’ toggle is set to <<Yes>>, UDGNIS will list the detail entries that are processed for each level: Country, States, Counties, Cities, Schools, Municipalities, Tax Jurisdictions.
*If you have converted from Vertex Taxation to Symmetry Taxation for the Payroll Module, you MUST run UDGNIS with the ‘Vertex Conversion’ toggle set to <<Yes>> for the first time. Please read [Vertex Conversion|US Load GNIS Locations#section-US+Load+GNIS+Locations-VertexConversion] below.
*If the 'Print Detail' toggle is set to <<Yes>>, UDGNIS will list the detail entries that are processed for each level: Country, States, Counties, Cities, Schools, Municipalities, Tax Jurisdictions.
At line 41 changed one line
*#*UDGNIS should be scheduled as part of the Legislation Cycle at the beginning of the year
*#*UDGNIS should be scheduled as part of the Legislation cycle at the beginning of the year
At line 47 removed one line
*If you have not converted from Vertex, UDGNIS will load in all necessary Geographic Names Information into the system.
At line 45 added 2 lines
* UDGNIS will not create Tax Jurisdictions with School Districts or Municipalities, therefore the user will have to manually associate the School District and Municipalities to the appropriate Tax Jurisdictions.
*In order for School District Tax and Municipality Tax to be calculated these must be associated to a Tax Jurisdiction in IDTX. If you have employees residing in Ohio or Pennsylvania please review their Tax Jurisdictions in IDTX and associate the appropriate School and Municipality.
At line 48 added one line
At line 56 changed one line
*‘ISO Alpha 2’ and ‘ISO Alpha 3’ will be updated if these are not set up
*'ISO Alpha 2' and 'ISO Alpha 3' will be updated if these are not set up
At line 65 changed one line
*existing County Code and County Name will be compared to Symmetry County Code and County Name
*Existing County Code and County Name will be compared to Symmetry County Code and County Name
At line 69 removed one line
*For Vertex conversion, Alternate County Code will be updated with the Vertex County Code for reference
At line 75 changed 3 lines
*City Code Format is: CCCCCCC - 7 digits City code
*For each county from IDCN, UDGNIS retrieves all City Codes that are for each county
*This helps the user to enter the correct combination of City with the related County for Tax calculation
*City Code format is: CCCCCCC - 7 digits City code
*For each county from IDCN, UDGNIS retrieves all City Codes for that county
*This helps you enter the correct combination of City with the related County for tax calculation
At line 82 changed one line
*existing School District Code and Name will be compared to Symmetry School Code and Name
*Existing School District Code and Name will be compared to Symmetry School Code and Name
At line 84 changed 2 lines
*for Each County from IDCN, UDGNIS retrieves all School District Codes that are for each County
*this helps the user to enter the correct combination of School with the related County for Tax calculation
*For each County from IDCN, UDGNIS retrieves all School District Codes for that county
*This helps you enter the correct combination of School with the related County for tax calculation
At line 89 changed 5 lines
*new Municipalities will be loaded
*existing Municipality Code and Name will be compared to Symmetry Municipality Code and Name
*Municipality Code Format is: MMMMMMM - 7 digits Municipality code
*for each County from IDCN, UDGNIS retrieves all Municipality Codes that are for each County
*this helps the user to enter the correct combination of Municipality with the related County
*New Municipalities will be loaded
*Existing Municipality Code and Name will be compared to Symmetry Municipality Code and Name
*Municipality Code Format is:MMMMMMM - 7 digits Municipality code
*For each County from IDCN, UDGNIS retrieves all Municipality Codes for that county
*This helps you enter the correct combination of Municipality with the related County
At line 97 changed 5 lines
*new ZIP codes will be loaded
*existing ZIP Code and Description will be compared to Symmetry ZIP Code and City Name
*for Each County from IDCN, UDGNIS retrieves all ZIP Codes that are for each County
*the applicable City code within each County are provided for each ZIP code
*this helps the user to enter the correct combination of ZIP code with the related County for Tax calculation
*New ZIP codes will be loaded
*Existing ZIP Code and Description will be compared to Symmetry ZIP Code and City Name
*For each County from IDCN, UDGNIS retrieves all ZIP Codes for that county
*The applicable City code within each County are provided for each ZIP code
*This helps you enter the correct combination of ZIP code with the related County for Tax calculation
At line 105 changed one line
*IDTX screen is used to store the combination of State, County, City, School, Municipality for Taxation
*IDTX screen is used to store the combination of State, County, City, School, Municipality for taxation
At line 107 changed 2 lines
*If the UDGNIS was run with the parameter Create Jurisdictions = Yes, the system will load in cities into IDTX creating Tax Jurisdictions for all cities for the states selected in the UDGNIS. The user would then have to manually enter Municipality and School District for Pennsylvania and Ohio.
*If UDGNIS was run with the parameter Create Jurisdictions = No, the user will need to enter the IDTX entry using the ‘Tax Jurisdiction Editor Dialog Box’ provided by the system on the applicable screen
*If the UDGNIS was run with the Create Jurisdictions toggle set to <<Yes>>, the system will load cities into IDTX, creating tax jurisdictions for all cities within the states selected in the UDGNIS. You then have to manually enter Municipality and School District for Pennsylvania and Ohio.
*If UDGNIS was run with the Create Jurisdictions toggle set to <<No>>, you will need to enter the IDTX entry using the 'Tax Jurisdiction Editor Dialog Box' provided by the system on the applicable screen.
At line 110 removed 41 lines
!!Vertex Conversion
!Vertex Conversion Processing
*if user is converting from Vertex Taxation to Symmetry Taxation in the Payroll Module, user MUST run UDGNIS with ‘Vertex Conversion’ = ‘Y’ for the first time
*after UDGNIS is run with ‘Vertex Conversion’ = ‘Y’, all related Vertex Geographic Data Base Tables are converted, after the conversion, user MUST review UDGNIS exception report and manually fix any IDTX entries that cannot be converted
*IDCN County Code format is changed from Vertex Format ‘XX-XXX-0000’ to Symmetry Format ‘XX-XXX’, the Alternate County Code will store the previous Vertex County Code for reference
*Vertex does not use IDCI City Code, no conversion is needed for City Codes
*Vertex does not use IDMN Municipality Code, no conversion is needed for Municipality Codes
*IDSD School Districts code are checked, if the Vertex School District has not been used in the System, this Vertex School District Code will be removed
*the Vertex School District Name is used to look for a close match from Symmetry and update the existing School District entry with the Symmetry School District Code and Name, along with the applicable County Code of the School District
*for Vertex IDTX Tax Jurisdiction entry that has not been used in the System, if the parameter Remove Jurisdiction was set to Yes, this IDTX entry will be removed. If the parameter was set to No, the tax jurisdiction will remain.
*for Vertex IDTX Tax Jurisdiction entry that has been used in the System, this IDTX entry will try to be converted to Symmetry Format
*the IDTX Jurisdiction name is used to look for a close match from Symmetry
*IDTX Vertex GEO Code format is changed from ‘XX-XXX-XXXX’ to Symmetry Format ‘AA-BBB-CCCCCCC’, the old Vertex GEO Code will be stored in the Vtx GEO Code for reference
*if Symmetry has an exact match of the Jurisdiction Name, then this IDTX entry will be updated with the new GNIS Code in format of ‘AA-BBB-CCCCCCC’, along with the County dcn_id and City dci_id
*if Symmetry has no exact match for the Jurisdiction Name, then an exception message will be displayed, a Suggested County and City Name may be displayed, user MUST manually convert this IDTX entry after UDGNIS is run
*after Vertex GEO entries are cleaned up from IDTX, the user MUST review the UDGNIS Exception Report and manually fix the IDTX entries that cannot be converted
*symmetry may not be able to convert a Vertex Jurisdiction if the name is not a valid town name as considered by the US Postal Service. Symmetry uses Zip Codes within their GNIS filter mechanism to determine the appropriate County, City, Feature id combination, if the town name is not valid then it will not be able to generate the correct combination.
!Manual Conversion - IDTX
There may be cases where the UDGNIS could not convert a tax jurisdiction. This could be a result of a spelling error or the jurisdiction is not classified as a real city by the US Postal Service and therefore the UDGNIS could not find the correct GNIS code to use.
To manually change a Vertex GEO Code to the Symmetry GNIS format follow the steps below:
#In IDTX, copy the Vertex GEO Code into the Vtx Geo Code field. This is needed so that when UPCALC is run using Vertex, UPCALC knows to use the Vertex GEO Code rather than the GNIS code.
#Using the fields on the right hand side, select the correct County and City. This will create the appropriate GNIS Geo Code. The name defined in the Jurisdiction field will be replaced with the City name.
At line 154 changed one line
*if ‘Create File’ = Yes, each State will generate one .csv File to contain the Geographic Information for the State
*If the 'Create File' toggle is set to <<Yes>>, each state will generate one .csv file to contain the Geographic Information for the state.
At line 158 changed 2 lines
*at State Level, the FIPS code is retrieved, e.g PA FIPS code is 42
*then all counties will be retrieved for this State, e.g. PA has 67 Counties
*At the State level, the FIPS code is retrieved, e.g PA FIPS code is 42
*At that point, all counties will be retrieved for this State, e.g. PA has 67 Counties
At line 163 changed 2 lines
*at County Level, all Counties are retrieved, the County Codes and Names are displayed, not sorted
*after all Counties are read, the County Code is built in Format XX-XXX, then will be sorted and updated to IDCN
*At the County level, all Counties are retrieved and the County codes and names are displayed but not sorted.
*After all Counties are read, the County code is built in as format XX-XXX, which will then be sorted and updated to IDCN
At line 168 changed one line
*UDGNIS will loop through each County to retrieve all Cities by County, then sorted and updated to IDCI
*UDGNIS will loop through each County to retrieve all Cities by County, which will then be sorted and updated to IDCI
At line 172 changed one line
*UDGNIS will loop through each County to retrieve all Schools by County, then sorted and updated to IDSD
*UDGNIS will loop through each County to retrieve all Schools by County, which will then be sorted and updated to IDSD
At line 176 changed one line
*UDGNIS will loop through each County to retrieve all Municipalities by County, then sorted and updated to IDSD
*UDGNIS will loop through each County to retrieve all Municipalities by County, which will then be sorted and updated to IDSD
At line 180 changed one line
*UDGNIS will loop through each County to retrieve all ZIPs by County and City, then sorted and updated to IDZR
*UDGNIS will loop through each County to retrieve all ZIPs by County and City, which will then be sorted and updated to [IDZR]
At line 184 removed 25 lines
!UDGNIS - Vertex Conversion Sample File
- During Vertex Conversion, if the IDTX Vertex GEO Code entries cannot find an exact match from Symmetry, a WARNING Message will be displayed
- user MUST manually go into IDTX screen to modify the Vertex GEO Code with Description to the Symmetry Format
- e.g the following is an example of UDGNIS Message Displays after Vertex Conversion:
- user should review the UDGNIS Messages and the Output File for the Vertex IDTX GEO Codes displayed
- if there is an exact match with the Jurisdiction Description, IDTX will be converted
- if there is no match, a partial search will be performed to help the user to manually enter on IDTX screen
- if there is no partial match, the user must manually convert the Vertex GEO Code on IDTX screen
- UDGNIS will remove the unused old Vertex IDTX entries, after UDGNIS is run, user MUST manually convert the left over IDTX Vertex entries because these entries are being used in the system by Payroll
----
This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbesTop