Coastal Area & Boundary Polygon:

The Coastal Area layer is a 1:24,000-scale, polygon feature-based layer that includes the land and waters that lie within the Coastal Area as defined by Connecticut General Statute (C.G.S.) 22a-94(a). Activities and actions conducted within the coastal area by Federal and State Agencies (i.e., U.S. Army Corps of Engineers (USACOE), DEP regulatory programs, and state plans and actions) must be consistent with all of the applicable standards and criteria contained in the Connecticut Coastal Management Act (C.G.S. 22a-90 to 22a-113). A subset of the Coastal Area, the Coastal Boundary, represents an area within which activities regulated or conducted by coastal municipalities must be consistent with the Coastal Management Act. As defined in this section of the statutes, the Coastal Area includes the land and water within the area delineated by the following: the westerly, southerly and easterly limits of the state's jurisdiction in Long Island Sound; the towns of Greenwich, Stamford, Darien, Norwalk, Westport, Fairfield, Bridgeport, Stratford, Shelton, Milford, Orange, West Haven, New Haven, Hamden, North Haven, East Haven, Branford, Guilford, Madison, Clinton, Westbrook, Deep River, Chester, Essex, Old Saybrook, Lyme, Old Lyme, East Lyme, Waterford, New London, Montville, Norwich, Preston, Ledyard, Groton and Stonington. This layer includes a single polygon feature defined by the boundaries described above. Attribute information is comprised of an Av_Legend to denote the coastal area. Data is compiled at 1:24,000 scale. This data is not updated.

The Coastal Boundary layer is a 1:24,000-scale, polygon feature-based layer of the legal mylar-based maps adopted by the Commissioner of the Department of Environmental Protection (DEP) (i.e., maps were adopted on a town by town basis) showing the extent of lands and coastal waters as defined by Connecticut General Statute (C.G.S.) 22a-93(5)) within Connecticut's coastal area (defined by C.G.S. 22a-94(c)). The coastal boundary is a hybrid of the original 1:24,000 version maps prepared by DEP consistent with C.G.S. 22a-94(d) (Coastal Area) and the revised boundary mapping undertaken by twenty-two coastal towns prepared pursuant to C.G.S. 22a-94(f). This layer therefore does not replace the legal maps and may not be used for legal determinations. The Coastal Boundary layer includes a single polygon feature that represents the coastal boundary. No other features are included in this layer. Data is compiled at 1:24,000 scale. Attribute information is comprised of an Av_Legend attribute and a CoastB_Flg attribute to denote the coastal boundary. Other attributes include automatically calculated Shape_Length and Shape_Area fields. This data is not updated. Any regulated activity conducted within the coastal boundary by a municipal agency (i.e., plans of development, zoning regulations, municipal coastal programs and coastal site plan review (i.e., site plans submitted to zoning commission, subdivision or resubdivision plans submitted to planning commission, application for special permit or exception to the zoning or planning commissions or zoning board of appeals, variance submitted to zoning board of appeals and a referral of a municipal project)) must be conducted in a manner consistent with the requirements of the Connecticut Coastal Management Act (CMA; C.G.S. 22a-90 to 22a-113). As the Coastal Boundary is a hybrid of the Coastal Area, all state and federal agency activities must be consistent with the requirements of the CMA. As defined in C.G.S. 22a-94(b) the coastal boundary is a "continuous line delineated on the landward side by the interior contour elevation of the one hundred year frequency coastal flood zone, as defined and determined by the National Flood Insurance Act, as amended (USC 42 Section 4101, P.L. 93-234), or a one thousand foot linear setback measured from the mean high water mark in coastal waters, or a one thousand foot linear setback measured from the inland boundary of tidal wetlands mapped under section 22a-20, whichever is farthest inland; and shall be delineated on the seaward side by the seaward extent of the jurisdiction of the state." The original boundary maps were created in 1979 on stable mylar overlay using the 1:24,000-scale US Geological Survey topographic quadrangle maps (mylar film format). The source for tidal wetland maps were the legal 1:24,000 maps (mylar format) adopted by the Commissioner of DEP and transformed to 1:24,000 mylar-scale maps by the Office of Policy and Management (OPM) using an accurate pantograph. OPM similarly converted FEMA's flood insurance maps (various scales) to a 1:24,000 mylar overlay. The inland extent of coastal waters was plotted on 1:24,000 USGS topographic maps following the procedures and sources described in The Boundary Between Saltwater and Freshwater in Connecticut, December 1978 prepared by the State of Connecticut, Department of Environmental Protection, Coastal Area Management Program. The following twenty-two towns have adopted municipal coastal boundaries: Chester, Clinton, Darien, Deep River, East Haven, Essex, Fairfield, Greenwich, Groton, Guilford, Hamden, Ledyard, Madison, Milford, New Haven, New London, North Haven, Norwalk, Old Lyme, Old Saybrook, Stamford and Waterford. The coastal boundary maps for these towns may be at different scales than the original DEP draft maps and may contain minor adjustments to the boundary as permitted in C.G.S. 22a-94(f).

