Parcels for Reporting datasets were created to provide information in both the internal and external Assessors maps and specifically formatted for Geocortex reporting which supplies parcel summary reports.
<div style='text-align:left;'><div>Previous excel workbooks with all data necessary to rebuild all of these layers annually are located here: O:\Parcel_Updates\PARCEL_MAP_TEMPLATES\Working_Parcels_2021.xls</div><div>SQL queries have already been written and are found in the Projects folder of SQL for all exports necessary to build the excel workbook and join to parcels to create new parcel layers for assessors map and geocortex reporting.</div></div><div style='text-align:left;'><u><font color='#20b2aa'><br /></font></u></div><div style='text-align:left;'><u><font color='#20b2aa'>PARCELS FOR REPORTING</font></u></div><div style='text-align:left;'>All layers are rebuilt using newest parcel boundary layer from Cartographer once a year after certification and then again after BOW, which occur sometime in May/June - the Assessor's office needs to give GIS analyst a 2 week window to go through all processes needed for this major update. Additional changes may be done after BOE adjourns in mid-July  (appeals from the public on their tax assessment notices). Dee Dee is able to print a report that just shows the parcel numbers of those parcels that had changes occur during the BOE process. BE21 memos can be pulled for the parcels that had changes to help define what changes need to be made in the attribute table.</div><div><div style='text-align:left;'><br /></div><div style='text-align:left;'>Monthly Updates via <a href='https://doc.arcgis.com/en/arcgis-online/manage-data/manage-hosted-feature-layers.htm#APPEND' target='_blank' rel='nofollow ugc noopener noreferrer'>Append data process</a>: Run SQL Query &quot;MONTHLY_UPDATE_ALL_TABLES&quot; which pulls data from 3 different tables. Parcel master ownership, deed transfers and all addressing information. Copy all data and headers to O:\Parcel_Updates\PARCEL_MAP_TEMPLATES\Working_Updates_YYYY.xls. Run formulas to turn all deed transfer values into text format prior to using the data to append the updates to the layer in AGOL.</div><div style='text-align:left;'><br /></div><div style='text-align:left;'><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>IMAGES: Copy the images folder located here: </span><font face='Avenir Next W01, Avenir Next W00, Avenir Next, Avenir, Helvetica Neue, sans-serif'><span style='font-size:16px;'>\\V1-SERVER3\Apps\ASSESSOR\Manatron\ProvalPlus\Images and then paste to local drive. Run a renaming script to make all path names lower-case, located here GISStorage:\Parcel_Updates\PARCEL_MAP_TEMPLATES\Renaming_Images and then paste images folder in </span></font><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>\\v1-mail\D$\inetpub\wwwroot\gis. Run ANNUAL_IMAGEINDEX.sql query in SQL which pulls lrsn, extension, image_path, and image_date from GRM_Main.dbo.v_image_index. Copy all fields with headers and paste for use into Image_Template.xlsx located here: </span><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>GISStorage:\Parcel_Updates\PARCEL_MAP_TEMPLATES. Make all letters lowercase and then use the FORMULAS_Images tab to make a single lrsn/parcel record with multiple fields of all associated images.</span></div><div style='text-align:left;'><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></span></div><div style='text-align:left;'><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>ImageYN, Image11Y, Image 21Y, and Image 31Y fields need to be added to Parcels for Reporting layer to be read by GeoCortex. If there is an image associated, then ImageYN is Y, if there are 11 or more sketches associated, then Image11Y is Y, and so on.</span></div><div style='text-align:left;'><br /></div><div style='text-align:left;'><div><font color='#20b2aa'><u>ASSESSMENT VALUES</u></font></div><div>Though Assessment values are also accounted for in the Parcels for Reporting Layer, the Assessment Values layer has many-to-one which is necessary for graphs. Data from TSBv_Cadastre table in GRM Main, fields needed are PIN, TaxYear, ValueType, ValueAmount. ValueType 102/Land, 103/Improvements, 112/Total.</div><div><br /></div><div><u><font color='#20b2aa'>IMPROVEMENTS</font></u></div><div><font face='Avenir Next W01, Avenir Next W00, Avenir Next, Avenir, Helvetica Neue, sans-serif'><span style='font-size:16px;'>Improvements are many-to-one and are used for the improvements with sketches sheets in the GeoCortex report. ANNUAL_REAL_IMPROV.sql query was written to pull the majority of fields necessary for this layer, which pulls from GRM_public.dbo.real_improv. ANNUAL_FULLBATH.sql is found to be more accurate in actual number of full baths than real_improv. Before running these queries, need to be sure public Cama tables have been updated by Assessor's department. </span></font></div><div><font face='Avenir Next W01, Avenir Next W00, Avenir Next, Avenir, Helvetica Neue, sans-serif'><span style='font-size:16px;'><br /></span></font></div><div><font face='Avenir Next W01, Avenir Next W00, Avenir Next, Avenir, Helvetica Neue, sans-serif'><span style='font-size:16px;'>Create a UniqueID for each improvement record based on LRSN+PropExt (many properties have more than one improvement which has its own PropExt). This Unique ID is also created for sketches and then used to join sketch URL's to the appropriate improvement record. SketchPath.sql query is run to ascertain the sketch name and path to the sketch and then sketch images can be pulled from </span><span style='font-size:16px;'>\\V1-SERVER3\Apps\ASSESSOR\Manatron\ProvalPlus\SktImage folder and copied into \\v1-mail\D$\inetpub\wwwroot\gis to create the URL links necessary for the necessary fields.</span></font></div><div><font face='Avenir Next W01, Avenir Next W00, Avenir Next, Avenir, Helvetica Neue, sans-serif'><span style='font-size:16px;'><br /></span></font></div><div><font face='Avenir Next W01, Avenir Next W00, Avenir Next, Avenir, Helvetica Neue, sans-serif'><span style='font-size:16px;'>ImageYN, Image11Y, Image 21Y, and Image 31Y fields need to be added to be read by GeoCortex. If there is a sketch associated, then ImageYN is Y, if there are 11 or more sketches associated, then Image11Y is Y, and so on.</span></font></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></span></div></div><div style='text-align:left;'><u><font color='#20b2aa'>TAX CHARGES</font></u></div><div>Though Tax charges are also accounted for in the Parcels for Reporting Layer, the Tax Charges layer has many-to-one which is necessary for graphs. <span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Query in SQL server from TaxMaster view for each parcel for last 5 years. RevObID and LRSN are the same identifier and so a one-to-many join was performed in ArcGIS Pro based on these values. </span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>ANNUAL_TAX_MASTER.sql query is run and pulls data from GRM_Main.dbo.tsbv_TaxMaster. The fields needed are revobjid, taxyear, TaxOnlyCharges. Only need the last 5 years worth.</span></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'><br /></span></div><div><font color='#20b2aa' face='Avenir Next W01, Avenir Next W00, Avenir Next, Avenir, Helvetica Neue, sans-serif'><span style='font-size:16px;'><u>OTHER NOTES</u></span></font></div><div><span style='font-family:&quot;Avenir Next W01&quot;, &quot;Avenir Next W00&quot;, &quot;Avenir Next&quot;, Avenir, &quot;Helvetica Neue&quot;, sans-serif; font-size:16px;'>Added YES for those with Homeowners Exemption per TSBv_MODIFIERS - using standard cap and calc cap override records. Per Dee Dee Gossi: The Calc cap override is used when individual owns a parcel or parcels that has something attached to it, such as a mobile home. The calcap override is used when a personal owns two or more parcels that are &quot;under&quot; an acre.  So if one parcel is .204 acres and they own the contiguous parcel that is .113 acres I would relate this parcels and apply the calcap override so that the computer spreads the exemption appropriately over all parcels involved.  The modifier for homeowners exemption usually will say 100% of $100,000 but the computer knows not to exceed the $100,000. </span></div></div>
[]
nan
nan
nan