 |
        |
           |
|
|
|
|
************** SPECIAL DISTRICT COVERAGE DOCUMENTATION ********************* The following export files contains boundary coverages for title-32 special districts. The export files and the district coverages that they import into are: firebnd.e00 Fire Districts watbnd.e00 Water Districts sanbnd.e00 Sanitation Districts wsbnd.e00 Water and Sanitation Districts recbnd.e00 Recreation Districts metbnd.e00 Metropolitan Districts ambbnd.e00 Ambulance Districts hospbnd.e00 Hospital Districts Title-32 refers to the statute that denotes the Colorado Department of Local Affairs, Division of Local Government as being responsible for maintaining a current file of certain special district boundaries. The title-32 districts are listed above. Each district is required to notify us of any boundary changes. Boundary maps used for GIS input vary in scale, the minimum being 1:50,000. The Boundary input method usually involves digitizing from paper maps, with the occaisional use of Coordinate Geometry (COGO) or digital conversion from DXF files. The boundaries in this data set are current through Dec 31, 1996*. Special District coverage attributes: COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME 1 AREA 4 12 F 3 5 PERIMETER 4 12 F 3 9 WSBND# 4 5 B - 13 WSBND-ID 4 5 B - 17 NAME 60 60 C - 77 CNTY 3 3 I - 80 LG_ID 5 5 I - The value for LG_ID is an identification number used within the Division of Local Government. If this value contains 999 as the first three numbers than it indicates that the polygon is a possible overlap between two districts. The item CNTY contains the FIPS code for the county the district is in. NAME contains the special district's name. The special district boundary coverages are on an annual update cycle. COORDINATE SYSTEM DESCRIPTION Projection UTM Zone 13 Datum NAD83 Units METERS Spheroid GRS1980 Xshift 0.00000 Yshift 0.00000 * Disclaimer: Inaccuracies may exist due to boundary information obtained from various sources and scales. There is also the possibility that we did not receive record of a boundary change, which would therefore not be reflected in the dataset. |
Sponsored by: For information regarding advertising rates Click Here! |
Copyright© 1995-2007 MindSites Group, LLC / Privacy Policy
GeoCommunity™, Wireless Developer Network™, GIS Data Depot®, and Spatial News™
including all logos and other service marks
are registered trademarks and trade communities of
MindSites Group, LLC