MetadataThese polygon features represent the areas comprising the U.S. Outer Continental Shelf (OCS) as defined by the Bureau of Ocean Energy Management (BOEM). In the Outer Continental Shelf Lands Act (OCSLA), the term "Outer Continental Shelf" is defined as "(1) all submerged lands lying seaward and outside of the area of lands beneath navigable waters as defined in the Submerged Lands Act, and of which the subsoil and seabed appertain to the United States and are subject to its jurisdiction and control or within the exclusive economic zone of the United States and adjacent to any territory of the United States; and (2) does not include any area conveyed by Congress to a territorial government for administration (43 USC 1331).Under international law, the continental shelf extends to the outer edge of the continental margin, or to 200nm from the baseline, whichever is greater. Where the outer edge of the continental margin extends beyond 200 nm from the baseline, the outer limits of the continental shelf are determined in accordance with Article 76 of the 1982 United Nations Convention on the Law of the Sea.The outer limits of the U.S. continental shelf, in areas beyond 200 nm, are established by the U.S. Extended Continental Shelf (ECS) Project led by the Department of State, the Department of the Interior, and the National Oceanic and Atmospheric Administration (NOAA).These data are not NOT an OFFICIAL record of exact boundaries and should be used for cartographic purposes only. These data should not be used to calculate areas.

Although there are a large number of software products available for calculating landscape metrics (e.g. FRAGSTATS, landscapemetrics package in R) no tools are currently available (to my knowledge) that calculate landscape metrics directly in ArcGIS Pro. Moreover, many, if not most, landscape metrics were designed with vector data in mind, but most software calculates landscape metrics from raster data due to processing time and complexity. Scaling landscape metrics can also be tedious in some instances. This toolbox was designed to calculate attributes of patches that are easily calculated on polygons in ArcGIS (i.e. area, number of patches, Landscape Shape Index, edge density, patch size, distance to the nearest patch) and scales those calculations to coarser resolutions using Block Statistics. The tool also summarizes the relationships among metrics by using Principal Component Analysis and correlation matrices to assess relationships among variables. All variables are output to a single folder.

MetadataPlanning areas are used to support mostly the National Oil and Gas Program but also other BOEM Programs consisting of a schedule of lease sales indicating the size, timing and location of proposed leasing activity the Secretary of Interior determines will best meet national energy needs. For oil and gas lease sales the Program covers a five year period following its approval, and an area must be included in the current 5-Year Program in order to be offered for leasing. Section 18 of the OCS Lands Act prescribes the major steps involved in developing a 5-Year Program including extensive public comment steps. These polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries.These data were created in the applicable NAD83 UTM Projection and re-projected to WGS84 Geographic. Because GIS projection and topology functions can change or generalize coordinates, these GIS files are NOT an OFFICIAL record for the exact boundaries. These files are to be used for Cartographic purposes only and should not be used to calculate area.

Lesson 1. An Introduction to working with multispectral satellite data in ArcGIS Pro In which we learn: • How to unpack tar and gz files from USGS EROS • The basic map interface in ArcGIS • How to add image files • What each individual band of Landsat spectral data looks like • The difference between: o Analysis-ready data: surface reflectance and surface temperature o Landsat Collection 1 Level 3 data: burned area and dynamic surface water o Sentinel2data o ISRO AWiFS and LISS-3 data Lesson 2. Basic image preprocessing In which we learn: • How to composite using the composite band tool • How to represent composite images • All about band combinations • How to composite using raster functions • How to subset data into a rectangle • How to clip to a polygon Lesson 3. Working with mosaic datasets In which we learn: o How to prepare an empty mosaic dataset o How to add images to a mosaic dataset o How to change symbology in a mosaic dataset o How to add a time attribute o How to add a time dimension to the mosaic dataset o How to view time series data in a mosaic dataset Lesson 4. Working with and creating derived datasets In which we learn: • How to visualize Landsat ARD surface temperature • How to calculate F° from K° using ARD surface temperature • How to generate and apply .lyrx files • How to calculate an NDVI raster using ISRO LISS-3 data • How to visualize burned areas using Landsat Level 3 data • How to visualize dynamic surface water extent using Landsat Level 3 data

