The ODNR software for CAUV tax computation is written for use with
ARC/INFO version 7 software on NT workstations. The processing steps of
tax computation can be run using a combination of Windows and ARC/INFO commands and the ODNR AMLs which must be properly installed along with the ODNR-supplied data.
Overview

Township parcel data layer:

Parcels uniquely identified by PIN. Any parcel may be composed of more than 1 polygon.

Township landuse data layer:

Township soils data layer:

Landuse classed as C, P, W, O C– cropland, P– pasture W– woodland, O– other landuse type

Various soil types, rated by agricultural productivity. CAUV $ tax rate is based on soil type within landuse category (better soil + more productive landuse has higher tax rate)

County data are stored in township coverages- <township>SOLU is a soils-landuse overlay which is static, not updated unless a new soil survey or landuse classification is done. <township>SOIL is the township’s soils, and is also static (only used for tax overlay plots). <township> is the township parcel layer, and it is updated as needed by new auditor records. The QTAX program does an overlay of the township’s parcel and SOLU layers:

producing tabular statistics of the data overlay in printed and digital forms. The statistics summarize the data overlay for each parcel and apply the CAUV tax rates to this overlay. Optional “Other Land Uses” may be supplied by the auditor to include these additional taxations into the data summary:

Data Components The data are organized as township workspaces within the main county directory:

An example of a township’s workspace is the following:

Software Components The software components are the main TAX.AML, the main menu of commands TAX.MENU, and individual special-purpose AMLs and menus which are called by these. The program is run by typing “TAX” from the Arc: prompt- Arc: tax ** ARC/INFO TAX Application– current workspace is C:\MORROWTAX\FRANKLIN

The following flowchart shows the major work phases with the TAX menu commands listed in brackets:

Output files from QTAX run: You provide the program with a <runname> prefix and it creates the following files: <run>.TAX– full listing file of individual parcels’ tax statistics <run>.LOG- listing of any warnings raised in individual parcels’ processing <run>.TOT– an internal INFO file of each parcel’s tax statistics <run>.CPW– an internal INFO file containing records for each parcel-landuse type-soil type overlay combination. The .TOT and .CPW files can potentially be reformatted to feed into a tax database system– they are the digital equivalents of the printed .TAX listing. A full listing of all files created by the TAX.AML software appears in Appendix C.

Appendices A and C list the individual files installed in the county and township workspaces.

Software/data Installation Details of the installation are given in the appendices:
Appendix A– data installation AML, details of installed files Appendix B– modification of user ARC accounts to run this software Details of new files created by the TAX software are given in Appendix C.
Appendix D describes all of the parcel coverage .PAT items for this county.

***************************************************************************************************************************
PARCEL ID OWNER ASSR ACRES COMPUTED ACRES
F140010007101 COHEN HARRY L AND 79.770 83.486
ADJUSTED % OF ASSR CAUV/
LAND USE SOIL ACRES ACRES ACRE CAUV ($)
CROPLAND 1 AdB Amanda silt loam, 2-6 % slopes 11.497 14.41 200 2,299.47
CROPLAND 2 AdC2 Amanda silt loam, 6-12 % slopes 9.933 12.45 110 1,092.66
CROPLAND 3 AdD2 Amanda silt loam, 12-18 % slopes 2.830 3.55 100 283.02
CROPLAND 4 AdE2 Amanda silt loam, 18-25 % slopes 4.164 5.22 100 416.39
CROPLAND 13 CdB Centerburg silt loam, 2-6 % slopes 18.231 22.85 210 3,828.56
CROPLAND 19 Co Condit silt loam 0.075 0.09 100 7.47
PASTURE 2 AdC2 Amanda silt loam, 6-12 % slopes 3.817 4.78 110 419.86
PASTURE 3 AdD2 Amanda silt loam, 12-18 % slopes 4.398 5.51 100 439.82
PASTURE 13 CdB Centerburg silt loam, 2-6 % slopes 0.700 0.88 210 147.05
WOODLAND 1 AdB Amanda silt loam, 2-6 % slopes 6.115 7.67 70 428.04
WOODLAND 2 AdC2 Amanda silt loam, 6-12 % slopes 15.023 18.83 70 1,051.58
WOODLAND 3 AdD2 Amanda silt loam, 12-18 % slopes 1.617 2.03 70 113.21
WOODLAND 4 AdE2 Amanda silt loam, 18-25 % slopes 0.225 0.28 70 15.74
WOODLAND 13 CdB Centerburg silt loam, 2-6 % slopes 0.833 1.04 70 58.31
WOODLAND 19 Co Condit silt loam 0.001 0.00 70 0.09
CPW TOTALS: 79.460 ADJUSTED ACRES 99.61 % (OF ASSR ACRES) $10,601.28 CAUV $ 133.42 CAUV/ADJUSTED ACRE
OTHER LANDUSE DESCRIPTION ACRES % OF ASSR ACRES TAX
Road/Waste 0.310 0.39 $ 0.00
ASSR OTHER LANDUSE TOTALS: 0.310 ACRES 0.39 % (OF ASSR ACRES) $ 0.00 TAX

Procedural Details Key to each QTAX run is which parcels are processed– this is controlled by the parcel coverage.PAT item called INCL (inclusion flag). It is set =1 for those PINs which are to be processed. The menu command SELECT PARCELS FOR TAX RUN allows zeroing out the selection, selecting all CAUV-eligible parcels in the township, or selecting individual parcels by their PINs. There are basically 2 types of QTAX runs: Incremental (only run on updated parcels)- zero out all INCL before starting series of parcel updates for this township, then calc INCL=1 on each parcel that is updated. Full township run– zero out all INCL, then use SELECT ALL to set INCL=1 on all eligible parcels.
Details of an individual parcel update and QTAX run are given in the Detailed Parcel Update Example section. Parcel coverage versions: As each parcel update is made a new parcel coverage is created. A backup version of the <township> coverage is created (first version <twp>-1, second version <twp>-2, etc.). After running the tax computation on that township and verifying the results, you can delete the backup version(s) if you want. This is done by the menu Utility Program CLEANUP TOWNSHIP WORKSPACE. It asks if you want to delete each temporary coverage that is finds. Backup of parcel coverages: The menu Utility Program BACKUP PARCEL COVERAGES will take the current <township> parcel coverage from each \<township> workspace and copy them all to a new single countywide parcel workspace. The default names for these backup workspaces are “PARCELS”<date>, for example \PARCELS_11Feb2001. This serves as a snapshot of the parcels at that time and allows restoring that version of any township later. The backup workspace can be deleted by a single ARC-level command– be located 1 directory level above the temporary workspace, and type from the Arc> prompt: Arc: KILLW parcels_20feb2001 (the KILLW AML verifies that you want to totally delete this workspace before deleting it).

Run-level recommendations: 1) Keep all <tpw>-1,-2,… parcel coverage versions until you are comfortable with parcel updating steps. If you make a mistake and have to recover an earlier version of the parcel coverage, this is easily done by: Arc: KILL <twp> ALL Arc: RENAME <twp>-1 <twp> (or whichever version # is the last good version, use <twp>-#) 2) Do BACKUP PARCEL COVERAGES before a large series of parcel updates Do the updates on each township with 1 full-township run for that township at the end of updates. At the end of the update series, run BACKUP PARCEL COVERAGES again, to make a final copy, and copy the full-township .TAX files into that workspace also.
Do a full-disk backup (or at least the full \<county> workspace) at the end of the series of updates, when you have all of the temporary files in each \<township> created. 3) Then to clean out ALL but the minimum files that the tax software needs: run the menu CLEANUP TOWNSHIP WORKSPACE command on each. 4) If however you have to run QTAX more frequently (as single parcel updates are done) you have to modify this strategy. Use the ZERO ALL menu command to unselect all parcels, run parcel updates and set INCL=1 on those that you want in the next QTAX run, make the QTAX run on the selected parcels and process the output.
You might want to double-check the new parcels by running the CREATE TAX PLOT on the updated area. If you feel confident about each update, you could clean up the \<township> workspace after each update and QTAX run. But it is probably good to keep a full-county “snapshot” by using the BACKUP PARCEL COVERAGES command frequently, and creating a full-township QTAX run listing to store with that backup data.

click where to add a label, one is added
use SELECT BOX to select 1 label, click where to move from,
click where to move to, it is moved there
use SELECT BOX to select 1 label, its attributes are listed on screen
use SELECT BOX to select 1 label, it is deleted
begin FORMS to edit parcel label attributes
switch to editing arcs (brings up the arc-editing menu)

select an arc and it is deleted
select an arc, select a vertex, and it is split there
select an arc, click a location and it is split there
select an arc, select a vertex, click where to move it so
select an arc, select which node, set distance and it is extended until it intersects another arc (or fails if no arc can be reached)
switch to editing labels (brings up the label-editing menu)

The MERGE LINEWORK command uses the following menus of ARCEDIT commands. These are used to splice in the new arcs which are added in parcel updates, and to edit old and new polygon labels, so that each polygon has a single label:

click 2 points to define the window rectangle, then screen is redrawn
enlarges the current mapextent by 2 times, then redraws
redraws the current display
draws parcel PIN values at polygon label points
turns off draw of parcel PINs

select an arc and its vertices are drawn
select an arc, select a vertex, and it is deleted
select an arc, click where to add a vertex, and it is added
undo the last ARCEDIT command
type in your own ARCEDIT commands, then type "RET" to return to this menu
end this menu, save or reject the updated coverage

click 2 points to define the window rectangle, then screen is redrawn
enlarges the current mapextent by 2 times, then redraws
redraws the current display
draws parcel PIN values at polygon label points
turns off draw of parcel PINs

undo the last ARCEDIT command
type in your own ARCEDIT commands, then type "RET" to return to this menu
end this menu, save or reject the updated coverage

CAUV Tax Procedure

- # -

Steps to Making Parcel Updates
Given a parcel update to make, you should do the following: 1) find the starting parcel(s) in the current parcel coverage 2) list attributes of starting parcel(s) 3) plan the linework changes– decide where to place the required 4 (or more) tic control points decide which lines must be added and/or deleted 4) plan the attribute changes– changes to existing parcel records, new parcel records to add 5) run TAX software to make the updates Detailed Parcel Update Example The following is an example of a parcel update– PIN F140010007100 is being split, resulting in a smaller starting parcel and an added F140010007105 parcel:

