Description: Description: Land Boundaries for JCPOS managed and co-managed lands. These features are kept as they were originally created and may not be topoologically correct. These data are intended to maintain the historical record of individual properties that have been absorbed into the JCPOS system. This is a query of the data based on ownership by Jefferson County Parks & Open Space (and parcels where Jefferson County Parks & Open Space is a co-owner of the land). This data is intended for use for Jeffco Planning and Zoning Unified Land Use Code Zoning project.Data Type: PolygonSensitive: NoUpdate Frequency: This data is sync with the AGOL data. When edits are to this the data in this location, an update occurs the following night to the AGOL data.Root Data: NoSource of Origination: Jefferson County Parks and Open Space, Jefferson County Assessors, Surveys, Legal DescriptionsCreation Process: Data is converted from CAD drawings provided by Jefferson County Surveyor, or Jeffco Assessors Parcel data, or a combination of Survey and Parcels (Noted in source field)Original Projection: NAD_1983_StatePlane_Colorado_Central_FIPS_0502_FeetAdditional Notes: Domain for the Property_Association_FK is managed by the addition of records to the RT_Property table via running a Python Script, "PropertyAssociationDomainUpdate.py". Property and Park specific information/data is contained in the RT_Property table and can be joined to this feature class. The RT_MasterLog table has a one to many relationship with the RT_MasterLogDetailed table. The RT_MasterLogDetailed table has an in-proper one to many relationship with the Land Boundaries Detailed data. It is an in-proper relationship because it really should be a many to many relationship between RT_MasterLog and Land Boundaries Detailed table. Where One Land Boundary record can potentially relates to Many (or None) through multiple real estate projects, but the data design is a One to Many and only captures the most recent Real Estate Project from the RT_MasterLog Table.Business Rules:1. One for One relationship to LandBoundariesAdjusted based on GIS_ID_PK field must be maintained in order for the Land Boundary Data Flow Process to function.2. Use Best Acreage determined by Real Estate Team for the "Verified_Acreage" value.3. Notes Field - Business Rule which states which type of data belongs in this field. In order to be in notes field there must not be an appropriate field for value.4. Notes Field - Business Rule which states that we track time sensitive information with a data range,5. Notes Field - Business Rule which states after we get a certain amount of like data in the notes field we re-evaluate the schema of the data and add an addition field to aquate for the data.6. As new records are added to this feature class which are a part of a new park or a new uniquely named Jeffco Parks and Open Space property, subsequent records are added to the RT_Properties table to get the values added into the Property_Association Domain.7. As new fields are added to this data, the data is maintained within 3rd Form Normalization.8. Feature Class is captured in the Organizational GIS Entity-Relation Diagram (E-R Diagram).9. Data Location Diagram is updated when master location of the dataset changes.10. Dates with year only have "01/01/YYYY" populated in the Date Field (Is this business rule still applicable - CWhite - 4/15/2020).11. As new fields are added to this feature class, the field type matches data type in cell (Double, Short, Long, Text, Date).12. Metadata in ArcCatolog is kept current as changes are made to the feature class. This includes field descriptions which can be view by changing to Metadata Style - FGDC CSDGM Metadata.13. Null values are to be remain populated if the data is unknown.14. Standard Coordinate System for data development: NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet.15. During the addition of a new field to the data use standard domains (for applicable feature classes).16. When editing data features which have relationships with other feature classes, the Editor must be aware of the impacts of the edits of the Origin/Parent feature class to the Destination/Child feature class.17. GIS_IDs that are decommissioned are not to be re-used.18. Records within this Feature Class must have the GIS_ID_PK field attributed at all times with a unique value.19. Data confidentiality policies (Sensitive Data SOP) rules are followed.20. The field "VERIFIED_ACREAGE" has a precision of 3 place past the decimal. Example 0.333.
Service Item Id: c15687344f0d4b0b947c2709bee4c04c
Copyright Text: Jefferson County Parks and Open Space
Description: Description: Land Boundaries for JCPOS managed and co-managed lands. These features are kept as they were originally created and may not be topoologically correct. These data are intended to maintain the historical record of individual properties that have been absorbed into the JCPOS system. This is a query of the data based on ownership by Jefferson County Parks & Open Space (and parcels where Jefferson County Parks & Open Space is a co-owner of the land). This data is intended for use for Jeffco Planning and Zoning Unified Land Use Code Zoning project.Data Type: PolygonSensitive: NoUpdate Frequency: This data is sync with the AGOL data. When edits are to this the data in this location, an update occurs the following night to the AGOL data.Root Data: NoSource of Origination: Jefferson County Parks and Open Space, Jefferson County Assessors, Surveys, Legal DescriptionsCreation Process: Data is converted from CAD drawings provided by Jefferson County Surveyor, or Jeffco Assessors Parcel data, or a combination of Survey and Parcels (Noted in source field)Original Projection: NAD_1983_StatePlane_Colorado_Central_FIPS_0502_FeetAdditional Notes: Domain for the Property_Association_FK is managed by the addition of records to the RT_Property table via running a Python Script, "PropertyAssociationDomainUpdate.py". Property and Park specific information/data is contained in the RT_Property table and can be joined to this feature class. The RT_MasterLog table has a one to many relationship with the RT_MasterLogDetailed table. The RT_MasterLogDetailed table has an in-proper one to many relationship with the Land Boundaries Detailed data. It is an in-proper relationship because it really should be a many to many relationship between RT_MasterLog and Land Boundaries Detailed table. Where One Land Boundary record can potentially relates to Many (or None) through multiple real estate projects, but the data design is a One to Many and only captures the most recent Real Estate Project from the RT_MasterLog Table.Business Rules:1. One for One relationship to LandBoundariesAdjusted based on GIS_ID_PK field must be maintained in order for the Land Boundary Data Flow Process to function.2. Use Best Acreage determined by Real Estate Team for the "Verified_Acreage" value.3. Notes Field - Business Rule which states which type of data belongs in this field. In order to be in notes field there must not be an appropriate field for value.4. Notes Field - Business Rule which states that we track time sensitive information with a data range,5. Notes Field - Business Rule which states after we get a certain amount of like data in the notes field we re-evaluate the schema of the data and add an addition field to aquate for the data.6. As new records are added to this feature class which are a part of a new park or a new uniquely named Jeffco Parks and Open Space property, subsequent records are added to the RT_Properties table to get the values added into the Property_Association Domain.7. As new fields are added to this data, the data is maintained within 3rd Form Normalization.8. Feature Class is captured in the Organizational GIS Entity-Relation Diagram (E-R Diagram).9. Data Location Diagram is updated when master location of the dataset changes.10. Dates with year only have "01/01/YYYY" populated in the Date Field (Is this business rule still applicable - CWhite - 4/15/2020).11. As new fields are added to this feature class, the field type matches data type in cell (Double, Short, Long, Text, Date).12. Metadata in ArcCatolog is kept current as changes are made to the feature class. This includes field descriptions which can be view by changing to Metadata Style - FGDC CSDGM Metadata.13. Null values are to be remain populated if the data is unknown.14. Standard Coordinate System for data development: NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet.15. During the addition of a new field to the data use standard domains (for applicable feature classes).16. When editing data features which have relationships with other feature classes, the Editor must be aware of the impacts of the edits of the Origin/Parent feature class to the Destination/Child feature class.17. GIS_IDs that are decommissioned are not to be re-used.18. Records within this Feature Class must have the GIS_ID_PK field attributed at all times with a unique value.19. Data confidentiality policies (Sensitive Data SOP) rules are followed.20. The field "VERIFIED_ACREAGE" has a precision of 3 place past the decimal. Example 0.333.
Service Item Id: c15687344f0d4b0b947c2709bee4c04c
Copyright Text: Jefferson County Parks and Open Space