Rockfish Conservation Areas (RCAs) are closed areas for west coast groundfish fisheries and for some fisheries that may incidentally take groundfish as bycatch. The RCA boundary line is a connection of a series of GPS coordinates published in federal regulations (See 50 CFR 660.71-660.74) that are intended to approximate underwater depth contours. RCA boundaries are used in groundfish regulations to avoid interactions with certain groundfish species of concern and may change between seasons and Recreational Fishing Management Areas. Attributes:area_name: Unique name field identifying depth and location of waypoint.Fathom: Approximate depth in fathoms of waypoint.Region: Describes which of the five groundfish management zones the waypoint is in.lat_DDM: Latitude in Decimal Degrees Minutes format.lon_DDM: Longitude in Decimal Degrees Minutes format.lat_DD: Latitude in Decimal Degrees format.lon_DD: Longitude in Decimal Degrees format.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
A compilation of the vegetation data stored in the source feature dataset. Each estate has best available veg mapping as determined by PaCs Botanist, with Keith Formations and fire thresholds added. Estate includes NPWS acquired lands. To recieve further updates contact individual NPWS Region STOs. All information is best available at time of production. Fields are Description: Vegetation type as described in feature class Code: code as described in feature class PCT: added where available (If ends in * more than one community may have been listed in report, only first community was added) NSW_Class: added where available (If ends in * more than one community may have been listed in report, only first community was added) NSW_Formation: added for all polygons FormationSourceID: links to FormationSourceLUT, oultines how formation was assigned and history of changes. Veg - long integer links Fire_Veg_Type_LUT which contains Min: minimum years btw burns Max: Maximum years between burns, Adv: 1= fire advantage and Regime Source. This code is dependent on region 1000-FWR 2000 - NPR 3000 -NTR 4000 - WRR, 9000 - Standardised classes Keith classes linking to regimes defined by Bradstock. Original_id: object id in source feature class source_id: Code relating to Vegetation sourceLUTdetailing origin of vegetation feature class, any changes made PWGRegion:domain with NPWG region PWGArea:domain with NPWG area EstateName: domain with NPWG estate name, also includes offpark Hectares - calculated useing calculate geometry, GDA94 z55 Last updated August 2013, Version 5. VIS_ID 4355 Data and Resources
https://camaps.maps.arcgis.com/sharing/rest/content/items/9ddb733d48804f35a2823ef0a160575a/datahttps://camaps.maps.arcgis.com/sharing/rest/content/items/9ddb733d48804f35a2823ef0a160575a/data
Click here for metadata. This feature class was created to digitally represent the conceptual regulated area or regulations screening limit for the purpose of administering regulations under Section 28 of the Conservation Authorities Act – Prohibited Activities, Exemptions and Permits (O. Reg. 41/24). Conceptual regulated areas under O. Reg. 41/24 are created using GIS analysis proximity tools to generate a buffer zone from a prescribed set of distances (regulation allowances) corresponding to known potential hazard features such as Great Lakes, Inland Lakes, Watercourses, Wetlands, Floodplains, Unstable Bedrock, Dynamic Beaches and Areas Subject to Erosion. Each mapped feature represents a continuous region enclosed by a specific criteria or combination of hazard buffer criteria. Development activity is prohibited in these areas without a permit from Quinte Conservation. This dataset may not adequately identify all regulated areas and is for information screening purposes only. It should not be used as a screen for projects under the Planning Act (i.e. site plans, plans of subdivisions).As per Sec. 4. (5) of O. Reg. 41/24, in case of conflict regarding the boundaries of the areas where development activities are prohibited under paragraph 2 of subsection 21 (1) of the Conservation Authorities Act, the description of those areas in that paragraph and in section 2 of this Regulation prevail over the depiction of the areas in the maps referred to in subsection (1) of this section.
https://data.gov.tw/licensehttps://data.gov.tw/license
Provides 112-year 42 district specific soil and water conservation area map shp download file, including OBJECTID (object code), CLASS (type), SWCB_Name (specific soil and water conservation area name), County01 (location of county and city 01), Town01 (location of township and town 01) ), Vill01 (Village 01), County02 (County and City 02), Town02 (Town 02), Vill02 (Village 02), TWD97_X (X coordinate), TWD97_Y (Y coordinate), Administrator (management agency code), P_DATE (delineation announcement date), P_HA (delineated area), DEBRISNO (landslide potential stream number), Potential (risk level), Length (stream length (km)), R_area (catchment area (ha)), Mapid01 (located in map number 01), Mapid02 (located in map number 02), Twpark (located in the national park), TWscenic (located in the national scenic area), Basin (located in the catchment area), Sub_basin (located in the sub-catchment area), Date ( Editing date), SWCB_Plan (name of specific soil and water conservation area), Shape_Leng (perimeter of specific soil and water conservation area), Shape_Area (area of specific soil and water conservation area) and other fields
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
A compilation of the vegetation data stored in the source feature dataset. Each estate has best available veg mapping as determined by PaCs Botanist, with Keith Formations and fire thresholds added. Estate includes NPWS acquired lands. To recieve further updates contact individual NPWS Region STOs. All information is best available at time of production. Fields are Description: Vegetation type as described in feature class Code: code as described in feature class PCT: added where available (If ends in * more than one community may have been listed in report, only first community was added) NSW_Class: added where available (If ends in * more than one community may have been listed in report, only first community was added) NSW_Formation: added for all polygons FormationSourceID: links to FormationSourceLUT, oultines how formation was assigned and history of changes. Veg - long integer links Fire_Veg_Type_LUT which contains Min: minimum years btw burns Max: Maximum years between burns, Adv: 1= fire advantage and Regime Source. This code is dependent on region 1000-FWR 2000 - NPR 3000 -NTR 4000 - WRR, 9000 - Standardised classes Keith classes linking to regimes defined by Bradstock. Original_id: object id in source feature class source_id: Code relating to Vegetation sourceLUTdetailing origin of vegetation feature class, any changes made PWGRegion:domain with NPWG region PWGArea:domain with NPWG area EstateName: domain with NPWG estate name, also includes offpark Hectares - calculated useing calculate geometry, GDA94 z55 Last updated August 2013, Version 5. VIS_Id 4353
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Sugarloaf State Conservation Area Vegetation Map. A vegetation survey was undertaken within Sugarloaf State Conservation Area and adjacent lands, located near Lake Macquarie in the lower Hunter Valley of New South Wales. Multivariate cluster analysis and non-metric multi-dimensional scaling were carried out on plot-based data to classify the vegetation into twenty-four native communities, and each compared to a larger regional dataset to consolidate their regional affiliations. Although relatively small in size, this reserve conserves examples of five Endangered Ecological Communities, including Hunter Lowlands Redgum Forest, Lower Hunter Spotted Gum - Ironbark Forest, Lowland Rainforest, River Flat Eucalypt Forest on Coastal Floodplains, and Swamp Sclerophyll Forest on Coastal Floodplains. VIS_ID 3914
Aerial Information Systems, Inc. (AIS) was contracted by the Western Riverside County Regional Conservation Authority to perform an update to their original 2005 Western Riverside Vegetation Map. The project was funded through a Local Assistance Grant from the California Department of Fish and Wildlife (CDFW). The original vegetation layer was created in 2005 using a baseline image dataset created from 2000/01 Emerge imagery flown in early spring. The original map has been used to monitor and evaluate the habitat in the Western Riverside County Multi-species Habitat Conservation Plan (MSHCP). An update to the original map was needed to address changes in vegetation makeup that have occurred in the intervening years due to widespread and multiple burns in the mapping area, urban expansion, and broadly occurring vegetation succession.The update conforms to the standards set by the National Vegetation Classification System (NVCS) published in 2008 by the Federal Geographic Data Committee. (FGDC-STD-005-2008, Vegetation Subcommittee, Federal Geographic Data Committee, February 2008) The update also adheres to the vegetation types as represented in the 2008-second edition of the Manual of California Vegetation (MCV2). Extensive ground based field data both within and nearby the western Riverside County mapping area has been acquired since the completion of the project in 2005. This additional data has resulted in the reclassification of several vegetation types that are addressed in the updated vegetation map. The mapping area covers 1,017,364 acres of the original 1.2 million acres mapped in the 2005 study. The new study covers portions of the Upper Santa Ana River Valley, Perris Plain, and the foothills of the San Jacinto and Santa Ana Mountains but excludes US Forest Service land. The final geodatabase includes both an updated 2012 vegetation map and a retroactively corrected 2005 vegetation base layer. Vegetative and cartographic comparisons between the newly created 2012 image-based map and the original vegetation map produced in 2005 are described in this report.The Update mapping was performed using baseline digital imagery created in 2012 by the US Department of Agriculture – Farm Service Agency’s National Agricultural Imagery Program (NAIP). Vegetation units were mapped using the National Vegetation Classification System (NVCS) to the Alliance and Association level as depicted in the MCV2. Approximately 55% of the study area is classified to vegetated or naturally occurring sparsely vegetated types; the remaining 45% is unvegetated, with over a third (36%) in urban development and an additional 9% in agriculture. The major tasks for the Update project consisted of updating the original mapping classification to conform to the changes and refinements to the MCV2 classification, updating the existing vegetation map to 2012 conditions, retroactively correcting the 2005 vegetation interpretations, creating the final report and project metadata, and producing the final vegetation geodatabase. After completion of the original 2005 vegetation map, CDFW crosswalked the original mapping units to the NVCS hierarchical names as defined in the Manual of California Vegetation (MCV).The original crosswalk was revised during the Update effort to reflect changes in the original MCV classification as depicted in the second edition (MCV2). Changes were minor and did not result in a significant effort in the updating process. The updating process in many steps is similar to the creation of the original vegetation map. First, photo interpreters review the study area for terrain, environmental features, and probable vegetation types present. Questionable photo signatures on the new baseline imagery (2012 NAIP) were compared to the original 2000/01 Emerge imagery. Photo signatures for a given vegetation polygon were correlated between the two image datasets. Production level updates to the linework and labeling commenced following the correlation of the two baseline image datasets and the subsequent refinement of photo interpretation criteria & biogeographical descriptions of the types. Existing datasets depicting topography, fire history, climate and past vegetation gathering efforts aided photo interpreters in their delineations and floristic assignments during the updating effort. The production updating effort took approximately 11 months.
This dataset depicts the boundaries of the Bureau of Land Management's (BLM's) National Monuments (NMs) and National Conservation Areas (NCAs) in Arizona as part of the National Landscape Conservation System (NLCS) data standards. The NLCS NM NCA dataset also depicts similar land designations such as Cooperative Management and Protection Areas, Forest Reserves, and Outstanding Natural areas. The NLCS NM NCA dataset is in progress as of April 30, 2019. Only the Gila Box Riparian NCA has completed the process of legal description, map creation, certification, and submittal to Congress. The remaining NMs and NCAs are awaiting the draft of legal descriptions. As legal descriptions are finalized and certified, the NLCS dataset may require updating to ensure that the spatial footprints of the NM and NCA boundary data match their respective legal descriptions. Once the boundaries are confirmed, no further changes to the NM/NCA boundary data should be made. Boundary changes can only be made through an amendment to the legal description and direct notification to Congress. The Antiquities Act of 1906 grants the President authority to designate national monuments in order to protect “objects of historic or scientific interest.” NCAs and similarly designated lands are designated by Congress to conserve, protect, enhance, and manage public lands for the benefit and enjoyment of present and future generations. In June 2000, the Bureau of Land Management (BLM) responded to growing concern over the loss of open space by creating the NLCS. The NLCS brings into a single system some of the BLM's premier designations. By putting these lands into an organized system, the BLM hopes to increase public awareness of the scientific, cultural, educational, ecological, and other values of these NM/NCA boundaries. The Public Law (P.L.) 101-628 established Gila Box Riparian NCA; P.L. 106-538 established the Las Cienegas NCA (also Sonoita Valley Acquisition Planning District), and P.L. 100-696 established San Pedro Riparian NCA. Each of these laws required the BLM to file boundary legal descriptions and maps to Congress for each NCA. As of April 30, 2019, only the Gila Box Riparian National Conservation Area has completed legal description, map depiction, certification, and submission to Congress. All other NM/NCA have gone through review by Arizona field offices. Draft maps have been completed and are awaiting legal descriptions to be drafted with the exception of the Grand Canyon-Parashant NM. All proposed boundaries are included in this dataset. When legal descriptions are finalized and certified, minor updates may be necessary to ensure that the geospatial depiction of the NM/NCA boundary data matches the legal descriptions, after which no further changes to the geospatial NM/NCA boundary data should be made. The standards, format and language for the legal descriptions and boundary maps were developed during regular meetings of the NLCS Coordinator, geospatial specialists and the Cadastral Surveyors regarding Arizona NLCS data. Guidance was provided from Congressional required maps and legal boundary descriptions for the NLCS Designation Manual 6120 (March, 2010). Established through Presidential Proclamation, there is no requirement for BLM to file boundary legal descriptions or maps with Congress for the National Monument. However, the NLCS Coordinator and Cadastral Survey Chief decided that it was prudent to extend the boundary process to NMs.
This polygon feature class represents the spatial extent and boundaries of the BLM Alaska National Landscape Conservation System (NLCS) National Monuments, National Conservation Areas and Similar Designations.
https://reference.data.gov.uk/id/open-government-licencehttps://reference.data.gov.uk/id/open-government-licence
What is a conservation area?A conservation area is 'an area of special architectural or historic interest, the character or appearance of which it is desirable to preserve or enhance'.Conservation areas are designated (chosen) by the council. Changes within, and adjacent to, conservation areas are managed through decisions made on planning applications.Developments in conservation areas should have a neutral or positive impact on the significance of the conservation area. If there is a negative impact, the development must be shown to provide public benefits instead.An area can be designated as a conservation area for a number of different reasons. Not all conservation areas are judged to be significant for the same reasons. This means something which is an acceptable development in one area might not be an acceptable development in another area.What special controls are there in conservation areas?You will need conservation area consent from the council to demolish a building or structure (with certain exceptions) - this gives the council the chance to consider the contribution of an existing building to the area before making a decision on any proposed replacement.The alterations and extensions that you can make to your home without needing planning permission are more limited than elsewhere. You need to give the council six weeks notice before carrying out any works to trees. This gives the council the chance to decide if a tree preservation order is necessary. Remember that there are extra controls over "listed buildings". It is always best to check with the Council before doing any work, to find out what approvals you may need.Linthorpe Conservation Area Article 4(2) DirectionAlthough restrictions already exist within the conservation area, permitted development including the removal of boundary walls and gate posts, and replacement of original timber windows with u-PVC windows, does not require planning permission. Over time similar alterations have damaged the character and appearance of the conservation area. The council has therefore introduced an Article 4(2) Direction, which means that residents will now have to apply for planning permission for certain alterations that were previously permitted developments.For further information read the conservation leaflet or to check if your property is affected contact the Conservation Officer on 01642 729116 or via email to conservation@middlesbrough.gov.uk.You can also view the document which officially confirmed the Article 4 Direction in February 2010.Guidance on the care, repair and upgrading of traditional windows can be found on Historic England's traditional windows guidance.Development Control Telephone: (01642) 729377
Aerial Information Systems, Inc. (AIS) was contracted by the Coachella Valley Conservation Commission (CVCC) through a Local Assistance Grant originating from the California Department of Fish and Wildlife (CDFW) to map and describe the essential habitats for bighorn sheep monitoring within the San Jacinto-Santa Rosa Mountains Conservation Area. This effort was completed in support of the Coachella Valley Multiple Species Habitat Conservation Plan (CVMSHCP). The completed vegetation map is consistent with the California Department of Fish and Wildlife classification methodology and mapping standards. The mapping area covers 187,465 acres of existing and potential habitat on the northern slopes of the San Jacinto and Santa Rosa Mountains ranging from near sea level to over 6000 feet in elevation. The map was prepared over a baseline digital image created in 2014 by the US Department of Agriculture '' Farm Service Agency''s National Agricultural Imagery Program (NAIP). Vegetation units were mapped using the National Vegetation Classification System (NVCS) to the Alliance (and in several incidences to the Association) level (See Appendix A for more detail) as described in the second edition of the Manual of California Vegetation Second Edition (Sawyer et al, 2009). The mapping effort was supported by extensive ground-based field gathering methods using CNPS rapid assessment protocol in the adjacent areas as part of the Desert Renewable Energy Conservation Plan (DRECP) to the north and east; and by the 2012 Riverside County Multiple Species Habitat Conservation Plan vegetation map in the western portion of Riverside County adjacent to the west. These ground-based data have been classified and described for the abovementioned adjacent regions and resultant keys and descriptions for those efforts have been used in part for this project.For detailed information please refer to the following report: Menke, J. and D. Johnson. 2015. Vegetation Mapping '' Peninsular Bighorn Sheep Habitat. Final Vegetation Mapping Report. Prepared for the Coachella Valley Conservation Commission. Aerial Information Systems, Inc., Redlands, CA.
Polygon geometry with attributes displaying conservation areas as defined by the comprehensive plan, FUTUREBR, in East Baton Rouge Parish, Louisiana.Metadata
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
Data disposal services related to the protection of marine life of Lara-Toxetra. The data download process is implemented through “GML” files packages. The files can be retrieved from the directory accessible via resource “HB_Habitattop BioDirectory (gml)”. The data is also available through WMS, ersiREST, json and SOAP services. Through these services, please select the level: HB.Habitat_Lara_Toxeftra_MPA.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The Terrestrial 30x30 Conserved Areas map layer was developed by the CA Nature working group, providing a statewide perspective on areas managed for the protection or enhancement of biodiversity. Understanding the spatial distribution and extent of these durably protected and managed areas is a vital aspect of tracking and achieving the “30x30” goal of conserving 30% of California's lands and waters by 2030.
Terrestrial and Freshwater Data
• The California Protected Areas Database (CPAD), developed and managed by GreenInfo Network, is the most comprehensive collection of data on open space in California. CPAD data consists of Holdings, a single parcel or small group of parcels, such that the spatial features of CPAD correspond to ownership boundaries.
• The California Conservation Easement Database (CCED), managed by GreenInfo Network, aggregates data on lands with easements. Conservation Easements are legally recorded interests in land in which a landholder sells or relinquishes certain development rights to their land in perpetuity. Easements are often used to ensure that lands remain as open space, either as working farm or ranch lands, or areas for biodiversity protection. Easement restrictions typically remain with the land through changes in ownership.
• The Protected Areas Database of the United States (PAD-US), hosted by the United States Geological Survey (USGS), is developed in coordination with multiple federal, state, and non-governmental organization (NGO) partners. PAD-US, through the Gap Analysis Project (GAP), uses a numerical coding system in which GAP codes 1 and 2 correspond to management strategies with explicit emphasis on protection and enhancement of biodiversity. PAD-US is not specifically aligned to parcel boundaries and as such, boundaries represented within it may not align with other data sources.
• Numerous datasets representing designated boundaries for entities such as National Parks and Monuments, Wild and Scenic Rivers, Wilderness Areas, and others, were downloaded from publicly available sources, typically hosted by the managing agency.
Methodology
1. CPAD and CCED represent the most accurate location and ownership information for parcels in California which contribute to the preservation of open space and cultural and biological resources.
2. Superunits are collections of parcels (Holdings) within CPAD which share a name, manager, and access policy. Most Superunits are also managed with a generally consistent strategy for biodiversity conservation. Examples of Superunits include Yosemite National Park, Giant Sequoia National Monument, and Anza-Borrego Desert State Park.
3. Some Superunits, such as those owned and managed by the Bureau of Land Management, U.S. Forest Service, or National Park Service , are intersected by one or more designations, each of which may have a distinct management emphasis with regards to biodiversity. Examples of such designations are Wilderness Areas, Wild and Scenic Rivers, or National Monuments.
4. CPAD Superunits and CCED easements were intersected with all designation boundary files to create the operative spatial units for conservation analysis, henceforth 'Conservation Units,' which make up the Terrestrial 30x30 Conserved Areas map layer. Each easement was functionally considered to be a Superunit.
5. Each Conservation Unit was intersected with the PAD-US dataset in order to determine the management emphasis with respect to biodiversity, i.e., the GAP code. Because PAD-US is national in scope and not specifically parcel aligned with California assessors' surveys, a direct spatial extraction of GAP codes from PAD-US would leave tens of thousands of GAP code data slivers within the 30x30 Conserved Areas map. Consequently, a generalizing approach was adopted, such that any Conservation Unit with greater than 80% areal overlap with a single GAP code was uniformly assigned that code. Additionally, the total area of GAP codes 1 and 2 were summed for the remaining uncoded Conservation Units. If this sum was greater than 80% of the unit area, the Conservation Unit was coded as GAP 2.
6. Subsequent to this stage of analysis, certain Conservation Units remained uncoded, either due to the lack of a single GAP code (or combined GAP codes 1&2) overlapping 80% of the area, or because the area was not sufficiently represented in the PAD-US dataset.
7. These uncoded Conservation Units were then broken down into their constituent, finer resolution Holdings, which were then analyzed according to the above workflow.
8. Areas remaining uncoded following the two-step process of coding at the Superunit and then Holding levels were assigned a GAP code of 4. This is consistent with the definition of GAP Code 4: areas unknown to have a biodiversity management focus.
9. Greater than 90% of all areas in the Terrestrial 30x30 Conserved Areas map layer were GAP coded at the level of CPAD Superunits intersected by designation boundaries, the coarsest land units of analysis. By adopting these coarser analytical units, the Terrestrial 30X30 Conserved Areas map layer avoids hundreds of thousands of spatial slivers that result from intersecting designations with smaller, more numerous parcel records. In most cases, individual parcels reflect the management scenario and GAP status of the umbrella Superunit and other spatially coincident designations.
Tracking Conserved Areas
The total acreage of conserved areas will increase as California works towards its 30x30 goal. Some changes will be due to shifts in legal protection designations or management status of specific lands and waters. However, shifts may also result from new data representing improvements in our understanding of existing biodiversity conservation efforts. The California Nature Project is expected to generate a great deal of excitement regarding the state's trajectory towards achieving the 30x30 goal. We also expect it to spark discussion about how to shape that trajectory, and how to strategize and optimize outcomes. We encourage landowners, managers, and stakeholders to investigate how their lands are represented in the Terrestrial 30X30 Conserved Areas Map Layer. This can be accomplished by using the Conserved Areas Explorer web application, developed by the CA Nature working group. Users can zoom into the locations they understand best and share their expertise with us to improve the data representing the status of conservation efforts at these sites. The Conserved Areas Explorer presents a tremendous opportunity to strengthen our existing data infrastructure and the channels of communication between land stewards and data curators, encouraging the transfer of knowledge and improving the quality of data.
CPAD, CCED, and PAD-US are built from the ground up. Data is derived from available parcel information and submissions from those who own and manage the land. So better data starts with you. Do boundary lines require updating? Is the GAP code inconsistent with a Holding’s conservation status? If land under your care can be better represented in the Terrestrial 30X30 Conserved Areas map layer, please use this link to initiate a review. The results of these reviews will inform updates to the California Protected Areas Database, California Conservation Easement Database, and PAD-US as appropriate for incorporation into future updates to CA Nature and tracking progress to 30x30.
The U. S. Geological Survey (USGS) Airborne Height Finder (AHF) system was used to perform topographic surveys in Water Conservation Areas 2 and 3A. The AHF is a helicopter-based instrument that uses a GPS receiver, a computer, and a mechanized plumb bob to make measurements.
Attribution 3.0 (CC BY 3.0)https://creativecommons.org/licenses/by/3.0/
License information was derived automatically
This map service is for use by the public and displays key maps from the Logan Planning Scheme 2015. These maps are also available in Council’s interactive mapping tool: http://www.loganinteractivemapping.com.au/. For a full list of planning scheme maps, please refer to Council’s website: http://www.logan.qld.gov.au/planning-and-building/planning-and-development/logan-planning-scheme/
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This map was constructed using pre-existing line work from the Regional Fire Management Strategy and was then reattributed with VIS Classification plant community types (PCTs) to product a draft PCT map. Field survey has been undertaken to ground-truth this map. Existing mapping were assessed for accuracy and aligned with the existing state-wide vegetation community classification. Past vegetation surveys and existing floristic site data were supplemented by strategic data collection where necessary, to adequately describe the floristic and structural diversity of vegetation within the reserve. Project outputs may be used in park planning, operations and environmental assessments. It will provide a basis for managing threatened species, preparation of weed control strategies, management and rehabilitation plans, as well as developing appropriate fire management strategies for the protection of life and property on and surrounding the target reserve. VIS_ID 4476
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
See full Data Guide here. This layer includes polygon features that depict protected open space for towns of the Protected Open Space Mapping (POSM) project, which is administered by the Connecticut Department of Energy and Environmental Protection, Land Acquisition and Management. Only parcels that meet the criteria of protected open space as defined in the POSM project are in this layer. Protected open space is defined as: (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non-facility-based outdoor recreation, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities. Includes protected open space data for the towns of Andover, Ansonia, Ashford, Avon, Beacon Falls, Canaan, Clinton, Berlin, Bethany, Bethel, Bethlehem, Bloomfield, Bridgewater, Bolton, Brookfield, Brooklyn, Canterbury, Canton, Chaplin, Cheshire, Colchester, Colebrook, Columbia, Cornwall, Coventry, Cromwell, Danbury, Derby, East Granby, East Haddam, East Hampton, East Hartford, East Windsor, Eastford, Ellington, Enfield, Essex, Farmington, Franklin, Glastonbury, Goshen, Granby, Griswold, Groton, Guilford, Haddam, Hampton, Hartford, Hebron, Kent, Killingworth, Lebanon, Ledyard, Lisbon, Litchfield, Madison, Manchester, Mansfield, Marlborough, Meriden, Middlebury, Middlefield, Middletown, Monroe, Montville, Morris, New Britain, New Canaan, New Fairfield, New Milford, New Hartford, Newington, Newtown, Norfolk, North, Norwich, Preston, Ridgefield, Shelton, Stonington, Oxford, Plainfield, Plainville, Pomfret, Portland, Prospect, Putnam, Redding, Rocky Hill, Roxbury, Salem, Salisbury, Scotland, Seymour, Sharon, Sherman, Simsbury, Somers, South Windsor, Southbury, Southington, Sprague, Sterling, Suffield, Thomaston, Thompson, Tolland, Torrington, Union, Vernon, Wallingford, Windham, Warren, Washington, Waterbury, Watertown, West Hartford, Westbrook, Weston, Wethersfield, Willington, Wilton, Windsor, Windsor Locks, Wolcott, Woodbridge, Woodbury, and Woodstock. Additional towns are added to this list as they are completed. The layer is based on information from various sources collected and compiled during the period from March 2005 through the present. These sources include but are not limited to municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions as of the date of research at each city or town hall. The Protected Open Space layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town Assessor's lot numbering system, and system-defined (automatically generated) fields. The Protected Open Space layer has an accompanying table containing more detailed information about each feature (parcel). This table is called Protected Open Space Dat, and can be joined to Protected Open Space in ArcMap using the parcel ID (PAR_ID) field. Detailed information in the Protected Open Space Data attribute table includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the unique parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, and acreage. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygons that represent the best available locational information, and are "best fit" to the land base available for each.
The Connecticut Department of Environmental Protection's (CTDEP) Permanently Protected Open Space Phase Mapping Project Phase 1 (Protected Open Space Phase1) layer includes permanently protected open space parcels in towns in Phase 1 that meet the CTDEP's definition for this project, the Permanently Protected Open Space Mapping (CT POSM) Project. The CTDEP defines permanently protected open space as (1) Land or interest in land acquired for the permanent protection of natural features of the state's landscape or essential habitat for endangered or threatened species; or (2) Land or an interest in land acquired to permanently support and sustain non facility-based outdoor recreations, forestry and fishery activities, or other wildlife or natural resource conservation or preservation activities.
Towns in Phase 1 of the CT POSM project are situated along the CT coast and portions of the Thames River and are the following: Branford, Bridgeport, Chester, Clinton, Darien, Deep River, East Haven, East Lyme, Essex, Fairfield, Greenwich, Groton, Guilford, Hamden, Ledyard, Lyme, Madison, Milford, Montville, New Haven, New London, North Branford, North Haven, Norwalk, Norwich, Old Lyme, Old Saybrook, Orange, Preston, Shelton, Stamford, Stonington, Stratford, Waterford, West Haven, Westbrook, Westport.
For the purposes of the project a number of categories or classifications of open space have also been created. These include: Land Trust, Land Trust with buidlings, Private, Private with buildings, Utility Company, Utility Company with buildings, Federal, State, Municipal, Municipal with buildings, Conservation easement, and non-DEP State land. The layer is based on information from various sources collected and compiled during the period from August 2002 trhough October 2003. These sources include municipal Assessor's records (the Assessor's database, hard copy maps and deeds) and existing digital parcel data. The layer represents conditions on the date of research at each city or town hall.
The Protected Open Space Phase1 layer includes the parcel shape (geometry), a project-specific parcel ID based on the Town and Town's Assessor lot numbering system, and system-defined (automatically generated) fields. In addition, the Protected_Open_Space_Phase1 layer has an accompanying table containing more detailed information about each parcel's collection, standardization and storage. This table is called Protected Open Space Phase1 Data and can be joined to Protected Open Space Phase1 in ArcMap using the parcel ID (PAR_ID) field. Detailed information includes the Assessor's Map, Block and Lot numbers (the Assessor's parcel identification numbering system), the official name of the parcel (such as the park or forest name if it has one), address and owner information, the deed volume and page numbers, survey information, open space type, the project-specific parcel ID number (Par_ID), comments collected by researchers during city/town hall visits, acreage collected during site reconaissance and the data source. This layer does not include parcels that do not meet the definition of open space as defined above. Features are stored as polygon feature type that represent the best available locational information, i.e. "best fit" to the land base available for each.
Phase 1 of the Protected Open Space Mapping (POSM) Project was accomplished by a contractor using only a querying process to identify open space. The contractor obtained assessor's data from the various towns and created programs to cull open space parcels strictly by query processes. We have found many errors and omissions in the data, but at this point in the project we cannot revisit all the coastal towns. Therefore, this data is being sent with a disclaimer for accuracy. You are welcome to use it but not to publish it. Please note that we do not include any water company parcels despite them being listed as part of our criteria because we must first obtain written clarification and clearance from the U.S. Department of Homeland Security.
We have since changed our data collection method for Phase 2 of this project. DEP staff now visit each town hall and thoroughly research the land records. The project is expected to be complete by 2010.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Rockfish Conservation Areas (RCAs) are closed areas for west coast groundfish fisheries and for some fisheries that may incidentally take groundfish as bycatch. The RCA boundary line is a connection of a series of GPS coordinates published in federal regulations (See 50 CFR 660.71-660.74) that are intended to approximate underwater depth contours. RCA boundaries are used in groundfish regulations to avoid interactions with certain groundfish species of concern and may change between seasons and Recreational Fishing Management Areas.
The process of digitizing these boundary lines is as follows:
30, 40, 50, 100, and 150fm waypoint .csv files were downloaded from NOAA’s West Coast Groundfish Closed Areas website https://www.fisheries.noaa.gov/west-coast/sustainable-fisheries/west-coast-groundfish-closed-areas" STYLE="text-decoration:underline;">https://www.fisheries.noaa.gov/west-coast/sustainable-fisheries/west-coast-groundfish-closed-areas and imported into ArcGIS Pro.
Each point feature was clipped to ocean waters offshore of California and merged together.
“Fathom” was added as a field to each shapefile and populated with the corresponding depth in fathoms.
Boundary lines for each shapefile (30, 40, 50, 100, and 150 fm) were created using the “Points to line” tool.
Line Field: “area_name”.
Attribute Source: Start Point.
Transfer Fields: FID, area_name, Fathom.
Attributes:
area_name: Unique name field displaying depth and location.
Fathom: Approximate depth in fathoms of contour line.
Region: Describes which of the five groundfish management zones the section of the contour line is in.
This map service is for use by the public to assist with planning and development enquiries in the City of Logan. It includes key maps from the current version of the Logan Planning Scheme 2015, including zones and zone precincts, local plans and local plan precincts, overlays, local government infrastructure plan (LGIP) maps, and some of the key planning scheme policy (PSP) maps relating to environment (policy 3) and infrastructure (policy 5). These maps are also available as ‘interactive mapping’ in the Logan PD Hub: https://loganhub.com.au . For a full list of planning scheme maps, please refer to Council’s website: <http://www.logan.qld.gov.au/planning-and-building/planning-and-development /logan-planning-scheme/>
Rockfish Conservation Areas (RCAs) are closed areas for west coast groundfish fisheries and for some fisheries that may incidentally take groundfish as bycatch. The RCA boundary line is a connection of a series of GPS coordinates published in federal regulations (See 50 CFR 660.71-660.74) that are intended to approximate underwater depth contours. RCA boundaries are used in groundfish regulations to avoid interactions with certain groundfish species of concern and may change between seasons and Recreational Fishing Management Areas. Attributes:area_name: Unique name field identifying depth and location of waypoint.Fathom: Approximate depth in fathoms of waypoint.Region: Describes which of the five groundfish management zones the waypoint is in.lat_DDM: Latitude in Decimal Degrees Minutes format.lon_DDM: Longitude in Decimal Degrees Minutes format.lat_DD: Latitude in Decimal Degrees format.lon_DD: Longitude in Decimal Degrees format.