Starting parcel

508
PIN =F140010007100
ONAME =LYONS MARILYN
AACRE = 94.730
HOMEACRE = 1.500
HOMEVAL =12100
ROADACRE = 0.000
ROADVAL = 0
OTHERACRE = 0.000
OTHERVAL = 0
INCL = 1

Starting attributes:

Find this area in the current parcel coverage (use the TAX menu LIST PARCEL and DRAW PARCEL commands). Remember that if a single PIN has more than 1 polygon record, then those records will have to be kept consistent when you update the parcel attributes. The acreages listed in both records must match and should be the total acreage for the entire parcel.
Here is the parent parcel and its INFO attributes:

The parcel update shows 75.084 Acres for the new -05 parcel. From this we calculate 19.646 remaining for the old -00 parcel. And Homesite acreages of 1 are indicated for both updated parcels. ***However the HOMEVAL values are not given for the revised parcel records.

Comparing the starting parcel and the update map, we decide that a new line must be added to separate out the new parcel. The linework edits require setting at least 4 tic control points around the new line(s). These must be placed at points in the existing linework, surrounding the new lines to be added. They should be placed close to the new lines. Below is the update map with the planned 5 tic points and the new line to be added drawn in red:

These parcel records also have the INCLusion flag set to 1, so they are selected to have their tax calculated in the next QTAX run on this township.
Details of the parcel update software steps are on the following pages.

508
AREA = 936,612.85177
PERIMETER = 5,669.16261
FRAN# = 508
FRAN-ID = 416
PIN =F140010007100
ONAME =LYONS MARILYN
AACRE = 19.646
HOMEACRE = 1.000
HOMEVAL = 0
ROADACRE = 0.000
ROADVAL = 0
OTHERACRE = 0.000
OTHERVAL = 0
INCL = 1
521
AREA = 3,265,150.90892
PERIMETER = 8,286.25586
FRAN# = 521
FRAN-ID = 599
PIN =F140010007105
ONAME =BRIAN JACOBSON
AACRE = 75.084
HOMEACRE = 1.000
HOMEVAL = 0
ROADACRE = 0.000
ROADVAL = 0
OTHERACRE = 0.000
OTHERVAL = 0
INCL = 1

After running the TAX software for Parcel Updates, a new version of the township parcel coverage is created which contains the modified F140010007100 and F140010007105 parcels:

User steps:

These prompts appear on the screen:

+

+

Digitize each tic point: enter the number “1” on the digitizer puck enter “A” on the digitizer puck (to end the 1st tic ID) position the puck crosshairs exactly over the point, press any key to register that tic point (repeat for tics 2,3,4,5) then press “0” and “A” on the puck, to indicate you have entered all of the tics that you want. Then for “Enter initial boundary”, enter a point at the lower-left and upper-right corners of the data.

Creating C:\MORROWTAX\SAMPLE\FRANADD00001
Digitize a minimum of 4 tics (from digitizer).
Signal end of tic input with Tic-ID = 0
Tic-ID:1*
Tic-ID:2*
Tic-ID:3*
Tic-ID:4*
Tic-ID:5*
Tic-ID:0*
Enter initial boundary
Define the box (from digitizer)

Detailed Parcel Update Example– Software Steps This example shows the software steps done to perform the parcel update described in the preceding pages. The full on-screen script of this example is in Appendix E. Before starting, have the digitizer power on and the base map taped up on it. Start TAX and choose Parcel Updates: ALL STEPS from the menu DIGITIZE step: ARCEDIT is started to create a new coverage named FRANADD00001 (FRANklin twp, added linework, temp coverage # 1). You are prompted to digitize at least 4 tics, then tic ID 0 to end adding tics, then set the bounding box of the new data. Then you add the single arc, tracing it on the base map. You should draw its starting and ending node points so that they will overlap the existing linework (it is easier to clean up overhanging lines than lines that fall short of where they are supposed to connect with existing lines).

Digitizing details: enter “2” to place starting node, enter “1” for 2 intermediate vertices, enter “2” to place ending node. Note that nodes overlap into the existing parent parcel arcs. Enter “9” to end arc digitizing, and you see the “1 arc(s) added …” message on the screen.

These prompts appear on the screen:

Next you digitize the linework which will split out the new parcel from the parent parcel. Build in overhang at both ends so it will cross the parent parcel’s existing arcs.

The edit coverage is now C:\MORROWTAX\SAMPLE\FRANADD00001
Defaulting the map extent to the BND of C:\MORROWTAX\SAMPLE\FRANADD00001
Current EDITCOV is franadd00001 and COORDINATE device is DIGITIZER.
0 element(s) for edit feature ARC
Coverage has no COGO attributes
ARCEDIT is set up to digitize new arcs, with INTERSECTARCS ALL and
NODESNAP CLOSEST .1" set. Starting ADD command:
--------------------Options--------------------
1) Vertex 2) Node 3) Curve
4) Delete vertex 5) Delete arc 6) Spline on/off
7) Square on/off 8) Digitizing Options 9) Quit
(Line) User-ID: 1 Points 0
1
2
3
4
Please wait...
(Line) User-ID: 2 Points 0
-----
1 arc(s) added to C:\MORROWTAX\SAMPLE\FRANADD00001

** CREATETICS PROCEDURE **
** You will be asked to assign an ID for each new tic.
Here are the current tic IDs in fran.tic
Press Return to see them: |>><<|
Record IDTIC
1 102
2 103
3 104
4 105
. . .
40 522
41 523
Press Return to continue:

CREATETICS step: CREATETICS starts up ARCEDIT on the current parcel coverage and has you enter tic points to match those that were just digitized with the new linework. The tics that you add must be in the same relative locations on the parcel arcs and have the same ID numbers as those in the digitized coverage.

Screen messages:

This ends the ARCEDIT session to create the tics and new linework. The program asks if the data is OK, and it saves the new coverage if so. You are also given the chance to do your own ARCEDIT commands here.

-----
1 arc(s) added to C:\MORROWTAX\SAMPLE\FRANADD00001
** Ended ADD. Do any of your own ARCEDIT commands now,
** then type "RET" when done. You will be prompted to save data
** or reject it then.
Running TTY - do your own ARCEDIT commands, then type "ret" to return to AML:
Arcedit: |> ret <|
This new digitized data is coverage franadd00001.
Do you want to SAVE it (Y)? |
Saving changes for C:\MORROWTAX\SAMPLE\FRANADD00001
Saving arcs...
1 arc(s) written to C:\MORROWTAX\SAMPLE\FRANADD00001
from the original 0, 1 added and 0 deleted
Saving tics...
** NOTE ** Tic(s) unchanged
BND replaced into C:\MORROWTAX\SAMPLE\FRANADD00001
Saving set tolerances to TOL file...
Leaving ARCEDIT...

CREATETICS operates in a command loop. You can do your own ARCEDIT
commands, add a new tic, or QUIT at each loop iteration. To delete tics,
you have to do your own AE commands EDITF TIC, SELECT, DELETE.
Press Return to start the add-tic loop:
DRAWING COVERAGES . . .

CREATETICS draws the current parcel coverage (named “fran” here) on the screen and asks if you want to do any of your own ARCEDIT commands, such as to change the DRAW environment:

Starting ARCEDIT - the current WORKSPACE is: c:\morrowtax\sample
The edit coverage is now C:\MORROWTAX\SAMPLE\FRAN
Defaulting the map extent to the BND of C:\MORROWTAX\SAMPLE\FRAN
Please wait...
Please wait...
Running TTY - do your own ARCEDIT commands, then type "ret" to return to AML:
Arcedit: |> ret <|

CREATETICS has a menu of 6 commands. But since the most common command is adding a tic at a node, it has a built-in shortcut to run this command without going through the menu. By clicking the left mouse button, you go immediately into the add tic at node command. This example shows adding the 1st node, in detail. The other 4 nodes are added using the same method:

+

+

Select Box Passthru– click on both sides of the arc to select it. Click on the node where the tic is to be created. (the software adds a tic at that exact location)

Select next command: ADD TIC AT NODE (left mouse button), PICK FROM MENU OF ALL COMMANDS (right mouse button):
Create tic at node.
Using SELECT BOX PASSTHRU, select an arc which ends at the node:
Define the box
1 element(s) now selected
Point to the node with the mouse and click:
Calculating exact node X,Y . . .
41 element(s) for edit feature TIC
--------------------Options--------------------
1) Add Tic 3) New User-ID 5) Delete last tic
6) New symbol 7) Autoincrement OFF 8) Autoincrement RESUME
9) Quit
(Tic) User-ID: 527 Coordinate =
New User-ID(Tic) User-ID: 0 Coordinate =

Proceed to enter tics with Ids 2,3,4,and 5. Then when prompted (left-click to add node at tic, right-click to select from the full menu) do right-click. The command “5” can be used to redraw and verify the tics are OK, then choose “6” Quit and save the coverage:

1

. . .
Select a command from the menu for the next step to be done:
(1) suspend CREATETICS to do your own ARCEDIT commands (e.g. MAPE,DRAW)
(2) add tic at node
(3) add tic at vertex
(4) add tic at X,Y
(5) redraw the screen
(6) exit CREATETICS loop (for ARCEDIT QUIT options):
QUIT command. Do you want to save fran (Y)? |
Saving changes for C:\MORROWTAX\SAMPLE\FRAN
Saving arcs...
Leaving ARCEDIT...
** NORMAL END OF CREATETICS.AML **

Then enter the tic ID number:

Type in the tic ID to assign
(or enter 0 to delete this tic, if it is wrong): |>> 1 <<|
Please wait...
Please wait...
The tic 1,1946121.721897,305039.8503293 has been added to fran.

The DIGI2SPC program runs, which converts the digitizer-inch coverage FRANADD00001 to Stateplane coordinates in a new coverage named FRANSPC00001. This runs in batch, without requiring user input. A backup copy of fran is made by incrementing the version number (first backup is fran-1, then fran-2, etc). Then an ARCEDIT session is started, to merge the new line(s) into the current coverage fran. Since the new line was digitized to overlap the parent parcel’s lines, new nodes are computed where the old and new lines cross. Here is the combined coverage (new line is purple), with zoomed-in views of the intersected arcs:

