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 113 changed one line
*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
*If you are converting from Vertex Taxation to Symmetry Taxation in the Payroll Module, your MUST run UDGNIS with Vertex Conversion toggle set to <<Yes>> for the first time.
At line 115 changed one line
*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
*After UDGNIS is run with Vertex Conversion toggle set to <<Yes>>, all related Vertex Geographic database tables are converted. After the conversion, you MUST review the UDGNIS exception report and manually fix any IDTX entries that cannot be converted.
At line 117 changed one line
*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
*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.
At line 119 changed one line
*Vertex does not use IDCI City Code, no conversion is needed for City Codes
*Vertex does not use IDCI City code therefore, no conversion is needed for City codes.
At line 121 changed one line
*Vertex does not use IDMN Municipality Code, no conversion is needed for Municipality Codes
*Vertex does not use IDMN Municipality code therefore, no conversion is needed for Municipality codes.
At line 123 changed one line
*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
*IDSD School Districts code are checked and if the Vertex School District has not been used in the system, that Vertex School District code will be removed.
At line 125 changed one line
*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
*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.
At line 127 changed one line
*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 a Vertex IDTX Tax Jurisdiction entry that has not been used in the system, if the Remove Jurisdiction toggle was set to <<Yes>>, this IDTX entry will be removed. If the toggle was set to <<No>>, the tax jurisdiction will remain.
At line 129 changed one line
*for Vertex IDTX Tax Jurisdiction entry that has been used in the System, this IDTX entry will try to be converted to Symmetry Format
*For a Vertex IDTX Tax Jurisdiction entry that has been used in the system, this IDTX entry will try to be converted to Symmetry format.
At line 131 changed one line
*the IDTX Jurisdiction name is used to look for a close match from Symmetry
*The IDTX Jurisdiction name is used to look for a close match from Symmetry
At line 133 changed one line
*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
*IDTX Vertex GEO Code format is changed from 'XX-XXX-XXXX' to Symmetry Format 'A-BBB-CCCCCCC', the old Vertex GEO Code will be stored in the Vtx GEO Code for reference
At line 135 changed one line
*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 an exact match of the Jurisdiction Name, then this IDTX entry will be updated with the new GNIS Code in the format of 'AA-BBB-CCCCCCC', along with the County dcn_id and City dci_id
At line 137 changed one line
*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
*If Symmetry has no exact match for the Jurisdiction Name, then an exception message will be displayed and a suggested County and City Name may be displayed. You MUST manually convert this IDTX entry after UDGNIS is run.
At line 139 changed one line
*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
*After Vertex GEO entries are cleaned up from IDTX, you MUST review the UDGNIS exception report and manually fix the IDTX entries that cannot be converted.
At line 141 changed one line
*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.
*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.
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 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 185 changed 3 lines
*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:
*During Vertex Conversion, if the IDTX Vertex GEO Code entries cannot find an exact match from Symmetry, a WARNING message will be displayed
*You 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:
At line 193 changed 5 lines
*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
*You 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 you to manually enter on IDTX screen.
*If there is no partial match, you must manually convert the Vertex GEO Code on IDTX screen.
*UDGNIS will remove the unused old Vertex IDTX entries, after UDGNIS is run, you MUST manually convert the left over IDTX Vertex entries because these entries are being used in the system by Payroll.
At line 199 removed 5 lines
This page (revision-37) was last changed on 26-Nov-2021 10:22 by rforbesTop