Geographic Information System (GIS) analyses are an essential part of natural resource management and research. Calculating and summarizing data within intersecting GIS layers is common practice for analysts and researchers. However, the various tools and steps required to complete this process are slow and tedious, requiring many tools iterating over hundreds, or even thousands of datasets. USGS scientists will combine a series of ArcGIS geoprocessing capabilities with custom scripts to create tools that will calculate, summarize, and organize large amounts of data that can span many temporal and spatial scales with minimal user input. The tools work with polygons, lines, points, and rasters to calculate relevant summary data and combine them into a single output table that can be easily incorporated into statistical analyses. These tools are useful for anyone interested in using an automated script to quickly compile summary information within all areas of interest in a GIS dataset

The Viewshed analysis layer is used to identify visible areas. You specify the places you are interested in, either from a file or interactively, and the Viewshed service combines this with Esri-curated elevation data to create output polygons of visible areas. Some questions you can answer with the Viewshed task include:What areas can I see from this location? What areas can see me?Can I see the proposed wind farm?What areas can be seen from the proposed fire tower?The maximum number of input features is 1000.Viewshed has the following optional parameters:Maximum Distance: The maximum distance to calculate the viewshed.Maximum Distance Units: The units for the Maximum Distance parameter. The default is meters.DEM Resolution: The source elevation data; the default is 90m resolution SRTM. Other options include 30m, 24m, 10m, and Finest.Observer Height: The height above the surface of the observer. The default value of 1.75 meters is an average height of a person. If you are looking from an elevation location such as an observation tower or a tall building, use that height instead.Observer Height Units: The units for the Observer Height parameter. The default is meters.Surface Offset: The height above the surface of the object you are trying to see. The default value is 0. If you are trying to see buildings or wind turbines add their height here.Surface Offset Units: The units for the Surface Offset parameter. The default is meters.Generalize Viewshed Polygons: Determine if the viewshed polygons are to be generalized or not. The viewshed calculation is based upon a raster elevation model which creates a result with stair-stepped edges. To create a more pleasing appearance, and improve performance, the default behavior is to generalize the polygons. This generalization will not change the accuracy of the result for any location more than one half of the DEM's resolution.By default, this tool currently works worldwide between 60 degrees north and 56 degrees south based on the 3 arc-second (approximately 90 meter) resolution SRTM dataset. Depending upon the DEM resolution pick by the user, different data sources will be used by the tool. For 24m, tool will use global dataset WorldDEM4Ortho (excluding the counties of Azerbaijan, DR Congo and Ukraine) 0.8 arc-second (approximately 24 meter) from Airbus Defence and Space GmbH. For 30m, tool will use 1 arc-second resolution data in North America (Canada, United States, and Mexico) from the USGS National Elevation Dataset (NED), SRTM DEM-S dataset from Geoscience Australia in Australia and SRTM data between 60 degrees north and 56 degrees south in the remaining parts of the world (Africa, South America, most of Europe and continental Asia, the East Indies, New Zealand, and islands of the western Pacific). For 10m, tool will use 1/3 arc-second resolution data in the continental United States from USGS National Elevation Dataset (NED) and approximately 10 meter data covering Netherlands, Norway, Finland, Denmark, Austria, Spain, Japan Estonia, Latvia, Lithuania, Slovakia, Italy, Northern Ireland, Switzerland and Liechtenstein from various authoritative sources.To learn more, read the developer documentation for Viewshed or follow the Learn ArcGIS exercise called I Can See for Miles and Miles. To use this Geoprocessing service in ArcGIS Desktop 10.2.1 and higher, you can either connect to the Ready-to-Use Services, or create an ArcGIS Server connection. Connect to the Ready-to-Use Services by first signing in to your ArcGIS Online Organizational Account:Once you are signed in, the Ready-to-Use Services will appear in the Ready-to-Use Services folder or the Catalog window:If you would like to add a direct connection to the Elevation ArcGIS Server in ArcGIS for Desktop or ArcGIS Pro, use this URL to connect: https://elevation.arcgis.com/arcgis/services. You will also need to provide your account credentials. ArcGIS for Desktop:ArcGIS Pro:The ArcGIS help has additional information about how to do this:Learn how to make a ArcGIS Server Connection in ArcGIS Desktop. Learn more about using geoprocessing services in ArcGIS Desktop.This tool is part of a larger collection of elevation layers that you can use to perform a variety of mapping analysis tasks.

Outer Continental Shelf (OCS) blocks serve as the legal definition for BOEM offshore boundary coordinates used to define small geographic areas within an Official Protraction Diagram (OPD) or Leasing Map (LM) for leasing and administrative purposes. These polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries. Only the most recently published paper or PDF versions of the OPDs, LMs or Supplemental Official Block Diagrams (SOBDs) should be used for official or legal purpose. These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM's enterprise GIS. However, this service in this collection has been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates, these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.