At this point, there are 2 coverages: franadd00001 (the digitizer-inch coverage of the single new line), and fran (the current parcel coverage, plus tics 1-5 added through CREATETICS):

6) ZOOM OUT (do repeatedly until you can see the View 2 area) 7) ZOOM IN (enter 2 points to zoom in on the View 2 area)

Edits are done in the order 1-9: 1) ZOOM IN (enter 2 points to zoom in on the View 1 area)

View 2

View 1

(split here)

5) VERTEX MOVE (select the purple arc, select its end point, snap it to the newly- created node on the black arc at the corner)

4) SPLIT ARC AT VERTEX (select the black arc, then click at its corner point, enter “1” to split the arc there)

3) DELETE ARC

2) DELETE ARC

9) VERTEX MOVE (select the other new arc, select its node, snap it to the node just below it)

8) DELETE ARC (the dangling end)

At the end of your edits, any dangling arcs are detected and you are forced to continue editing until there are none. Then you are prompted whether the data are OK (to save this as the current parcel coverage, or not). The final merged linework looks like this (green boxes are the areas highlighted above):

The arc-editing menu appears, and you perform edits using menu commands to cleanly join the arcs. Details of these steps can be seen in the screen log file (Appendix E). Detail areas (View 1 and 2) are indicated as green boxes in the full-screen drawing at bottom of this page.

The parcel coverage is built to reconstruct polygon topology. Then it is tested for LABELERRORS. There probably will be at least 1 labelerror, if a new parcel was created. The error(s) are highlighted with red stars where polygons are missing labels, or multiple label symbols with coverage-ID numbers for polygons with 2 or more labels. Here is the graphic for fran. The new (smaller) F140010007100 parcel has no label. Note that 1 red star appears in the center of the coverage, for the expected “Polygon 1 has 0 labels”. You ignore that one, since polygon 1 is the Universe polygon and so should not have any labels.

Note that you should not use the DRAW PINS command when editing labels because the PINs that it draws on screen reflect the values before the editing session, NOT the current values as you move, add, or delete labels. So having the DRAW PINS on as you edit labels would be confusing.

Move to here

2) ADD LABEL (click at old label location, new label is added there, enter “9” to quit ADD)

1) MOVE LABEL (select by box, click original location, click new location)

Then you do ARCEDIT commands to fix the errors- in this case, move the existing F140010007100 label to lie inside of the (now smaller) parent parcel. By moving the old label rather than adding a new label there, you save having to set some of the parcel attributes (e.g. PIN and ONAME stay the same for that label). Then add a label for the new F140010007105 parcel:

Note that if either of these PINs were multiple-polygon parcels, you would have to individually select each polygon label of the PIN and do these same changes to them. The attributes of each polygon label of the same PIN must match. After modifying the second parcel’s attributes, click “Cancel” to end FORMS. The edited fran coverage is saved and the main menu redisplays (the Parcel Update: ALL STEPS command is complete).

Edited attributes:

Starting attributes:

Do Select Box and select the other modified parcel:

Edited attributes:

Starting attributes:

FORMS is run to check/update parcel attributes. You have to select the parcel (use the Select Box command on the menu), it fills in the current attributes for that parcel, and you replace obsolete values. Use TAB key to move to the next line of the form. The values listed in the form are automatically calculated into the INFO PAT file for this coverage.

***************************************************************************************************************************
PARCEL ID OWNER ASSR ACRES COMPUTED ACRES
F140010007100 LYONS MARILYN 19.646 21.397
ADJUSTED % OF ASSR CAUV/
LAND USE SOIL ACRES ACRES ACRE CAUV ($)
CROPLAND 2 AdC2 Amanda silt loam, 6-12 % slopes 0.035 0.18 110 3.84
CROPLAND 3 AdD2 Amanda silt loam, 12-18 % slopes 0.000 0.00 100 0.04
CROPLAND 13 CdB Centerburg silt loam, 2-6 % slopes 0.129 0.66 210 27.12
PASTURE 2 AdC2 Amanda silt loam, 6-12 % slopes 4.249 21.63 110 467.35
PASTURE 3 AdD2 Amanda silt loam, 12-18 % slopes 0.223 1.13 100 22.26
PASTURE 6 BeB Bennington silt loam, 2-6 % slopes 0.218 1.11 100 21.82
PASTURE 13 CdB Centerburg silt loam, 2-6 % slopes 4.104 20.89 210 861.74
WOODLAND 2 AdC2 Amanda silt loam, 6-12 % slopes 4.043 20.58 70 283.00
WOODLAND 3 AdD2 Amanda silt loam, 12-18 % slopes 2.090 10.64 70 146.28
WOODLAND 13 CdB Centerburg silt loam, 2-6 % slopes 1.566 7.97 70 109.65
WOODLAND 38 Sh Shoals silt loam, occ. flooded 1.989 10.13 70 139.26
CPW TOTALS: 18.646 ADJUSTED ACRES 94.91 % (OF ASSR ACRES) $ 2,082.38 CAUV $ 111.68 CAUV/ADJUSTED ACRE
OTHER LANDUSE DESCRIPTION ACRES % OF ASSR ACRES TAX
Homesite 1.000 5.09 $ 0.00
ASSR OTHER LANDUSE TOTALS: 1.000 ACRES 5.09 % (OF ASSR ACRES) $ 0.00 TAX
***************************************************************************************************************************
PARCEL ID OWNER ASSR ACRES COMPUTED ACRES
F140010007105 BRIAN JACOBSON 75.084 75.062
ADJUSTED % OF ASSR CAUV/
LAND USE SOIL ACRES ACRES ACRE CAUV ($)
CROPLAND 1 AdB Amanda silt loam, 2-6 % slopes 16.369 21.80 200 3,273.72
CROPLAND 2 AdC2 Amanda silt loam, 6-12 % slopes 14.938 19.90 110 1,643.19
CROPLAND 3 AdD2 Amanda silt loam, 12-18 % slopes 0.002 0.00 100 0.24
CROPLAND 13 CdB Centerburg silt loam, 2-6 % slopes 9.548 12.72 210 2,005.11
CROPLAND 19 Co Condit silt loam 1.893 2.52 100 189.31
CROPLAND 25 Lo Lobdell silt loam, occ. flooded 1.371 1.83 300 411.38
CROPLAND 38 Sh Shoals silt loam, occ. flooded 4.233 5.64 320 1,354.58
PASTURE 2 AdC2 Amanda silt loam, 6-12 % slopes 0.152 0.20 110 16.72
PASTURE 13 CdB Centerburg silt loam, 2-6 % slopes 0.016 0.02 210 3.37
WOODLAND 1 AdB Amanda silt loam, 2-6 % slopes 1.702 2.27 70 119.14
WOODLAND 2 AdC2 Amanda silt loam, 6-12 % slopes 7.181 9.56 70 502.66
WOODLAND 3 AdD2 Amanda silt loam, 12-18 % slopes 4.696 6.25 70 328.73
WOODLAND 13 CdB Centerburg silt loam, 2-6 % slopes 2.510 3.34 70 175.69
WOODLAND 19 Co Condit silt loam 1.709 2.28 70 119.63
WOODLAND 25 Lo Lobdell silt loam, occ. flooded 0.297 0.40 70 20.80
WOODLAND 38 Sh Shoals silt loam, occ. flooded 7.466 9.94 70 522.63
CPW TOTALS: 74.084 ADJUSTED ACRES 98.67 % (OF ASSR ACRES) $10,686.91 CAUV $ 144.25 CAUV/ADJUSTED ACRE
OTHER LANDUSE DESCRIPTION ACRES % OF ASSR ACRES TAX
Homesite 1.000 1.33 $ 0.00
ASSR OTHER LANDUSE TOTALS: 1.000 ACRES 1.33 % (OF ASSR ACRES) $ 0.00 TAX

and the TAX file:

ARC/INFO TAX RUN DATE: 13 Feb 01 09:39:58 Tuesday
Coverage: franpsl
TAX listing file: FRAN.tax
TAX log file: FRAN.log
INFO file of parcel aggregate data: FRAN.TOT
INFO file of individual CPW records: FRAN.CPW
***********************************************************************
*** WARNINGS GENERATED IN THIS TAX RUN:
(no warnings were generated)

At this point, this FRAN update is complete. Since ZERO ALL INCLs was run before the update and INCL was set to 1 on these 2 altered parcels, a QTAX run can now be done to calculate taxes for just these 2 parcels. On the menu select RUN QTAX. The screen listing of the run is shown in Appendix E. After the run, if you say OK to the View Tax Results prompt, you see the .LOG file:

Running the Sample Parcel Update The sample update in the previous section can be run by you as a learning tutorial. The Morrow County, Franklin Township data resides in the \<county>\sample workspace. To run it– start ArcInfo, move to that workspace, and start the TAX Application there: Arc: w c:\morrowtax\sample Arc: tax (TAX.AML begins and displays the main menu) Then follow the printed example and/or Appendix E. Use the menu to do your own update of FRAN. Then when done (or if it fails)- run the AML named CLEANUP_SAMPLE from within the \sample workspace: Arc: &r cleanup_sample This AML restores the initial \sample workspace, ready to rerun the sample parcel update. NOTE: you cannot use the CHANGE WORKSPACE command from within the \sample workspace. Quit from the TAX Application and move to a different workspace, then restart TAX from there. Details of CAUV TAX Processing Running the TAX calculations– from the TAX menu, choose RUN QTAX:
QTAX.AML does the following steps:
a) set up and verify the input and output files
b) select parcels for TAX out of the entire township coverage
c) check them for attribute consistency
d) intersect these parcels with the township SOLU coverage to produce the
3-way overlay <twp>PSL
e) calculate TAX on the PSL coverage to produce INFO files ___.TOT and .CPW
and ASCII listings ___.TAX and .LOG
Steps b-d are done by SELTAX.AML and step e is done by CALCTAX.AML.
a) specify the input coverage and output filenames:
The input township parcel coverage is automatically known by the software.
You specify a new name <outfile> to use for the 4 output files to be created. If INFO files <outfile>.TOT or .CPW, or ASCII files <outfile>.tax or .log already exist, you are given the options to overwrite them with
this run's data or to reset <outfile> and keep the old files.

