Description: Metadata creation by Eric Lubell (GIS Coordinator) on 7/15/24. Current GIS Coordinator is taking over from a retired employee who curated the data for 25 years, with a varied degree of attention to detail. This is a small, rural County, and we apologize in advance for any errors.MAP - this is the last 3 digits of the parcel number and needs to be updated whenever a parcel number is changed. This field should not be null.LOT - this is typically from the plat and may or may not exist. This field, historically, has many values other than the LOT stored in it. This field has not been reliably populated and is assumed to have many errors that will eventually be fixed. No ETA on accuracy QAQC. This field can be null.BLK - current GIS Coordinator still not entirely sure what this field represents. This field can be null.SUB - this field is supposed to represent the subdivision that the parcel is contained within. This field has not been reliably populated and is assumed to have many errors that will eventually be fixed. No ETA on accuracy QAQC. This field can not be null.MAPLOC - this is a combination of data. The first 4 digits should represent the State of Colorado's Assessment Mapping and Parcel Identification ID. The next 2 digits are the PLSS Section number. I'm not exactly sure what any additional digits represent but is is common to have additional digits. It is also common to only have 4 digits and, as always, QAQC is needed and an ETA is unknown.ORDER_ - C stands for Calculated (Aliquot parts w/o survey infromation) and S stands for Survey. This field can be null and I suspect there are many errors, not really sure if it should be kept at all.MR - this is for Mineral Rights. 600s are for improvements on leased land, 700s are mineral rights, 800s are mining claims. MRO is mineral rights only. This field can be null and I suspect there are many errors, not really sure if it should be kept at all.PI - this is for Partial Interest. This field can be null and I suspect there are many errors, not really sure if it should be kept at all.MapType - clearly something related to PLSS data but I suspect this field is highly inaccurate. This field can be null and I suspect there are many errors, not really sure if it should be kept at all.ORDERNO - this field is no longer relevant and will be deleted. DELETED 8/1/24.STREETNO - the street number of the address. Some parcels have yet to be assigned an address, so this field can be null.PREDIRECTION - the direction of the address, for example W for West before something like Main Street. This field can be null.STREETNAME - the street name of the address. This field can be null but should probably be filled in more than it is.STREETTYPE - the street type, drive, circle, etc. This field can be null.UNITTYPE - field used to identify the type of unit, currently only building, common elements, hangar, lot, or unit. UNITTYPE and LOT seem to have been used interchangeably, so some QAQC needs to happen. This is primarily for multi family housing. This field can be null.UNITNAME - the number or letter assigned to the unit. This field can be null.PROPERTYCITY - the city or township where the parcel is situated. Unincorporated indicates it is on County land. This field should not be null.EXEMPT - this field identifies exempt parcels: BV is Buena Vista, CC is Chaffee County, CO is State of Colorado, OT is Other (think churches), PS is Poncha Springs, SA is Salida, SA/CC is Salida and Chaffee County, SD is School District, US is the Federal Government, DPT = Department of Property Taxation. These are tax exempt properties. This field can be null.BUSINESSNAME - no clue as to the accuracy of this data but an attempt at identifying the business that exists on the parcel. It should probably be removed from the parcel data and only remain in the exports from RealWare. This field can be null.ADDRES - the full address concatenated from the other address related fields. This field should not be null.TaxDist - the tax district of the parcel. With the exception of parcels that split a tax district, this field should be accurate as of 7/14/24. This field should not be null.AREA - this is where the area was captured from the plat map. However, it was not filled in consistently. It will be replaced with the next 4 fields for better accuracy. This field should not be null.Plat_Acres - if there is an acres value on the plat, it should be recorded here. This field can be null.GIS_Acres - calculated with geodesic value on all parcels and used as a QAQC on the plat acres (if applicable). This field should not be null.Plat_SqFt - if there is a square footage value on the plat, it should be recorded here. This field can be null.GIS_SqFt - calculated with geodesic value on all parcels and used as a QAQC on the plat square footage (if applicable). This field should not be null.NOTE_01 - field added by current GIS Coordinator to capture notes not applicable to other fields. This field was used in some cases to capture previously entered data that wasn't entered into the correct place. This field can be null.NOTE_02 - second field added by current GIS Coordinator to capture notes not applicable to other fields. This field was used in some cases to capture previously entered data that wasn't entered into the correct place. This field can be null.Added "ReceptNum" on 9/20/24 to record the reception number from the Recorder's Office.PROCESSING NOTES: Over the last six months, the current GIS Coordinator has spent significant amounts of time and effort to clean this layer up. Starting on 7/14/24, additional QA/QC and processing notes will be recorded here:7/18/24 - used Select by Attributes to identify 75 parcels where the MAP value did NOT match the last three digits of the Parcel and fixed them accordingly. PARCEL LIKE '%' || CAST(MAP AS VARCHAR(3)). This was the field calculator expression to fix the issue: !PARCEL![-3:]8/1/24 - added and attributed the Fire District and Tax District fields. Also exported the Owner table from ListBuilder so I could populate the STATUS field and the GIS_TYPE field.8/8/24 - added in the redacted accounts (Status = Redacted) so that I can be sure NOT to deliver the ownership data for these parcels in data requests. The query STATUS LIKE '%Redacted%' will identify them all.8/8/24 - Ran the Condo Search in RW and updated the GIS_TYPE field accordingly. My initial accounting of Condos in GIS came up with 554 parcels but the RW export showed 689 so much more accurate.