Outer Continental Shelf (OCS) blocks serve as the legal definition for BOEM offshore boundary coordinates used to define small geographic areas within an Official Protraction Diagram (OPD) for leasing and administrative purposes. These polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries. OCS blocks relate back to individual Official Protraction Diagrams (OPDs) and are not uniquely numbered. A block is uniquely described by the Protraction Number and Block Number (e.g., NK18-02, Block 6822). A full OCS block is 4800 x 4800 meters. Smaller, clipped aliquots are found along the Federal/State OCS boundary and along UTM zone borders. Only the most recently published paper or PDF versions of the OPDs or Supplemental Official Block Diagrams (SOBDs) should be used for official or legal purposes.These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM's enterprise GIS. However, this service in this collection has been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates, these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.

1. The word document "Source and processing of GIS-RS input data" contains the information of the used Sentinel-2 and DEM data and details of the followed pre-processing steps.2. Calculation of weighted average: the Geodatabase and the Toolbox can be opened in ArcGis. The model in the "WeightedAverage" tbx contains the steps to calculate the values of four vegetation indices for each pixel portion inside each plot. The resulting attribute table can be copied to excel and values/plot can be calculated using the proportional area of each polygon in proportion to the plot area. Notes: a) some very small polygons will require manual filling of the VIs value. b) Check the new location (folder) of the inputs and outputs for each step of the model (model builder).3. The following geo files are input for the model builder in ArcGis (model in the tbx) that need to be transformed into a geodatabase "WeightedAverage":- Shapefiles: all files named "Buffer_Plots_2017", "FishNet10m", "FishNet_DEM12.5", "PlotPolygones", "FishDEM30".- Raster files: all files named "SAVI_Clip", "bi_Clip", "ireci_Clip", "mtci_Clip", "ndi45_Clip", "Slope30utm", "Slope_Degree".4. Models. The R script ModelsP1 contains the information on the model selection process and parameter estimation using K-fold using the examples of two models for two ecosystem services. Use the provided excel file as input. Date Copyrighted: 2020-06-01 Date Submitted: 2020-08-19

These data contain a national scale spatial footprint of the outer boundaries of the Bureau of Ocean Energy Management’s (BOEM’s) Official Protraction Diagrams (OPDs). These polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries and are updated as needed. OPDs are mapping products produced and used by the BOEM to delineate areas available for potential offshore mineral leases, determine the State/Federal offshore boundaries, and determine the limits of revenue sharing and other boundaries to be considered when leasing offshore waters. The OPDs serve as the legal definition for BOEM offshore boundary coordinates and area descriptions. These data show only the outline of the maps that are available from BOEM. Only the most recently published paper or pdf versions of the OPDs should be used for official or legal purposes. Further information on the history of the development of OPDs can be found in OCS Report MMS 99-0006: Boundary Development on the Outer Continental Shelf.These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM's enterprise GIS. However, this service in this collection has been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates, these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.

This is a national data collection of data resources managed by the Bureau of Ocean Energy Management (BOEM) for the Outer Continental Shelf (OCS). The data collection is designated as a National Geospatial Data Asset (NGDA) and includes: OCS BOEM Offshore Boundary Lines (Submerged Lands Act Boundary, OCSLA Limit of “8(g) Zone,” and Continental Shelf Boundary), OCS Protraction Polygons - 1st Division, OCS Gulf of Mexico NAD27 Protraction Polygons - 1st Division, OCS Block Polygons - 2nd Division, OCS Gulf of Mexico NAD27 Block Polygons - 2nd Division, and Aliquot 16ths Polygons - 3rd Division.All polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries reflecting federal jurisdiction. The NAD27 Gulf of Mexico Protractions and Blocks have a different protraction and block configuration when compared to the OCS Protraction Polygons - 1st Division and OCS Block Polygons - 2nd Division. The NAD27 Gulf of Mexico data is used for Oil and Gas leasing.These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM"s enterprise GIS. However, the services in this collection have been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates,these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.Layers MetadataOCS BOEM Offshore Boundary LinesOCS Protraction Polygons - 1st DivisionOCS Gulf of Mexico NAD27 Protraction Polygons - 1st DivisionOCS Block Polygons - 2nd DivisionOCS Gulf of Mexico NAD27 Block Polygons - 2nd DivisionAliquot 16ths Polygons - 3rd Division