Note that after viewing these on the screen, the expanded window is not resized vertically- you have to do that yourself. After seeing that the tax run was OK, the extra 5 tics can be deleted from the new parcel coverage (using the menu DELETE TICS command). The final workspace contains many temporary files and the backup copy of fran (fran-1). You can easily clean up the workspace by choosing the menu command CLEANUP TOWNSHIP WORKSPACE” and answering Y or N to delete each temporary file as they are prompted for.

b) select parcels for the TAX run using INFO:
The parcel coverages have a numeric item INCL for use as INCLusion flag.
It must be CALC'd to value 1 for parcels which are to have TAX calculated,or to 0 for other parcels in the township. This allows partial-township runs without generating output file records for every parcel.
When running the full township, you should reselect out the non-CAUV parcels which do not have the required assessor item AACRE set.
The TAX menu commands allow you to run on all CAUV-eligible parcels, or to zero out INCL then set it just for those that you want in the run. Having set INCL, the parcel coverage is ready for the RESELECT command (QTAX does this automatically in its SELTAX.AML):
Arc: RESELECT <twp> <twp>sel poly
>: resel incl = 1
>: <carriage return>
Do you wish to re-enter expression (Y/N)? N
Do you wish to enter another expression (Y/N)? N
<n> features out of <total_n> selected
Reselecting polygons . . .
(this creates new coverage <twp>sel of just the INCL=1 polygons, plus any island polygons that they contain. Any islands with INCL=0 will be ignored by the QTAX program)
c) SELTAX.AML performs parcel attribute consistency checks.
1. For all of the PINs selected for TAX calculation, is the count of polygons in <twp>sel for each PIN value equal to the count of polygons in the full <twp> coverage for that same PIN value? If not, you have not correctly set INCL = 1 on all polygons of a multiple-polygon parcel. The AML exits without running CALCTAX, since the results would be incorrect (the computed acreage, by sum of polygons' areas, would be undercounted on these PIN(s) where not all of the polygons were selected). The problem PINs
are listed in the file SELTAX.LST - you will need to use the menu command SELECT INDIVIDUAL PINS to set INCL=1 on all polygons of the selected Parcel IDs, then rerun QTAX.
2. if there are any multiple-polygon parcels selected for the TAX calculation, SELTAX performs attribute consistency checks by copying the <twp>sel.PAT and comparing polygon records which have the same PIN value. Any PINs with 2 polygons having different values in 1 or more TAX-related PAT items are listed in a file named SELTAX.LST. The AML lists this file on the screen.
If any parcels are flagged with attribute problems:
SELTAX asks if you want to continue and run INTERSECT and TAX calculation anyway (say N unless you know that the differences are only in non-TAX PAT items). If you say N, SELTAX and QTAX exit here and return to the main menu.
You should locate and fix the attribute problems using the menu command UPDATE ATTRIBUTES.
Then restart QTAX on the corrected <twp> coverage.
Otherwise (no parcel attribute problems were found):
the output coverage from RESELECT has polygon topology and is ready to intersect with the township SOLU coverage to create the 3-way overlay of parcels-landuse-soils.

d) SELTAX intersects the attribute-checked parcels with the SOLU coverage to make the PSL overlay coverage:
Arc: INTERSECT <twp>sel <twp>solu <twp>psl poly 1
This creates the parcel-soils-landuse overlay coverage <twp>PSL with all PAT items from the parcel and SOLU coverages. It is the input coverage for the CALCTAX.AML.
e) CALCTAX.AML is run on the 3-way overlay:
CALCTAX is the INFO-based CAUV TAX computation program.
It uses the overlay coverage's PAT plus the installed INFO soils tables to do the following steps:
1) for each parcel, compare computed acreage (from the PAT's polygon areas) to assessor's acreage (from the user-maintained <twp>.PAT AACRE item) to calculate an adjustment factor
2) adjust the area of each polygon of the parcel by the adjustment factor
3) apply the CAUV rate for the soils and land use of each polygon of the parcel, multiplying the CAUV rate times adjusted acreage to assign a tax $ value to each polygon
4) aggregate the polygon statistics by parcel, then tabulate the statistics into the listing file <outfile>.tax
5) print a summary of the run and special-case warnings into <outfile>.log
The mechanics of this AML involve creating the INFO files <outfile>.TOT (total values for each parcel) and <outfile>.CPW (1 record per each parcel-soil-landuse combination, aggregates all polygonal area for each combination and does the particular area adjustment and CAUV lookup for that combination).
These 2 INFO files contain most of the data that appear in the .tax and .log files, and may be more useful than these ASCII files, depending on how the TAX results are being used. If you do not want these INFO files at all, use Arc: KILLINFO <outfile>.TOT and Arc: KILLINFO <outfile>.CPW to delete, or you can use the TAX menu CLEANUP TOWNSHIP WORKSPACE to selectively delete them.
The INFO items of these files are:
<outfile>.TOT - total values for the parcel (one .TOT record per unique PIN value in the selected parcels of this TAX run):
PIN - parcel ID
OACRES - computed acres from the coverage PAT for all polys of this PIN
OCPW - computed acres for this PIN, land use CPW codes 1-3 only
OOTHR - computed acres for this PIN, land use CPW code 4 only
OADJ - the calculated acreage adjustment value,
= AACRES / OACRES if no assr-supplied OTHER items
= ACPW / OCPW if assr-supplied OTHER items
SUM-ADJACR - sum of all polygons' adjusted (CPW 1-3) acreages for this PIN
(sum of <outfile>.CPW ADJACR item for this PIN)
SUM-CPWTAX - sum of all CPW tax values (sum of <outfile>.CPW ATAX item)
SUM-CPWTAX-AC - overall CAUV rate/acre (= SUM-CPWTAX / SUM-ADJACR)
SUM-CPWPCT - % ratio of adjusted CPW acreage to assessor's acreage
(= SUM-ADJACR / AACRES * 100, will be < 100% if no assr-supplied
OTHER items and the parcel has CPW=4, i.e. non-CPW area)
AACRES - assessor's parcel acreage (item AACRE in the <twp>.PAT)
ACPW - assessor's CPW (=AACRES - <assr-supplied OTHER landuse acreage>)
AOTHR - assessor-supplied OTHER landuse acreage for this parcel

<outfile>.TOT file format, continued-
(OTHR* items are only created if assr-supplied OTHER items are in use):
OTHR<1,2,3...>ACRES - acreage of 1st, 2nd, ... assr-supplied landuse
OTHR<1,2,3...>TAX - tax $ value assigned to this assr-supplied landuse,
item not created if this landuse has no $ value or tax rate assigned for it.
OTHR<1,2,3...>PCT - % ratio of this assr-supplied landuse's acreage to
total assessor's acreage for the parcel
SUM-OTHRTAX - sum of all OTHR*TAX for this parcel
SUM-OTHRPCT - sum of all OTHR*PCT for this parcel
(WRN items are created for all TAX runs):
WRN_AACR - flag item, = 1 if parcel has unfilled or invalid AACRE item in the parcel <twp>.PAT WRN_NOCPW - (only applicable with assr-supplied OTHER items in use):
flag item, = 1 if parcel has OCPW=0 and ACPW=0 - no acreage adjustment or CAUV calculation are done, parcel is entirely assr-supplied OTHER landuse acreage.
WRN_CPW - flag item, = 1 if parcel has only CPW=4 (OTHER) in <twp>.PAT but ACPW > 0. Therefore parcel only overlays land use code 4 but assessor says it has taxable CPW acreage. The entire parcel is recoded to CPW=1 (Cropland) and entire OACRES is adjusted
to ACPW area and taxed as cropland.
WRN_OTHR - (only applicable with assr-supplied OTHER items in use):
flag item, = 1 if parcel has OCPW > 0 but ACPW=0, assessor has entire parcel in non-CPW land uses. No adjustment or CAUV calculation are done on parcel.
WRN_PTOL - flag item, = 1 if relative difference between OACRES and AACRES exceeds the user-set tolerance % value (from TAXSETUP.SAV)
WRN_PTOL2 - flag item, = 1 if relative difference between OACRES and AACRES is within user tolerance but relative difference between OCPW and ACPW exceeds the % tolerance and one of these CPW acreages exceeds 5 acres.
<outfile>.CPW - single TAX line records (one record per unique
PIN-landuse-soil code combination in this TAX run):
PIN - parcel ID
CPW - land use code item (1,cropland 2,pasture 3,woodland 4,other)
SOI - numeric soil code (1:n, for n soils in the particular county)
ACRES - sum of polygon areas / 43560, for all polygons of this PIN-CPW-SOI combination
ADJACR - adjusted acreage (ACRES * OADJ, where OADJ is the <outfile>.TOT adjustment factor for this PIN parcel)
ATAX - $ tax value for this PIN-CPW-SOI combination
(= ADJACR * CAUV_VAL, from CAUV.INF table, for this CPW-SOI)
APCT - % of this combination's acreage in the parcel total
( = ADJACR / AACRES * 100, where AACRES is the <outfile>.TOT assr acreage for this PIN)
To view the <outfile>.TAX and/or .LOG listing, use the TAX menu LIST RESULTS command. It widens the Arc window for the wide lines. After it is done listing and returns to the menu, you have to resize your Arc window vertically.
Also you can view the .TAX file in WORD or other word-processing software. Note that with some fonts the listing's columns are altered - use Courier font to reset the columns (blank characters have same width as printed characters then).
To create a plot of the 3 tax data layers, for the entire township or for selected parcels or areas, run the TAX menu CREATE TAX PLOT command.
To create a plot of a township's parcels and PINs, run the TAX menu CREATE PIN PLOT command.

