{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "Geometrically adjusted JCOS Land Boundaries", "description": "
Description: <\/SPAN>This is an adjusted land boundary feature class. Its intent is to 'fill the gaps' by adjusting the historic geometries in the LandBoundariesDetailed feature class to create a seamless cartographic representation of JCOS Boundaries. This feature class maintains a 1-to1 relationship with the LandBoundariesDetailed feature class in order to get accurate attribution if necessary. It also serves as the basis from which all distributed Land Boundary data will derive.<\/SPAN><\/P> <\/P> Data Type: <\/SPAN>Polygon<\/SPAN><\/P> <\/P> Sensitive: <\/SPAN>No<\/SPAN><\/P> <\/P> Update Frequency: <\/SPAN>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.<\/SPAN><\/P> <\/P> Root Data: <\/SPAN>No<\/SPAN><\/P> <\/P> Source of Origination: <\/SPAN>LandBoundariesDetailed<\/SPAN><\/P> <\/P> Creation Process: <\/SPAN>Data began as a one-for-one copy of the LandBoundariesDetailed feature class. Adjustments were made to feature geometries in the interior of park boundaries in order to eliminate topological errors and create a seamless boundary feature class. The BOUNDARY_DIFFERENCE_NOTES field indicates why a boundary was adjust if the reason is different from correcting a topological issue.<\/SPAN><\/P> <\/P> Original Projection: <\/SPAN>NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet <\/SPAN><\/P> <\/P> Business Rules:<\/SPAN><\/P> <\/P> 1. One for One relationship to LandBoundariesDetailed based on GIS_ID_PK field must be maintained in order for the Land Boundary Data Flow Process to function.<\/SPAN><\/P> <\/P> 2. Notes are added to identify why the records' spatial extent differs from the LandBoundaryDetailed related record. No note is needed to for adjustment of internal polygons.<\/SPAN><\/P> <\/P> 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.<\/SPAN><\/P> <\/P> 4. Notes Field - Business Rule which states that we track time sensitive information with a data range,<\/SPAN><\/P> <\/P> 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.<\/SPAN><\/P> <\/P> 6. As new fields are added to this data, the data is maintained within 3rd Form Normalization.<\/SPAN><\/P> <\/P> 7. Feature Class is captured in the Organizational GIS Entity-Relation Diagram (E-R Diagram).<\/SPAN><\/P> <\/P> 8. Data Location Diagram is updated when master location of the dataset changes.<\/SPAN><\/P> <\/P> 9. As new fields are added to this feature class, the field type matches data type in cell (Double, Short, Long, Text, Date).<\/SPAN><\/P> <\/P> 10. 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.<\/SPAN><\/P> <\/P> 11. Null values are to be remain populated if the data is unknown.<\/SPAN><\/P> <\/P> 12. Standard Coordinate System for data development: NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet.<\/SPAN><\/P> <\/P> 13. During the addition of a new field to the data use standard domains (for applicable feature classes).<\/SPAN><\/P> <\/P> 14. GIS_IDs that are decommissioned are not to be re-used.<\/SPAN><\/P> <\/P> 15. Records within this Feature Class must have the GIS_ID_PK field attributed at all times with a unique value.<\/SPAN><\/P> <\/P> 16. Data confidentiality policies (Sensitive Data SOP) rules are followed.<\/SPAN><\/P><\/DIV>",
"summary": "Geometrically adjusted JCOS Land Boundaries",
"title": "Data View - Land Boundaries Adjusted",
"tags": [
"Land boundaries",
"park boundaries",
"easements",
"verified acreage",
"land verification",
"Data View"
],
"type": "",
"typeKeywords": [],
"thumbnail": "",
"url": "",
"minScale": 5000000,
"maxScale": 5000,
"spatialReference": "",
"accessInformation": "Jefferson County Open Space",
"licenseInfo": ""
}