Lists U.S. counties designated as Low Vacancy Areas for the purposes of the Tenant-Protection Vouchers (TPV) program set-aside for low-vacancy areas.The Department of Housing and Urban Development (HUD) identifies low-vacancy areas for purposes of funding the Tenant Protection Vouchers (TPVs) set-aside for certain at-risk households in low-vacancy areas. The Department has set low-vacancy areas at the county level.Low-vacancy areas are set at the county level using occupancy rates for public housing and multifamily assisted properties. Occupancy data at the project level are obtained from the most recent Picture of Subsidized Households Report. For the purposes of the TPV set-aside, a low-vacancy area is defined to be an area with an occupancy rate for public housing and multifamily assisted properties greater than or equal to 90 percent.To ensure that vacancy rates are only counted for high quality units, the occupancy data is matched to the most recent Physical Inspection Scores data for both public housing and multifamily assisted properties. Properties with inspection scores below 60 are removed from the sample, as are properties that are missing inspection scores or occupancy rates.Project-level data is aggregated to the county level, and the total occupancy rate for each county is calculated. County-level occupancy rates are used for the determination of eligibility for TPV set-aside funding as long as at least ten units of public housing and multifamily assisted housing are included in the dataset.- Counties within a Core-Based Statistical Area (CBSA) that have less than ten units use the CBSA-level occupancy rates.- Counties outside of CBSAs with less than ten units use state-wide non-CBSA totals to calculate occupancy rates.- Counties in states with only CBSA counties or a state non-CBSA unit count below ten use national non-CBSA occupancy rates.To learn more about Low Vacancy Areas visit : https://www.huduser.gov/portal/datasets/lowvactpv.html, for questions about the spatial attribution of this dataset, please reach out to us at GISHelpdesk@hud.gov. Date of Coverage: Jun 30, 2024 - Jul 1, 2025Data Dictionary: DD_Low Vacancy Areas - Set-Aside Tenant Protection Voucher

North Dakota statewide ambulance service area polygons. The data was created in 2011 to replace an earlier dataset that was obsolete and contained topology errors. The dataset was compiled from the following data sources: North Dakota state maintained county boundaries, ambulance service area shapefiles provided by some counties, PDF files provided by some counties that showed ambulance service boundaries, and a shapefile from Bullberry Services. Update 3/30/2012: Additional attributes were added to the data to show total area of each ASA in square miles and the total population for each ASA based on the 2010 US Census. The following methodologies were used:Update 3/30/2012: To calculate area in square miles, the calculation was made in ArcGIS Desktop within a data frame where the projection was set to Albers Equal Area in order to preserve area and obtain accurate calculations.Update 3/30/2012: To calculate population totals for each ASA, the following method was used. A shapefile was obtained from the US Census that contained census block geometry with population totals for each block. For each ASA, a spatial query was performed where all census blocks whose geographic centroid was within the ASA were selected. The total population for each of these selected census blocks was then summed and appended to the ASA in question. The resulting population totals for each ASA can be considered as very close approximations of the actual population totals. This is because census block polygons do not precisely match ASA boundaries. In most cases ASA boundaries and census block boundaries do match each other but in some cases they do not. In such cases, the total for the block in question is added to the sum of the ASA where the block centroid falls within. Because census block geographies are much smaller than ASA geographies, the "error" introduced with this method is estimated to be small. Furthermore, given available data, this is considered the best approximation of the true total polulation for each ASA short of conduction a new census based on ASA polygons.Williams County GIS downloaded this data on 2/10/2021 from the NDGISHUB website. It was then edited to show only the areas that touch Williams County.