Workspace Maintenance of TAX Outputs
Use the TAX menu CLEANUP TOWNSHIP WORKSPACE command to selectively delete files. It identifies each non-essential file in the workspace and prompts you if you want it deleted. The .TAX listing files can be dragged to different directories using the Windows Explorer, or opened up in Word or other text-editing software. The .LOG and .TAX output files are plain text format (but .TAX has 132-character wide lines to it may have problems in some editors). See the documentation section "Procedural Details" for guidelines on maintaining the county and township workspaces.
Troubleshooting
If QTAX totally crashes or ends with unexplained error(s), do the following:
a) from the ARC prompt, DESCRIBE <twp> for your parcel coverage.
Be sure it is a valid coverage with Polygon Topology.
If so, do the following to rerun the QTAX with additional messages generated:
b) from the ARC prompt, type:
&ECHO &ON
&R QTAX <township_coveragename> 1 - the "1" argument will generate full screen messages for example, Arc: &R QTAX FRAN 1 (runs QTAX on the franklin township with full messages on)
c) note the screen messages at the end of the run - these should contain ARC's error or warning messages.
d) list the file named info00000 (or 00001, 2, or whatever is the highest number of info00* file) - it contains the last INFO session's screen messages.
e) call or email ODNR for help in diagnosing the problem:
Mark Anstaett (614) 265-6782
mark.anstaett@dnr.state.oh.us

Appendix A – Data / Workspace Setup
The supplied CW_TWPS.AML will create the township workspaces. It is only run once, during the initial data install. During installation, the following files must exist at the main \<COUNTY> level:
<township>, <township>SOLU, <township>SOIL coverages
files TAXSETUP.SAV, TWPS.LST, TWPS.MENU
INFO files CPW.INF, CAUV.INF, CDCONV.INF
the setup AML - CW_TWPS.AML
To setup the townships, run CW_TWPS from the Arc: prompt, at the \county level:
Arc: W
Current location: c:\morrowtax
Arc: &r cw_twps
(begins, verifies current workspace is correct)
Creating 15 township workspaces . . .
Copied benn to bennington\benn
. . .(copies data into each \<twp>)
It creates as many township workspaces as needed, then copies the parcel, SOIL, and SOLU coverages, the 3 .INF files, and TAXSETUP.SAV into the new workspace. If there is a name conflict (coverage name = township name), it renames the parcel coverage at the \COUNTY level, since that coverage will not be used
(the one within the \township workspace will be used by TAX software).
After successfully running CW_TWPS, the AML and 2 sets of township coverages may be deleted from the \COUNTY level.
See the documentation section "Data Components" for views of the directory structure.
CW_TWPS.AML reads the file TWPS.LST for the file-naming information. Records of TWPS.LST must be the following format:
<4-letter township prefix>,<township workspace name>,{full twp name, if different from workspace name}
For example:
benn,bennington - twp coverage name is "benn", soils-landuse cov is bennsolu,
creates workspace \bennington, full-township name is "BENNINGTON"
nblo,nbloomfield,NORTH BLOOMFIELD - twp coverage name is "nblo", soils-landuse cov is nblosolu,
creates workspace \nbloomfield, full-township name is "NORTH BLOOMFIELD"
The associated file TWPS.MENU is required by the TAX.AML application and has the record format:
record #) <full township name> - 1 name per record. Example: 1) BENNINGTON
2) NORTH BLOOMFIELD The record # must be 1- n, and order of townships in TWPS.MENU must match the order in TWPS.LST (put both in alphabetical order by full township name).

Appendix B –User Account Modifications for Running TAX Software
Each user who will be running this software must have a file named .arc located in their home directory. This is the standard ARC Startup File which is executed every time they run ARC. It must have the following
lines as a minimum (install_path is the drive:directory where the ODNR software is installed):
&s .odnr_path <install_path>
&amlpath %.odnr_path%
&atool %.odnr_path%
&menupath %.odnr_path%
&terminal 9999
For example: &s .odnr_path c:\morrowtax\amls &amlpath %.odnr_path% . . .
A sample .arc file has been provided with the software installation.
It can be copied to the user's %home% directory, or these required lines should be edited in if there is already an existing .arc file there.

Appendix C – Descriptions of Files in the Township Workspaces
The following are the default files installed in the township workspaces
and the file types which are created from running the TAX software:
Installed files (these are required as the minimum for a valid township workspace):
<twp> - parcel coverage (example: FRAN)
<twp>solu - soils/landuse overlay coverage (example: FRANSOLU)
<twp>soil - soils coverage (example: FRANSOIL)
TAXSETUP.SAV - file of county-specific parameters for tax runs
INFO files:
CPW.INF - lookup file of landuse codes + descriptions
CDCONV.INF - lookup file of soil codes + descriptions
CAUV.INF - $ tax rates for each C,P,W landuse within each soiltype
Files created during TAX runs (a workspace may contain any or all of these).
These files are flagged as non-essential and when the CLEANUP TOWNSHIP WORKSPACE
command is run, prompts are made to OK the deletion of each of these files:
<twp>-1, -2, -3 etc. - backup versions of the parcel coverage. Created in order (i.e. -1 was 1st created, then -2, then -3
as 1st backup version, 2nd backup version, etc.)
(example: FRAN-1, FRAN-2)
<twp>add00000, 00001, 00002 - coverages of digitized linework for parcel updates.
These are the inputs to the DIGI2SPC step and are not needed after successfully
completing the MERGE LINEWORK step.
(example: FRANADD00000)
<twp>spc00000, 00001, etc. - coverages of digitized linework, after converting them from digitizer-inch units to Stateplane coordinates (in the DIGI2SPC step). These are merged into the <twp> parcel coverage in the MERGE LINEWORK step and are not needed after successfully completing that step.
(example: FRANSPC00000)
<twp>spc00000.trf, 00001.trf, etc. -
statistics from ARC/INFO TRANSFORM command which is used in the DIGI2SPC step. If digitized linework does not merge into the parcel coverage nicely, then this file should be examined to see possibly bad fit of control points.
(example: FRANSPC00000.TRF)
_____.gra - plot files (name is specified by the user) created by the PIN PLOT or TAX PLOT commands.
They can be drawn on screen by: Arc: DRAW _____.gra 9999
or plotted by: Arc: PLOT _____.gra
(example: franpin.gra, frantax.gra)
_____.log - file of WARNING messages created by QTAX run. The filename is specified by the user for that QTAX run.
(example: FRAN.LOG)
_____.tax - file of complete tax statistics created by QTAX run. The filename is specified by the user for that QTAX run.
(example: FRAN.TAX)
log - ARC/INFO's log file (automatically created by ARC/INFO). It contains records of each ARC command with time and date listed. This file can be deleted when it becomes large - it is not used by the TAX software.

(Appendix C, continued):
INFO files created by QTAX runs:
_____.TOT - total tax values for each parcel in the QTAX run. The values in this file are reformatted and printed in the _____.TAX file. The filename is specified by the user for that QTAX run.
(example: FRAN.TOT)
_____.CPW - single line records of the _____.TAX file, one record for each unique PIN-landuse code-soil code overlay combination.
The filename is specified by the user for that QTAX run.
(example: FRAN.CPW)

Appendix D – Parcel Attributes for this County
The following INFO items are in each parcel coverage's .PAT file:
AREA, PERIMETER, <coverage>#, <coverage>-ID -
the default ARC/INFO-created items.
(PIN, ONAME, and AACRE are required and must be filled in for each PAT record):
PIN - Parcel Identification Number, the unique parcel identifier
ONAME - Owner Name
AACRE - Assessor's Acreage (the official acreage for the parcel)
(the following items are optionally supplied by the auditor. They are
acreages subtracted from the AACRE total and the remaining acreage
is processed by QTAX as Crop, Pasture, and Woodland taxable soils acreage):
HOMEACRE - additional homesite acreage (optional)
HOMEVAL - $ tax assessed for homesite
ROADACRE - roads acreage (optional)
ROADVAL - $ tax assessed for roads
OTHERACRE - unspecified OTHER landuse type (optional)
OTHERVAL - $ tax assessed for unspecified OTHER landuse type
INCL - an INCLUDE-this-parcel flag
(set to 1 if the parcel is to be included in next QTAX run,
the parcel is ignored in QTAX processing if INCL = 0)

These are the detailed screen messages for the parcel update session “Detailed Parcel Update Example– Software Steps”. Comments were added to the left side of the script. User keyboard entries are indicated by “|><|”, I.e. |>TAX<| when you typed in “TAX” within the script text. (comments): (on-screen script text):

Appendix E – Screen-Messages Script for Parcel Update Example