Summary: This dataset contains an inventory of City of Los Angeles Sidewalks and related features (Access Ramps, Curbs, Driveways, and Parkways).Background: This inventory was performed throughout 2017 using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines. The dataset has not been updated since its creation.Description: The following provides more detail about the feature classes in this dataset. All features were digitized (“traced”) as observed in the orthophotography (digital aerial photos) and assigned the Parcel Identification Number (PIN) of their corresponding property:Sidewalk (polygon) – represents paved pedestrian walkways. Typical widths are between 3‐6 feet in residential areas and larger and more variable in commercial and high‐density traffic areas.Alley-Sidewalk (polygon) – represents the prevailing walkway or path of travel at the entrance/exit of an alley. Digitized as Sidewalk features but categorized as Alley Sidewalk and assigned a generic PIN value, ALLEY SIDEWALK.Corner Polygon (polygon) - feature created where sidewalks from two streets meet but do not intersect (i.e. at corner lots). There’s no standard shape/type and configurations vary widely. These are part of the Sidewalk feature class.In commercial and high‐density residential areas where there is only continuous sidewalk (no parkway strip), the sidewalk also functions as a Driveway.Driveway (polygon) – represents area that provides vehicular access to a property. Features are not split by extended parcel lot lines except when two adjacent properties are served by the same driveway approach (e.g. a common driveway), in which case they are and assigned a corresponding PIN.Parkway (polygon) – represents the strip of land behind the curb and in front of the sidewalk. Generally, they are landscaped with ground cover but they may also be filled in with decorative stone, pavers, decomposed granite, or concrete. They are created by offsetting lines, the Back of Curb (BOC) line and the Face of Walk (FOW). The distance between the BOC and FOW is measured off the aerial image and rounded to the nearest 0.5 foot, typically 6 – 10 feet.Curb (polygon) – represents the concrete edging built along the street to form part of the gutter. Features are always 6” wide strips and are digitized using the front of curb and back of curb digitized lines. They are the leading improvement polygon and are created for all corner, parkway, driveway and, sidewalk (if no parkway strip is present) features.Curb Ramp, aka Access Ramp (point) – represents the geographic center (centroid) of Corner Polygon features in the Sidewalk feature class. They have either a “Yes” or “No” attribute that indicates the presence or absence of a wheelchair access ramp, respectively.Fields: All features include the following fields...FeatureID – a unique feature identifier that is populated using the feature class’ OBJECTID fieldAssetID – a unique feature identifier populated by Los Angeles City staff for internal usePIND – a unique Parcel Identification Number (PIN) for all parcels within the City of L.A. All Sidewalk related features will be split, non-overlapping, and have one associated Parcel Identification Number (PIN). CreateDate – indicates date feature was createdModifiedDate – indicates date feature was revised/editedCalc_Width (excluding Access Ramps) – a generalized width of the feature calculated using spatial and mathematical algorithms on the feature. In almost all cases where features have variable widths, the minimum width is used. Widths are rounded to the nearest whole number. In cases where there is no value for the width, the applied algorithms were unable to calculate a reliable value.Calc_Length (excluding Access Ramps) – a generalized length of the feature calculated using spatial and mathematical algorithms on the feature. Lengths are rounded to the nearest whole number. In cases where there is no value for the length, the applied algorithms were unable to calculate a reliable value.Methodology: This dataset was digitized using a combination of G.I.S software, aerial imagery (2014 LARIAC), and a geographic dataset of property/right-of way lines.The general work flow is as follows:Create line work based on digital orthophotography, working from the face‐of‐curb (FOC) inward to the property right-of-way (ROW)Build sidewalk, parkway, driveway, and curb polygons from the digitized line workPopulate all polygons with the adjacent property PIN and classify all featuresCreate Curb Ramp pointsWarnings: This dataset has been provided to allow easy access and a visual display of Sidewalk and related features (Parkways, Driveway, Curb Ramps and Curbs). Every reasonable effort has been made to assure the accuracy of the data provided; nevertheless, some information may not be accurate. The City of Los Angeles assumes no responsibility arising from use of this information. THE MAPS AND ASSOCIATED DATA ARE PROVIDED WITHOUT WARRANTY OF ANY KIND, either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Other things to keep in mind about this dataset are listed below:Obscured Features – The existence of dense tree canopy or dark shadows in the aerial imagery tend to obscure or make it difficult to discern the extent of certain features, such as Driveways. In these cases, they may have been inferred from the path in the corresponding parcel. If a feature and approach was completely obscured, it was not digitized. In certain instances the coloring of the sidewalk and adjacent pavement rendered it impossible to identify the curb line or that a sidewalk existed. Therefore a sidewalk may or may not be shown where one actually may or may not exist.Context: The following links provide information on the policy context surrounding the creation of this dataset. It includes links to City of L.A. websites:Willits v. City of Los Angeles Class Action Lawsuit Settlementhttps://www.lamayor.org/willits-v-city-la-sidewalk-settlement-announcedSafe Sidewalks LA – program implemented to repair broken sidewalks in the City of L.A., partly in response to the above class action lawsuit settlementhttps://sidewalks.lacity.org/Data Source: Bureau of EngineeringNotes: Please be aware that this dataset is not actively being maintainedLast Updated: 5/20/20215/20/2021 - Added Calc_Width and Calc_Length fieldsRefresh Rate: One-time deliverable. Dataset not actively being maintained.

These data contain a Gulf of Mexico OCS Region NAD27 scale spatial footprint of the outer boundaries of the Bureau of Ocean Energy Management’s (BOEM’s) Official Protraction Diagrams (OPDs) and Leasing Maps (LMs). These polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries and are updated as needed. OPDs are mapping products produced and used by the BOEM to delineate areas available for potential offshore mineral leases, determine the State/Federal offshore boundaries, and determine the limits of revenue sharing and other boundaries to be considered when leasing offshore waters. The OPDs serve as the legal definition for BOEM offshore boundary coordinates and area descriptions. These data show only the outline of the maps that are available from BOEM. Only the most recently published paper or pdf versions of the OPDs should be used for official or legal purposes. Further information on the history of the development of OPDs can be found in OCS Report MMS 99-0006: Boundary Development on the Outer Continental Shelf.These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM's enterprise GIS. However, this service in this collection has been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates, these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.

Outer Continental Shelf (OCS) blocks serve as the legal definition for BOEM offshore boundary coordinates used to define small geographic areas within an Official Protraction Diagram (OPD) or Leasing Map (LM) for leasing and administrative purposes. These polygons are clipped to the Submerged Land Act Boundary and Continental Shelf Boundaries. Only the most recently published paper or PDF versions of the OPDs, LMs or Supplemental Official Block Diagrams (SOBDs) should be used for official or legal purpose. These data were created in the applicable NAD83 UTM or NAD27 UTM/SPCS Projection and re-projected to GCS WGS84 (EPSG 4326) for management in BOEM's enterprise GIS. However, this service in this collection has been published in WGS 1984 Web Mercator Auxiliary Sphere (EPSG 3857). Because GIS projection and topology functions can change or generalize coordinates, these data are NOT an OFFICIAL record for the exact boundaries. These data are to be used for Cartographic purposes only and should not be used to calculate area.

Tabular Summaries - Communities at Risk As part of Montana DNRC’s Montana Wildfire Risk Assessment (MWRA), wildfire risk to homes, commercial buildings, and other structures was assessed across the state. The purpose of this assessment is to identify the counties and communities whose structures are most threatened by wildfire—both on average and in total. The risk-to-structures methods used for this assessment are identical to the methods used for structures within the overall MWRA project. See earlier section 3.4.1 of the report (page 20) for details. This portion of the report addresses only the tabular summaries. The summary methods used in this section were customized to the MWRA results from similar methods previously developed for the Pacific Northwest Risk Assessment (PNRA) and for the national Wildfire Risk to Communities (WRC) project.  Mean Risk to Structures We calculated the Mean Risk to Structures as the product of Mean Conditional Risk to Structures and Mean Burn Probability (multiplied by 1000 to remove decimal places). This is the primary variable by which the summary polygons are ranked. Like the components used to calculate it, Mean Risk to Structures is not a cumulative measure for a summary polygon, so it does not necessarily increase as the number or importance of structures increases. It represents the average of the structures in the polygon regardless of the total number or importance of structures. Total Structure Risk We calculated Total Structure Risk as the product of Mean Risk to Structures and Total Structure Importance. This is the secondary variable by which the summary polygons are ranked. Unlike the previous measures, the total importance of structures (their number and mean importance) strongly influences Total Structure Risk. The risk-to-structures results were summarized for two primary sets of summary polygons: MT Counties MT Communities Expanded Area Each set of summary polygons captures nearly all structures in Montana, without overlap. In the MT Counties set, a summary polygon is an individual county (e.g. Ravalli County). In the MT Communities (core plus zone combined) set called MT Communities Expanded Area, a summary polygon is the community core plus the zone surrounding the core (as defined below). Expanded Areas include populated areas outside of official community boundaries that are closer to the selected community than to any other community. Long definition: Populated areas not within the boundaries of a community were associated with the community to which they were closest, as measured by travel time. Travel time is influenced by road networks, associated travel speeds, and physical barriers such as water. Populated areas greater than 45 minutes travel time from any community are not included within the Expanded Area for any community. For this assessment, a community core was defined as a Populated Place Area (PPA) as identified by the U.S. Census Bureau. PPAs include incorporated cities and towns as well as Census Designated Places (CDPs). A CDP is an unincorporated concentration of population—a statistical counterpart to incorporated cities and towns. There are 364 PPAs across Montana. Of those, 127 (35 percent) are incorporated cities or towns, and 235 (65 percent) are CDPs. Two PPAs—Butte-Silver Bow and Anaconda-Deer Lodge—are unique in that they represent the balance of a county that is not otherwise incorporated; they are much larger in size than most PPAs. In the PPA dataset, the CDPs represent the location of highest concentration of population for a community; they do not include the less-densely populated areas surrounding the PPA. We refer to the U.S. Census PPA delineation as the community “core.” Approximately 66 percent of Montana’s total structure importance can be found within these PPA core areas (Figure A.1 of the Montana Wildfire Risk Assessment report). To include the populated area and structures surrounding the PPAs, Ager and others (2019) used a travel-time analysis to delineate the land areas closest by drive-time to each PPA core, up to a maximum of 45 minutes travel time. Approximately 33 percent of Montana’s total structure importance can be found within 45 minutes travel time of the cores. Only 1 percent of the total structure importance is not within 45-minutes travel time of any community core.