Arc: |> TAX <|
** ARC/INFO TAX Application - current Workspace is C:\MORROWTAX\SAMPLE
Reading in township names . . .
Choose command from main menu:
SELECT PARCELS - zeroing out all INCLs . . .
All parcel records now have INCL=0.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Choose command from main menu:
PARCEL UPDATE - running ALL steps
Setting up to DIGITIZE a new coverage of new parcel linework . . .
**Setting COORDINATE DIGITIZER and CREATing franadd00000 . . .
Creating C:\MORROWTAX\SAMPLE\FRANADD00000
Digitize a minimum of 4 tics (from digitizer).
Signal end of tic input with Tic-ID = 0
Tic-ID:1*
Tic-ID:2*
Tic-ID:3*
Tic-ID:4*
Tic-ID:5*
Tic-ID:0*
Enter initial boundary
Define the box (from digitizer)
The edit coverage is now C:\MORROWTAX\SAMPLE\FRANADD00000
Defaulting the map extent to the BND of C:\MORROWTAX\SAMPLE\FRANADD00000
Current EDITCOV is franadd00000 and COORDINATE device is DIGITIZER.
** End of ADIGI.AML **
0 element(s) for edit feature ARC
Coverage has no COGO attributes
ARCEDIT is set up to digitize new arcs, with INTERSECTARCS ALL and
NODESNAP CLOSEST .1" set. Starting ADD command:
--------------------Options--------------------
1) Vertex 2) Node 3) Curve
4) Delete vertex 5) Delete arc 6) Spline on/off
7) Square on/off 8) Digitizing Options 9) Quit
(Line) User-ID: 1 Points 0
1
2
3
4
Please wait...
(Line) User-ID: 2 Points 0
-----
1 arc(s) added to D:\MORROW_CD\TEST\FRANKLIN\FRANADD00000
** Ended ADD. Do any of your own ARCEDIT commands now,
** then type "RET" when done. You will be prompted to save data
** or reject it then.
Running TTY - do your own ARCEDIT commands, then type "ret" to return to AML:
Arcedit: |> ret <|
This new digitized data is coverage franadd00000.
Do you want to SAVE it (Y)? |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Running CREATETICS on fran. Checking fran's current tic IDs . . .
** CREATETICS PROCEDURE **
** You will be asked to assign an ID for each new tic.
Here are the current tic IDs in fran.tic
Press Enter key to see them: |>><<|
Record IDTIC
1 102
2 103
3 104
4 105
. . . . (lists other tics)
40 522
41 523
Press Enter key to continue: |>><<|
STARTING ARCEDIT . . .
Enter any other ARCEDIT startup commands (DRAWE, BACKC, BACKE), then
type "RET" when all are set:
Running TTY - do your own ARCEDIT commands, then type "ret" to return to AML:
Arcedit: |> mape * <|
Define the box
Arcedit: |> draw <|
Arcedit: |> ret <|
CREATETICS operates in a command loop. You can do your own ARCEDIT
commands, add a new tic, or QUIT at each loop iteration. To delete tics,
you have to do your own AE commands EDITF TIC, SELECT, DELETE.
Press Enter key to start the add-tic loop: |>><<|
DRAWING COVERAGES . . .
Select next command: ADD TIC AT NODE (left mouse button),
PICK FROM MENU OF ALL COMMANDS (right mouse button):
Create tic at node.
Using SELECT BOX PASSTHRU, select an arc which ends at the node:
Point to the node with the mouse and click:
Calculating exact node X,Y . . .
Type in the tic ID to assign
(or enter 0 to delete this tic, if it is wrong): |>> 1 <<|
The tic 1,1946121.721897,305039.8503293 has been added to fran.
Select next command: ADD TIC AT NODE (left mouse button),
PICK FROM MENU OF ALL COMMANDS (right mouse button):
Create tic at node.
Using SELECT BOX PASSTHRU, select an arc which ends at the node:
Point to the node with the mouse and click:
. . . (repeated steps to add tics 2-5)
Type in the tic ID to assign
(or enter 0 to delete this tic, if it is wrong): |>> 5 <<|
The tic 5,1947318.221897,301589.174548 has been added to fran.
Select next command: ADD TIC AT NODE (left mouse button),
PICK FROM MENU OF ALL COMMANDS (right mouse button):
Select a command from the menu for the next step to be done:
(1) add tic at node
(2) add tic at vertex
(3) add tic at X,Y
(4) suspend CREATETICS to do your own ARCEDIT commands (e.g. MAPE,DRAW)
(5) redraw the screen
(6) exit CREATETICS loop (for ARCEDIT QUIT options):
Redrawing FRAN . . .
Select next command: ADD TIC AT NODE (left mouse button),
PICK FROM MENU OF ALL COMMANDS (right mouse button):
Select a command from the menu for the next step to be done:
(1) add tic at node
(2) add tic at vertex
(3) add tic at X,Y
(4) suspend CREATETICS to do your own ARCEDIT commands (e.g. MAPE,DRAW)
(5) redraw the screen
(6) exit CREATETICS loop (for ARCEDIT QUIT options):
QUIT command. Do you want to save fran (Y)? |
** NORMAL END OF CREATETICS.AML **
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Running DIGI2SPC on franadd00000 to create Stateplane version franspc00000 . . .
Dumping franadd00000 tics to a temporary POINT coverage . . .
DUMPING FRANADD00000.TIC TO FILE tmp00000.tic . . .
TRANSFORMing franadd00000 to franspc00000 . . .
Transforming coordinates for coverage franadd00000
Scale (X,Y) = (421.908,427.206) Skew (degrees) = (-0.939)
Rotation (degrees) = (-0.817) Translation = (1930249.519,289889.055)
RMS Error (input,output) = (0.044,18.968)
Affine X = Ax + By + C
Y = Dx + Ey + F
A = 421.866 B = -0.908 C = 1930249.519
D = -6.018 E = 427.263 F = 289889.055
tic id input x input y
output x output y x error y error
------ ---------------- ---------------- ---------------- ----------------
1 37.709 35.928
1946121.722 305039.850 3.294 -27.026
2 40.908 35.766
1947475.933 304906.241 -1.222 18.116
3 37.491 32.040
1946040.691 303335.364 -4.112 17.576
4 37.266 28.112
1945944.390 301666.875 0.838 9.130
5 40.523 27.913
1947318.222 301589.175 1.202 -17.796
BUILDing franspc00000 . . .
Running ARCEDIT to create ADJUSTment links . . .
ADJUSTing franspc00000 . . .
Please wait...
adjusting ARCs...
Updating the adjustment structure for the second pass...
adjusting ARCs...Please wait...
Please wait...
WARNING not a graphic device
BUILDing franspc00000 . . .
Statistics from this runs conversions:
TRANSFORM of input units to preliminary output units (before ADJUST):
RMS Error (input,output) = (0.044,18.968)
(see full listing of TRANSFORM statistics in the file franspc00000.trf).
In ARCEDIT ADJUST command:
the maximum link length used was 27.22528399144 output units.
** franspc00000 has been ADJUSTed and BUILt. End of DIGI2SPC.AML **
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Creating backup copy of fran . . .
Created backup copy fran-1 from current fran.
Starting ARCEDIT to merge franspc00000 arcs into fran . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Press Enter key to GET franspc00000 arcs into fran: |>><<|
New arcs are magenta-colored.
Use menu commands to fix arc topology:
MAPE *:
Enter next menu choice:
Select the arc to delete (or NONE to override deletion):
Point to the feature to select
Enter point
Arc 1801 User-ID: 1 with 2 points
1 element(s) now selected
1 arc(s) deleted
Enter next menu choice:
Select the arc to delete (or NONE to override deletion):
Point to the feature to select
Enter point
Arc 1801 User-ID: 1 with 2 points
1 element(s) now selected
1 arc(s) deleted
Enter next menu choice:
Select the arc to SPLIT (or NONE to override deletion):
Point to the feature to select
Enter point
Arc 1800 User-ID: 165 with 3 points
1 element(s) now selected
Click on the vertex where it should be SPLIT:
Point to the vertex where the arc should be split
Enter point
Vertex 2 Arc 1800 (1946259.710,303317.205)
1 = Split 2 = Next 3 = Who
4 = Restart 9 = Quit
Enter point
Split arc 1800 User-ID: 165 at vertex 2 (1946259.710,303317.205)
Enter next menu choice:
Select the arc (or NONE to override VERTEX MOVE):
Point to the feature to select
Enter point
Arc 1804 User-ID: 1 with 4 points
1 element(s) now selected
Running VERTEX MOVE . . .
Point at vertex to move <9 to Quit>
Enter point
Vertex 1 Arc 1806 (1946259.967,303323.067) selected
1 = Select 2 = Next 3 = Who
4 = Move 9 = Quit
Enter point
Point to where to move it (9 to Stop)
Enter point
Vertex (1946259.967,303323.067) moved to (1946259.750,303316.490)
within arc 1806 User-ID: 1
Point at vertex to move <9 to Quit>
Enter point
Enter next menu choice:
Running IMAPE 2 . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Enter next menu choice:
Running IMAPE 2 . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Enter next menu choice:
Running IMAPE 2 . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Enter next menu choice:
Running IMAPE 2 . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Enter next menu choice:
MAPE *:
Enter next menu choice:
Select the arc to delete (or NONE to override deletion):
Point to the feature to select
Enter point
Arc 1803 User-ID: 1 with 2 points
1 element(s) now selected
1 arc(s) deleted
Enter next menu choice:
Select the arc (or NONE to override VERTEX MOVE):
Point to the feature to select
Enter point
Arc 1802 User-ID: 1 with 4 points
1 element(s) now selected
Running VERTEX MOVE . . .
Point at vertex to move <9 to Quit>
Enter point
Vertex 4 Arc 0 (1947454.547,304356.573) selected
1 = Select 2 = Next 3 = Who
4 = Move 9 = Quit
Enter point
Point to where to move it (9 to Stop)
Enter point
Vertex (1947454.547,304356.573) moved to (1947453.848,304344.814)
within arc 0 User-ID: 1
Point at vertex to move <9 to Quit>
Enter point
Enter next menu choice:
Do you want to SAVE the modified fran (Y)? |
Do you want to delete all temporary tics from fran (Y)? |>> n <<|
Unsplitting all arcs . . .
Saving fran . . .
BUILDing fran and checking for LABELERRORS . . .
REPORT_LABELERRS: count of labelerrors = 1
***THERE ARE 1 LABELERRORS IN fran.
Redrawing fran - note LABELERRORS in red:
Create your own windows around the LABELERRORS,
(Note that 1 red star is drawn in the center of the coverage
for "Polygon 1 has 0 labels" - ignore it)
then Press Enter key to continue: |>><<|
Current EDITFEATURE is LABEL.
Use menu commands to edit labels:
LISTing labels - using SELECT BOX to select the label to LIST:
Define the box
1 element(s) now selected
519
AREA = 3269756.63465
PERIMETER = 8296.01488
FRAN# = 521
FRAN-ID = 416
PIN = F140010007100
ONAME = LYONS MARILYN
AACRE = 94.730
HOMEACRE = 1.500
HOMEVAL = 12100
ROADACRE = 0.000
ROADVAL = 0
OTHERACRE = 0.000
OTHERVAL = 0
INCL = 1
Enter next menu choice:
MOVing labels - using SELECT BOX to select the label to move:
Define the box
1 element(s) now selected
Point to the coordinate to move from
Enter point
Point to the coordinate to move to
Enter point
Please wait...
Please wait...
1 label(s) moved
Enter next menu choice:
ADDing labels - use "9" to quit ADD command:
--------------------Options--------------------
1) Add Label 5) Delete last label 8) Digitizing Options
9) Quit
(Label) User-ID: 599 Coordinate = 1946745.288,302938.653
(Label) User-ID: 600 Coordinate =
1 label(s) added to D:\MORROW_CD\TEST\FRANKLIN\FRAN
Please wait...
Enter next menu choice:
Saving fran . . .
BUILDing fran and checking for LABELERRORS . . .
REPORT_LABELERRS: count of labelerrors = 0
Do you want to run FORMS to update parcel attributes (Y)? |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Starting ARCEDIT to update parcel attributes in fran . . .
Running FORMS to edit parcel attributes.
Check all parcels that were altered in the MERGE LINEWORK step,
** be sure to set INCL=1 on parcels that you want to run in the next TAX run.
If you want to use the menu for ARCEDIT commands, click CANCEL
and you can do label edits with the menu (then you will be returned to FORMS).
Otherwise click the CANCEL button to exit, after all updates are done:
Created form menu file aeform.menu
0 element(s) seleted, selecting all.
Do you want to use the ARCEDIT menu (N)? |
Saving fran . . .
** The parcel update is complete.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Choose command from main menu:
Running QTAX on selected parcel(s)
Enter the filename to use for outputs (for INFO <filename>.TOT and .CPW ,
and for ASCII files <filename>.TAX and .LOG): |>> FRAN <<|
*** The file FRAN.tax or .log still exists from an earlier run.
This run will delete and overwrite these files.
Do you want to reset the output filename and keep these files (Y)? |>> N <<|
Running SELTAX.AML to select and check parcels . . .
Running RESELECT on fran to create fransel . . .
Checking fransel for valid selection of polygons . . .
Running INTERSECT on fransel with fransolu to create franpsl . . .
Intersecting fransel with fransolu to create franpsl
Sorting...
Intersecting...
Assembling polygons...
Creating new labels...
Creating franpsl.PAT...
** Item "AREA" duplicated, Join File version dropped **
** Item "PERIMETER" duplicated, Join File version dropped **
** Item "AREA" duplicated, Join File version dropped **
** Item "PERIMETER" duplicated, Join File version dropped **
The 3-way overlay coverage franpsl has been created
and should be ready to run in QTAX.
Killed fransel with the ALL option
Running CALCTAX.AML to perform CAUV TAX calculations . . .
Checking polygon topology of franpsl . . .
Computing overlay statistics . . .
Computing TAX values and flagging parcels for warnings . . .
Writing FRAN.tax listing file . . .
Writing FRAN.log file of run summary messages . . .
The TAX listing file is FRAN.tax,
the run summary messages are in FRAN.log.
** End of CALCTAX.AML **
** End of QTAX.AML **
Do you want to list the QTAX results (Y)? |
Resetting screen to 132 columns wide . . .
Press Enter key to see the TAX listing: |>><<|
Press Enter key to continue: |>><<|
Resetting screen to 80 columns wide . . .
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Choose command from main menu:
Deleting temporary tics from fran . . .
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Choose command from main menu:
Quitting from TAX application . . .
** End of TAX.AML **