Purpose:This feature layer describes the boundaries of Proposed Critical Habitat for the Rusty Patched Bumble Bee in Virginia and West Virginia.Source & Date:Data was downloaded from Regulations.gov, Document FWS-R3-ES-2024-0132-0016: CORRECTED_Rusty Patched Bumble Bee Critical Habitat Plot Points. Posted by the Fish and Wildlife Service on Dec 6, 2024 and accessible here as of 1/16/2025.Processing:The data was downloaded as a list of Latitude and Longitude coordinates in a PDF document. The PPDF was converted to Microsoft Excel format using Nitro Pro PDF editor. Data was cleaned of extra tabs, spaces, etc., given an OBJECTID field and saved as a comma-separated values (CSV) text file. The CSV file was loaded into ArcGIS Pro and converted to a point feature class using Latitude and Longitude as Y & X coordinates, respectively. The point featureclass was converted to polyline using the Points to Line script in Data management Tools - Features tool set. The polyline feature was converted to Polygon using Feature to Polygon (again in Features tool set). Fields for Square Miles (SqMi) and Acres were added and calculated with Calculate Geometry. The polygon feature class was exported to shapefile, zipped and uploaded to ArcGIS Online, where it was published as a feature layer.Symbology:Varies - default is medium blue polygon with dark gray outline.

Tabular Summaries - Communities at Risk As part of Montana DNRC’s Montana Wildfire Risk Assessment (MWRA), wildfire risk to homes, commercial buildings, and other structures was assessed across the state. The purpose of this assessment is to identify the counties and communities whose structures are most threatened by wildfire—both on average and in total. The risk-to-structures methods used for this assessment are identical to the methods used for structures within the overall MWRA project. See earlier section 3.4.1 of the report (page 20) for details. This portion of the report addresses only the tabular summaries. The summary methods used in this section were customized to the MWRA results from similar methods previously developed for the Pacific Northwest Risk Assessment (PNRA) and for the national Wildfire Risk to Communities (WRC) project.  Mean Risk to Structures We calculated the Mean Risk to Structures as the product of Mean Conditional Risk to Structures and Mean Burn Probability (multiplied by 1000 to remove decimal places). This is the primary variable by which the summary polygons are ranked. Like the components used to calculate it, Mean Risk to Structures is not a cumulative measure for a summary polygon, so it does not necessarily increase as the number or importance of structures increases. It represents the average of the structures in the polygon regardless of the total number or importance of structures. Total Structure Risk We calculated Total Structure Risk as the product of Mean Risk to Structures and Total Structure Importance. This is the secondary variable by which the summary polygons are ranked. Unlike the previous measures, the total importance of structures (their number and mean importance) strongly influences Total Structure Risk. The risk-to-structures results were summarized for two primary sets of summary polygons: MT Counties MT Communities Expanded Area Each set of summary polygons captures nearly all structures in Montana, without overlap. In the MT Counties set, a summary polygon is an individual county (e.g. Ravalli County). In the MT Communities (core plus zone combined) set called MT Communities Expanded Area, a summary polygon is the community core plus the zone surrounding the core (as defined below). Expanded Areas include populated areas outside of official community boundaries that are closer to the selected community than to any other community. Long definition: Populated areas not within the boundaries of a community were associated with the community to which they were closest, as measured by travel time. Travel time is influenced by road networks, associated travel speeds, and physical barriers such as water. Populated areas greater than 45 minutes travel time from any community are not included within the Expanded Area for any community. For this assessment, a community core was defined as a Populated Place Area (PPA) as identified by the U.S. Census Bureau. PPAs include incorporated cities and towns as well as Census Designated Places (CDPs). A CDP is an unincorporated concentration of population—a statistical counterpart to incorporated cities and towns. There are 364 PPAs across Montana. Of those, 127 (35 percent) are incorporated cities or towns, and 235 (65 percent) are CDPs. Two PPAs—Butte-Silver Bow and Anaconda-Deer Lodge—are unique in that they represent the balance of a county that is not otherwise incorporated; they are much larger in size than most PPAs. In the PPA dataset, the CDPs represent the location of highest concentration of population for a community; they do not include the less-densely populated areas surrounding the PPA. We refer to the U.S. Census PPA delineation as the community “core.” Approximately 66 percent of Montana’s total structure importance can be found within these PPA core areas (Figure A.1 of the Montana Wildfire Risk Assessment report). To include the populated area and structures surrounding the PPAs, Ager and others (2019) used a travel-time analysis to delineate the land areas closest by drive-time to each PPA core, up to a maximum of 45 minutes travel time. Approximately 33 percent of Montana’s total structure importance can be found within 45 minutes travel time of the cores. Only 1 percent of the total structure importance is not within 45-minutes travel time of any community core.