Start up TAX Application: ZERO ALL command: - - - - - - - - - - - - - - Parcel Update: ALL STEPS command: (DIGITIZE step) digitize 5 tics: digitize 2 points for outer boundary:

digitize the arc: (pressed Enter key to accept default, “Y”): (CREATETICS step)

ARCEDIT is set up to digitize new arcs, with INTERSECTARCS ALL and
NODESNAP CLOSEST .1" set. Starting ADD command:
--------------------Options--------------------
1) Vertex 2) Node 3) Curve
4) Delete vertex 5) Delete arc 6) Spline on/off
7) Square on/off 8) Digitizing Options 9) Quit
(Line) User-ID: 1 Points 0
1
2
3
4
Please wait...
(Line) User-ID: 2 Points 0
-----
1 arc(s) added to C:\MORROWTAX\SAMPLE\FRANADD00000
** Ended ADD. Do any of your own ARCEDIT commands now,
** then type "RET" when done. You will be prompted to save data
** or reject it then.
Running TTY - do your own ARCEDIT commands, then type "ret" to return to AML:
Arcedit: |> ret <|
This new digitized data is coverage franadd00000.
Do you want to SAVE it (Y)? |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Running CREATETICS on fran. Checking fran's current tic IDs . . .
** CREATETICS PROCEDURE **
** You will be asked to assign an ID for each new tic.
Here are the current tic IDs in fran.tic
Press Enter key to see them: |>><<|
Record IDTIC
1 102
2 103
3 104
4 105
. . . . (lists other tics)
40 522
41 523
Press Enter key to continue: |>><<|
STARTING ARCEDIT . . .
Enter any other ARCEDIT startup commands (DRAWE, BACKC, BACKE), then
type "RET" when all are set:
Running TTY - do your own ARCEDIT commands, then type "ret" to return to AML:

Reset mapextent to zoom in on the update area: left-click, define the 1st tic: (details on other tics is omitted) right-click, choose menu # 5:

Arcedit: |> mape * <|
Define the box
Arcedit: |> draw <|
Arcedit: |> ret <|
CREATETICS operates in a command loop. You can do your own ARCEDIT
commands, add a new tic, or QUIT at each loop iteration. To delete tics,
you have to do your own AE commands EDITF TIC, SELECT, DELETE.
Press Enter key to start the add-tic loop: |>><<|
DRAWING COVERAGES . . .
Select next command: ADD TIC AT NODE (left mouse button),
PICK FROM MENU OF ALL COMMANDS (right mouse button):
Create tic at node.
Using SELECT BOX PASSTHRU, select an arc which ends at the node:
Point to the node with the mouse and click:
Calculating exact node X,Y . . .
Type in the tic ID to assign
(or enter 0 to delete this tic, if it is wrong): |>> 1 <<|
The tic 1,1946121.721897,305039.8503293 has been added to fran.
Select next command: ADD TIC AT NODE (left mouse button),
PICK FROM MENU OF ALL COMMANDS (right mouse button):
Create tic at node.
Using SELECT BOX PASSTHRU, select an arc which ends at the node:
Point to the node with the mouse and click:
. . . (repeated steps to add tics 2-5)
Type in the tic ID to assign
(or enter 0 to delete this tic, if it is wrong): |>> 5 <<|
The tic 5,1947318.221897,301589.174548 has been added to fran.
Select next command: ADD TIC AT NODE (left mouse button),
PICK FROM MENU OF ALL COMMANDS (right mouse button):
Select a command from the menu for the next step to be done:
(1) add tic at node
(2) add tic at vertex
(3) add tic at X,Y
(4) suspend CREATETICS to do your own ARCEDIT commands (e.g. MAPE,DRAW)
(5) redraw the screen
(6) exit CREATETICS loop (for ARCEDIT QUIT options):
Redrawing FRAN . . .
Select next command: ADD TIC AT NODE (left mouse button),
PICK FROM MENU OF ALL COMMANDS (right mouse button):

Right-click, choose menu # 6: (pressed Enter key to accept default, “Y”): (DIGI2SPC step)

Select a command from the menu for the next step to be done:
(1) add tic at node
(2) add tic at vertex
(3) add tic at X,Y
(4) suspend CREATETICS to do your own ARCEDIT commands (e.g. MAPE,DRAW)
(5) redraw the screen
(6) exit CREATETICS loop (for ARCEDIT QUIT options):
QUIT command. Do you want to save fran (Y)? |
** NORMAL END OF CREATETICS.AML **
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Running DIGI2SPC on franadd00000 to create Stateplane version franspc00000 . . .
Dumping franadd00000 tics to a temporary POINT coverage . . .
DUMPING FRANADD00000.TIC TO FILE tmp00000.tic . . .
TRANSFORMing franadd00000 to franspc00000 . . .
Transforming coordinates for coverage franadd00000
Scale (X,Y) = (421.908,427.206) Skew (degrees) = (-0.939)
Rotation (degrees) = (-0.817) Translation = (1930249.519,289889.055)
RMS Error (input,output) = (0.044,18.968)
Affine X = Ax + By + C
Y = Dx + Ey + F
A = 421.866 B = -0.908 C = 1930249.519
D = -6.018 E = 427.263 F = 289889.055
tic id input x input y
output x output y x error y error
------ ---------------- ---------------- ---------------- ----------------
1 37.709 35.928
1946121.722 305039.850 3.294 -27.026
2 40.908 35.766
1947475.933 304906.241 -1.222 18.116
3 37.491 32.040
1946040.691 303335.364 -4.112 17.576
4 37.266 28.112
1945944.390 301666.875 0.838 9.130
5 40.523 27.913
1947318.222 301589.175 1.202 -17.796
BUILDing franspc00000 . . .
Running ARCEDIT to create ADJUSTment links . . .
ADJUSTing franspc00000 . . .
Please wait...
adjusting ARCs...

(MERGE LINEWORK step) uses menu for individual ARCEDIT commands: ZOOM IN: DELETE ARC: DELETE ARC:

Updating the adjustment structure for the second pass...
adjusting ARCs...Please wait...
Please wait...
WARNING not a graphic device
BUILDing franspc00000 . . .
Statistics from this runs conversions:
TRANSFORM of input units to preliminary output units (before ADJUST):
RMS Error (input,output) = (0.044,18.968)
(see full listing of TRANSFORM statistics in the file franspc00000.trf).
In ARCEDIT ADJUST command:
the maximum link length used was 27.22528399144 output units.
** franspc00000 has been ADJUSTed and BUILt. End of DIGI2SPC.AML **
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Creating backup copy of fran . . .
Created backup copy fran-1 from current fran.
Starting ARCEDIT to merge franspc00000 arcs into fran . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Press Enter key to GET franspc00000 arcs into fran: |>><<|
New arcs are magenta-colored.
Use menu commands to fix arc topology:
MAPE *:
Enter next menu choice:
Select the arc to delete (or NONE to override deletion):
Point to the feature to select
Enter point
Arc 1801 User-ID: 1 with 2 points
1 element(s) now selected
1 arc(s) deleted
Enter next menu choice:
Select the arc to delete (or NONE to override deletion):
Point to the feature to select
Enter point
Arc 1801 User-ID: 1 with 2 points
1 element(s) now selected
1 arc(s) deleted

SPLIT ARC AT VERTEX: VERTEX MOVE: (zoom out until you can see other area to be edited, then zoom in on it) ZOOM OUT: ZOOM OUT:

Enter next menu choice:
Select the arc to SPLIT (or NONE to override deletion):
Point to the feature to select
Enter point
Arc 1800 User-ID: 165 with 3 points
1 element(s) now selected
Click on the vertex where it should be SPLIT:
Point to the vertex where the arc should be split
Enter point
Vertex 2 Arc 1800 (1946259.710,303317.205)
1 = Split 2 = Next 3 = Who
4 = Restart 9 = Quit
Enter point
Split arc 1800 User-ID: 165 at vertex 2 (1946259.710,303317.205)
Enter next menu choice:
Select the arc (or NONE to override VERTEX MOVE):
Point to the feature to select
Enter point
Arc 1804 User-ID: 1 with 4 points
1 element(s) now selected
Running VERTEX MOVE . . .
Point at vertex to move <9 to Quit>
Enter point
Vertex 1 Arc 1806 (1946259.967,303323.067) selected
1 = Select 2 = Next 3 = Who
4 = Move 9 = Quit
Enter point
Point to where to move it (9 to Stop)
Enter point
Vertex (1946259.967,303323.067) moved to (1946259.750,303316.490)
within arc 1806 User-ID: 1
Point at vertex to move <9 to Quit>
Enter point
Enter next menu choice:
Running IMAPE 2 . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Enter next menu choice:
Running IMAPE 2 . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Enter next menu choice:

ZOOM OUT: ZOOM OUT: ZOOM IN: DELETE ARC: VERTEX MOVE: QUIT EDITING:

Running IMAPE 2 . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Enter next menu choice:
Running IMAPE 2 . . .
IMAPE modifying the MAPE range by factor of 2 . . .
Enter next menu choice:
MAPE *:
Enter next menu choice:
Select the arc to delete (or NONE to override deletion):
Point to the feature to select
Enter point
Arc 1803 User-ID: 1 with 2 points
1 element(s) now selected
1 arc(s) deleted
Enter next menu choice:
Select the arc (or NONE to override VERTEX MOVE):
Point to the feature to select
Enter point
Arc 1802 User-ID: 1 with 4 points
1 element(s) now selected
Running VERTEX MOVE . . .
Point at vertex to move <9 to Quit>
Enter point
Vertex 4 Arc 0 (1947454.547,304356.573) selected
1 = Select 2 = Next 3 = Who
4 = Move 9 = Quit
Enter point
Point to where to move it (9 to Stop)
Enter point
Vertex (1947454.547,304356.573) moved to (1947453.848,304344.814)
within arc 0 User-ID: 1
Point at vertex to move <9 to Quit>
Enter point
Enter next menu choice:
Do you want to SAVE the modified fran (Y)? |
Do you want to delete all temporary tics from fran (Y)? |>> n <<|
Unsplitting all arcs . . .

(begins label-editing session with menu of ARCEDIT commands) LIST LABEL: MOVE LABEL:

Saving fran . . .
BUILDing fran and checking for LABELERRORS . . .
REPORT_LABELERRS: count of labelerrors = 1
***THERE ARE 1 LABELERRORS IN fran.
Redrawing fran - note LABELERRORS in red:
Create your own windows around the LABELERRORS,
(Note that 1 red star is drawn in the center of the coverage
for "Polygon 1 has 0 labels" - ignore it)
then Press Enter key to continue: |>><<|
Current EDITFEATURE is LABEL.
Use menu commands to edit labels:
LISTing labels - using SELECT BOX to select the label to LIST:
Define the box
1 element(s) now selected
519
AREA = 3269756.63465
PERIMETER = 8296.01488
FRAN# = 521
FRAN-ID = 416
PIN = F140010007100
ONAME = LYONS MARILYN
AACRE = 94.730
HOMEACRE = 1.500
HOMEVAL = 12100
ROADACRE = 0.000
ROADVAL = 0
OTHERACRE = 0.000
OTHERVAL = 0
INCL = 1
Enter next menu choice:
MOVing labels - using SELECT BOX to select the label to move:
Define the box
1 element(s) now selected
Point to the coordinate to move from
Enter point
Point to the coordinate to move to
Enter point
Please wait...
Please wait...
1 label(s) moved

ADD LABEL: QUIT EDITING: (UPDATE ATTRIBUTES step) (here do the FORMS edits. Hit “Cancel” button when done): (pressed Enter key to skip further label edits): - - - - - - - - - - - - - - RUN QTAX:

Enter next menu choice:
ADDing labels - use "9" to quit ADD command:
--------------------Options--------------------
1) Add Label 5) Delete last label 8) Digitizing Options
9) Quit
(Label) User-ID: 599 Coordinate = 1946745.288,302938.653
(Label) User-ID: 600 Coordinate =
1 label(s) added to C:\MORROWTAX\SAMPLE\FRAN
Please wait...
Enter next menu choice:
Saving fran . . .
BUILDing fran and checking for LABELERRORS . . .
REPORT_LABELERRS: count of labelerrors = 0
Do you want to run FORMS to update parcel attributes (Y)? |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Starting ARCEDIT to update parcel attributes in fran . . .
Running FORMS to edit parcel attributes.
Check all parcels that were altered in the MERGE LINEWORK step,
** be sure to set INCL=1 on parcels that you want to run in the next TAX run.
If you want to use the menu for ARCEDIT commands, click CANCEL
and you can do label edits with the menu (then you will be returned to FORMS).
Otherwise click the CANCEL button to exit, after all updates are done:
Created form menu file aeform.menu
0 element(s) seleted, selecting all.
Do you want to use the ARCEDIT menu (N)? |
Saving fran . . .
** The parcel update is complete.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Choose command from main menu:
Running QTAX on selected parcel(s)
Enter the filename to use for outputs (for INFO <filename>.TOT and .CPW ,
and for ASCII files <filename>.TAX and .LOG): |>> FRAN <<|
*** The file FRAN.tax or .log still exists from an earlier run.
This run will delete and overwrite these files.
Do you want to reset the output filename and keep these files (Y)? |>> N <<|

(pressed Enter key to view results): listing .LOG and .TAX:

Running SELTAX.AML to select and check parcels . . .
Running RESELECT on fran to create fransel . . .
Checking fransel for valid selection of polygons . . .
Running INTERSECT on fransel with fransolu to create franpsl . . .
Intersecting fransel with fransolu to create franpsl
Sorting...
Intersecting...
Assembling polygons...
Creating new labels...
Creating franpsl.PAT...
** Item "AREA" duplicated, Join File version dropped **
** Item "PERIMETER" duplicated, Join File version dropped **
** Item "AREA" duplicated, Join File version dropped **
** Item "PERIMETER" duplicated, Join File version dropped **
The 3-way overlay coverage franpsl has been created
and should be ready to run in QTAX.
Killed fransel with the ALL option
Running CALCTAX.AML to perform CAUV TAX calculations . . .
Checking polygon topology of franpsl . . .
Computing overlay statistics . . .
Computing TAX values and flagging parcels for warnings . . .
Writing FRAN.tax listing file . . .
Writing FRAN.log file of run summary messages . . .
The TAX listing file is FRAN.tax,
the run summary messages are in FRAN.log.
** End of CALCTAX.AML **
** End of QTAX.AML **
Do you want to list the QTAX results (Y)? |
Resetting screen to 132 columns wide . . .
Press Enter key to see the TAX listing: |>><<|
Press Enter key to continue: |>><<|
Resetting screen to 80 columns wide . . .

- - - - - - - - - - - - - - DELETE TICS: - - - - - - - - - - - - - - EXIT:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Choose command from main menu:
Deleting temporary tics from fran . . .
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Choose command from main menu:
Quitting from TAX application . . .
** End of TAX.AML **

The software performs the following functions through the main menu:
CHANGE WORKSPACE- changes the current workspace to the selected township
ALL STEPS- run all steps of the parcel update
(or run parcel update steps individually):
DIGITIZE - digitize 4 or more tics and new linework
CREATETICS - add same 4 or more tics to current parcel coverage
DIGI2SPC - convert digitized coverage to Stateplane coordinates
MERGE LINEWORK - add new linework to the current parcel coverage, perform ARCEDIT commands to merge linework and edit polygon labels, if necessary
UPDATE ATTRIBUTES - update parcel coverage PAT attributes
ZERO ALL - set all INCL to 0
SELECT ALL - calc INCL=1 on all CAUV-eligible parcels
SELECT INDIVIDUAL PIN(s) - select PINs 1-by-1 and set INCL=1
RUN QTAX - runs Tax calculation on all selected parcels
LIST RESULTS - list the LOG and TAX listing files on the screen
LIST PARCEL - select a PIN and lists its attributes on screen
DRAW PARCEL - select a PIN and draws it centered on the screen, plus locational reference (where it is in the township)
CREATE PIN PLOT - create .gra map file of parcels and PIN text
CREATE TAX PLOT - create .gra map of all 3 data layers for selected or entire township area
DELETE TICS - deletes all temporary tics from the parcel coverage
CLEANUP TOWNSHIP WORKSPACE - prompts the user if they want to keep or delete each non-essential file
BACKUP PARCEL COVERAGES - creates a new workspace and copies all current township coverages into it
EXIT– quit the TAX application.

Cleanup temporary data

Backup parcel coverages and tax listings

Post into database

Analyze results

Calculate tax

Select parcels for tax run

Edit parcel linework and attributes

Plan parcel updates

Upgrade user accounts

Install Data and Software

Arc: &r cw_twps edit .ARC file [LIST PARCEL], [DRAW PARCEL] [Parcel Update: ALL STEPS] {[CREATE PIN PLOT]} [SELECT ALL] {or [ZERO ALL], [SELECT INDIVIDUAL PINS]} [ RUN QTAX] [LIST RESULTS] {[CREATE TAX PLOT]} ? Automate from INFO files? [BACKUP PARCEL COVERAGES]
Windows Explorer: copy .TAX files into backup directory [CLEANUP TOWNSHIP WORKSPACE]

Phase Processing Step Software Commands [ ] = menu command, { } = optional

Installation: Parcel Updates: Calculate Tax: Process Results: Workspace Maintenance:

Appendix F – County Plots
These county plots appear on the following pages:
7 1/2-minute quads and Morrow county boundary Townships and parcel coverages Townships and shaded CPW Landuse