Ecologists frequently set up sampling quadrats along straight line transects or record transitions from one type of vegetation to another along transects. This simple tool can be used to help visualize the location of those quadrats. Others may have need of such methods to split lines as well. This tool is contingent upon the lines being straight lines.You'll need the following:1) A point shapefile representing the start end of the transect attributed with XY coordinates, line distance, bearing (polar coodinates in degrees from north), and a unique ID field (FID will do). Make sure that you've declinated the bearing to account for the difference between magentic and true north.2) A table with unique IDs for each line and distances along the line where points will be generated.Also, check out Line Intercept Tools for ArcGIS - https://www.arcgis.com/home/item.html?id=6d39ac09fd384d29ba8cc32861e6fb0c

This style comprises 20 distinct hues, plus a white version, of the firefly symbol family for points, lines, and polygons.Points have two flavors of symbols. One is a standard radial opacity decay with a molten white core. The other is a variant with a shimmer effect, if that's what you need.Line symbols are available in solid or dashed. Lines are a stack of colorized semitransparent strokes beneath a white stroke, to create a glow effect.Polygons are also available in two versions. One version applies the glow to the perimeter of the polygon in both inner and outer directions, with a semi-transparent fill. This is effective for non-adjacent polygons. The alternate version only applies an inner glow, to prevent blending and overlapping of adjacent polygons.This is an early version of these symbols and only the points respond to color selection.Learn how to install this style by visiting this salacious blog post.Learn more about Firefly Cartography here.Happy Firefly Mapping! John

For more information about this layer please see the GIS Data Catalog.Points created along lines representing river banks are categorized as Critcal, High, Medium, or Low in potenial to provide shade based on the aspect of the point in relation to the centerline of the river. The point were then converted to continuous lines with the same values as the points.

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

This dataset contains 50-ft contours for the Hot Springs shallowest unit of the Ouachita Mountains aquifer system potentiometric-surface map. The potentiometric-surface shows altitude at which the water level would have risen in tightly-cased wells and represents synoptic conditions during the summer of 2017. Contours were constructed from 59 water-level measurements measured in selected wells (locations in the well point dataset). Major streams and creeks were selected in the study area from the USGS National Hydrography Dataset (U.S. Geological Survey, 2017), and the spring point dataset with 18 spring altitudes calculated from 10-meter digital elevation model (DEM) data (U.S. Geological Survey, 2015; U.S. Geological Survey, 2016). After collecting, processing, and plotting the data, a potentiometric surface was generated using the interpolation method Topo to Raster in ArcMap 10.5 (Esri, 2017a). This tool is specifically designed for the creation of digital elevation models and imposes constraints that ensure a connected drainage structure and a correct representation of the surface from the provided contour data (Esri, 2017a). Once the raster surface was created, 50-ft contour interval were generated using Contour (Spatial Analyst), a spatial analyst tool (available through ArcGIS 3D Analyst toolbox) that creates a line-feature class of contours (isolines) from the raster surface (Esri, 2017b). The Topo to Raster and contouring done by ArcMap 10.5 is a rapid way to interpolate data, but computer programs do not account for hydrologic connections between groundwater and surface water. For this reason, some contours were manually adjusted based on topographical influence, a comparison with the potentiometric surface of Kresse and Hays (2009), and data-point water-level altitudes to more accurately represent the potentiometric surface. Select References: Esri, 2017a, How Topo to Raster works—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/how-topo-to-raster-works.htm. Esri, 2017b, Contour—Help | ArcGIS Desktop, accessed December 5, 2017, at ArcGIS Pro Raster Surface toolset at http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/contour.htm. Kresse, T.M., and Hays, P.D., 2009, Geochemistry, Comparative Analysis, and Physical and Chemical Characteristics of the Thermal Waters East of Hot Springs National Park, Arkansas, 2006-09: U.S. Geological Survey 2009–5263, 48 p., accessed November 28, 2017, at https://pubs.usgs.gov/sir/2009/5263/. U.S. Geological Survey, 2015, USGS NED 1 arc-second n35w094 1 x 1 degree ArcGrid 2015, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html. U.S. Geological Survey, 2016, USGS NED 1 arc-second n35w093 1 x 1 degree ArcGrid 2016, accessed December 5, 2017, at The National Map: Elevation at https://nationalmap.gov/elevation.html.

Those portions of Lake Huron grids 304 and 305 north of a line beginning at the southerly point of land on the easterly side of Dudley Bay (Cadogan Point); then running southwesterly in a straight line to the southeasterly end of Beaver Tail Point; then running westerly in a straight line to the southeasterly end of Whitefish Point in Mackinac County. Regulations: All commercial fishing is prohibited for the period from the Friday before Memorial Day through Labor Day only. Maps for general reference only: refer to text of Consent Decree 2000 for exact locations and provisions.Created a new polygon shapefile in ArcGIS 8.1. Digitized missing target area from Chippewa county 1:24,000 DRG. The new polygon feature was then commbined with the US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer using the union tool from the geoprocessing wizard in Arc Map. The desired features were then selected and exported as a new shapefile. Created a new polygon shapefile in ArcGIS 8.1. A point was located on the USGS Mackinac county 1:24,000 DRG as outlined in the Consent Decree 2000 documentation. The new pollygon layer was created using the snapping tool in ArcMap. Starting form the above point location and heading in a clockwise direction (as outlined in the Consent Decree 2000 documentation) extending the polygon boundaries beyond the improved US Department of Commerce (Bureau of the Census, Geography Division) county census (1995) layer created earlier. The new polygon feature was then commbined with the preceding layer using the union tool from the geoprocessing wizard in Arc Map. The desired features were then selected, exported as a new shapefile, and reprojected from Michigan georef to Decimal Degrees to create the final Les Cheneaux Island Closure C layer.The boundaries represented on consent decree maps are approximations based on the text contained in the 2000 Consent Decree. For legal descriptions of geographic extent or details pertaining to regulations for these representations refer to the original 2000 Consent Decree Document.

The California State Lands Commission (CSLC) was created by the California Legislature in 1938 and given the authority and responsibility to manage certain public lands within the state. The public lands under the Commission’s jurisdiction are of two distinct types—sovereign lands acquired upon California’s admission into the Union in 1850; and certain federally granted lands including school lands, and swamp and overflowed lands. For purposes of this GIS data, sovereign lands are considered to be further divided into two general categories—fixed-boundary sovereign lands and ambulatory-boundary sovereign lands. The following lands are included in this data: Portions of the ambulatory-boundary for state sovereign lands at a specific point in time, for portions of the San Joaquin River. NOT INCLUDED IN THIS DATA: School lands: These are what remains of nearly 5.5 million acres throughout the state originally granted to California by Congress in 1853 to benefit public education. Fixed-boundary sovereign lands: These are sovereign, public trust lands having fixed boundaries as the result of land exchanges, boundary line agreements or court orders. Swamps and overflowed lands: These are what remain of federal lands granted to California by Congress in 1850 to encourage reclamation and development of agricultural lands. ALSO NOT INCLUDED IN THIS DATA: Ownership details within the U.S. Government meanders of Owens Lake. THIS DATA SUPERSEDES all previously published GIS information with respect to the above described state-owned lands under the jurisdiction of the CSLC.

The Statistics Canada street network for 2016 was used to derive street intersection counts within buffers of 100, 250, 300, 500, 750 and 1000 meters of each DMTI Spatial single link postal code for the year 2019. Only street intersections with more than one street segment joining were counted - no dead ends were included. A higher value indicates more intersections and a greater degree of connectivity enabling more direct travel between two points using existing streets. CANUE staff used ArcGIS and the Line and Junction Connectivity Toolbox (see supporting documentation) to create intersection counts and PostGres SQL to produce buffer counts.

Individual boundary polylines were created by first making a point shapefile of the line endpoints or a series of points, then converting the points to a polyline. The point/polyline conversion was done using XTools 'Make One Polyline from Points' tool. Point locations were based on latitude/longitude coordinates given in the technical report or geographic landmark (i.e. islands, points, state/international boundary lines, etc.). Points requiring an azimuth bearing were created in a projected view (UTM Zone 17 NAD27) using the Distance and Azimuth Tools v. 1.6 extension developed by Jenness Enterprises.The polyline shapefiles created in step 1 and an existing polyline shapefile of the international boundary were merged together using the ArcView GeoProcessing Wizard.The shapefile generated in step 2 was converted to a line coverage using the ArcToolbox Conversion Tools - Feature Class to Coverage.The line coverage topology was cleaned and updated using the ArcInfo Workstation CLEAN (dangle length and fuzzy tolerance both set to 0.001) and BUILD commands.The boundary line coverage and an existing Lake Erie shoreline shapefile (derived from ESRI 100k data) were merged together using the ArcView GeoProcessing Wizard.The shapefile generated in step 5 was converted to a line coverage using the ArcToolbox Conversion Tools - Feature Class to Coverage.Topology of the boundary/shoreline coverage was cleaned and updated using the ArcInfo Workstation CLEAN (dangle length and fuzzy tolerance both set to 0.00001) and BUILD commands. BUILD was done for both line and polygon topology.The polygon feature from the coverage generate in step 7 was converted to a shapefile using Theme\Convert to Shapefile in ArcView.

This feature class represents the routes that were used for the Route Directness Index calculation. These routes were generated by submitting the begin and end points of each RDI_Transect to the Esri routing service using the Walking Distance parameter. The service returns a route of the shortest pedestrian path between the two points. The search tolerance for the routing service was set to 400 feet, so that if there was no valid walking destination within 400 feet of the begin or end point, no route was calculated. The routing service is dependent on the Esri network data available when the service was accessed in January 2025. The Route Directness Index (RDI) is a ratio that compares the straight-line (crow-flies) distance from one point to another across a barrier to the actual distance imposed by the network of paths available to a traveler. RDI data is particularly relevant to pedestrian and/or bicyclist trips due to the extra time, physical energy, and exposure to weather that out of direction travel creates. A complete discussion of route directness, including potential applications to decision making, can be found in the Washington State Multimodal Permeability Pilot Report, August 2021 [https://wsdot.wa.gov/sites/default/files/2021-11/MultimodalPermeabilityPilotReport-Aug2021.pdf]. RDI can be analyzed at different scales. A high-level analysis of RDI can address questions that compare population centers across the state or consider whether the RDI values are generally similar within a given population center or tend to vary in different portions of a population center. High level data could be combined with other statewide data such as crash data, transit stops, level of traffic stress data, destination data, etc. to analyze potential correlations. High level RDI data is less useful for analyzing a particular crossing location or recommending solutions to address high RDI values. A more detailed analysis is likely required when questions involve corridor studies or project evaluations. Detailed location information can refer to key destinations and crossing locations that are not captured using higher level network maps.The lowest RDI is 1 because a trip between those points can be made directly along an existing roadway. The actual methodology analyzed hypothetical trips where the start and end points were about a quarter mile apart relative to a straight line. In such a situation, an RDI of 2 would mean the trip is twice the distance it might otherwise be, or about one-half mile. Although one-half mile is not particularly far, the RDI is independent of the actual distance. We might start further down the road and if the RDI remained a 2 our trip distance would be twice as long as it could have been. The RDI thus measures the real or perceived burden or travel cost incurred by a person walking or bicycling.

The view service AGS-ZABAGED® (visualization for orthophoto) is public view map service for viewing ZABAGED® data (including altimetry in the form of contour lines) with Orthophoto of the Czech Republic. It is on-line dynamic map service, which is published from vector data stored in a database. Hence, it is possible to work with individual layers. The WMS interface provides GetFeatureInfo operation, which enables WMS clients to query for attributes of ZABAGED® features. Cartographic visualization of the ZABAGED® features is done with respect to a combination with the Orthophoto of the Czech Republic. Therefore, the service can be used to create thematic orthopfotomaps. Point and line map symbols are in bold colours to stand out in the orthophoto background. Polygon ZABAGED® features are displayed only by an outline without fill, so they do not cover situation on the orthophoto. The service is intended for viewing from scale circa 1 : 10 000.

Last Revised: February 2016 Map InformationThis nowCOAST™ time-enabled map service provides maps depicting the latest surface weather and marine weather observations at observing sites using the international station model. The station model is a method for representing information collected at an observing station using symbols and numbers. The station model depicts current weather conditions, cloud cover, wind speed, wind direction, visibility, air temperature, dew point temperature, sea surface water temperature, significant wave height, air pressure adjusted to mean sea level, and the change in air pressure over the last 3 hours. The circle in the model is centered over the latitude and longitude coordinates of the station. The total cloud cover is expressed as a fraction of cloud covering the sky and is indicated by the amount of circle filled in; however, all cloud cover values are presently displayed using the "Missing" symbol due to a problem with the source data. Present weather information is also not available for display at this time. Wind speed and direction are represented by a wind barb whose line extends from the cover cloud circle towards the direction from which the wind is blowing. The short lines or flags coming off the end of the long line are called barbs, which indicate wind speed in knots. Each normal barb represents 10 knots, while short barbs indicate 5 knots. A flag represents 50 knots. If there is no wind barb depicted, an outer circle around the cloud cover symbol indicates calm winds.Due to software limitations, the observations included in this map service are organized into three separate group layers: 1) Wind velocity (wind barb) observations, 2) Cloud Cover observations, and 3) All other observations, which are displayed as numerical values (e.g. Air Temperature, Wind Gust, Visibility, Sea Surface Temperature, etc.).Additionally, due to the density of weather/ocean observations in this map service, each of these group data layers has been split into ten individual "Scale Band" layers, with each one visible for a certain range of map scales. Thus, to ensure observations are displayed at any scale, users should make sure to always specify all ten corresponding scale band layers in every map request. This will result in the scale band most appropriate for your present zoom level being shown, resulting in a clean, uncluttered display. As you zoom in, additional observations will appear.The observations in this nowCOAST™ map service are updated approximately every 10 minutes. However, since the reporting frequency varies by network or station, the observations for a particular station may update only once per hour. For more detailed information about layer update frequency and timing, please reference the nowCOAST™ Dataset Update Schedule.Background InformationThe maps of near-real-time surface weather and ocean observations are based on non-restricted data obtained from the NWS Family of Services courtesy of NESDIS/OPSD and also the NWS Meteorological Assimilation Data Ingest System (MADIS). The data includes observations from terrestrial and maritime observing stations from the U.S.A. and other countries. For terrestrial networks, the platforms include but are not limited to ASOS, AWOS, RAWS, non-automated stations, U.S. Climate Reference Networks, many U.S. Geological Survey Stations via NWS HADS, several state DOT Road Weather Information Systems, and U.S. Historical Climatology Network-Modernization. For maritime areas, the platforms include NOS/CO-OPS National Water Level Observation Network (NWLON), NOS/CO-OPS Physical Oceanographic Real-Time System (PORTS), NWS/NDBC Fixed Buoys, NDBC Coastal-Marine Automated Network (C-MAN), drifting buoys, ferries, Regional Ocean Observing System (ROOS) coastal stations and buoys, and ships participating in the Voluntary Ship Observing (VOS) Program. Observations from MADIS are updated approximately every 10 minutes in the map service and those from NESDIS are updated every hour. However, not all stations report that frequently. Many stations only report once per hour sometime between 15 minutes before the hour and 30 minutes past the hour. For these stations, new observations will not appear until approximately 23 minutes past top of the hour for land-based stations and 33 minutes past the top of the hour for maritime stations.Time InformationThis map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:Issue a returnUpdates=true request (ArcGIS REST protocol only) for an individual layer or for the service itself, which will return the current start and end times of available data, in epoch time format (milliseconds since 00:00 January 1, 1970). To see an example, click on the "Return Updates" link at the bottom of the REST Service page under "Supported Operations". Refer to the ArcGIS REST API Map Service Documentation for more information.Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against the proper layer corresponding with the target dataset. For raster data, this would be the "Image Footprints with Time Attributes" layer in the same group as the target "Image" layer being displayed. For vector (point, line, or polygon) data, the target layer can be queried directly. In either case, the attributes returned for the matching raster(s) or vector feature(s) will include the following:validtime: Valid timestamp.starttime: Display start time.endtime: Display end time.reftime: Reference time (sometimes referred to as issuance time, cycle time, or initialization time).projmins: Number of minutes from reference time to valid time.desigreftime: Designated reference time; used as a common reference time for all items when individual reference times do not match.desigprojmins: Number of minutes from designated reference time to valid time.Query the nowCOAST™ LayerInfo web service, which has been created to provide additional information about each data layer in a service, including a list of all available "time stops" (i.e. "valid times"), individual timestamps, or the valid time of a layer's latest available data (i.e. "Product Time"). For more information about the LayerInfo web service, including examples of various types of requests, refer to the nowCOAST™ LayerInfo Help DocumentationReferencesNWS, 2013: Sample Station Plot, NWS/NCEP/WPC, College Park, MD (Available at http://www.wpc.ncep.noaa.gov/html/stationplot.shtml).NWS, 2013: Terminology and Weather Symbols, NWS/NCEP/OPC, College Park, MD (Available at http://www.opc.ncep.noaa.gov/product_description/keyterm.shtml).NWS, 2013: How to read Surface weather maps, JetStream an Online School for Weather (Available at http://www.srh.noaa.gov/jetstream/synoptic/wxmaps.htm).

This dataset contains the information for the transit lines in Los Angeles, California. The file contains left and right alignments for five Metro lines to include: the Red and Purple Line, the Gold Line, the Green Line, the Expo Line, the Blue Line. The alignments were created from coordinate points extracted from the Record Drawing. The Record Drawings included spiral curve, circle curve, and alignment data. The Record Drawings were created at various time from 11/1985 to 04/1999. Only tangent lines and circular curve data were used to create the alignments. Spiral data and crossover data were estimated and do not reflect the actual curvature of the tracks.

This feature class represents the transects that were used for the Route Directness Index calculation. These lines were generated along the increasing state routes as represented by the 12/31/2023 WSDOT LRS. Transects were only generated within Population Centers (using the Population Centers dataset obtained from the GIS Workbench in January 2025). Every 0.01 mile (52.8 feet) along the route a transect was created perpendicular to the route extending 500 feet on each side of the route. The begin and end points of each transect were then used to generate the shortest walking route between the two points.The Route Directness Index (RDI) is a ratio that compares the straight-line (crow-flies) distance from one point to another across a barrier to the actual distance imposed by the network of paths available to a traveler. RDI data is particularly relevant to pedestrian and/or bicyclist trips due to the extra time, physical energy, and exposure to weather that out of direction travel creates. A complete discussion of route directness, including potential applications to decision making, can be found Washington State Multimodal Permeability Pilot, August 2021 [https://wsdot.wa.gov/sites/default/files/2021-11/MultimodalPermeabilityPilotReport-Aug2021.pdf].RDI can be analyzed at different scales. A high-level analysis of RDI can address questions that compare population centers across the state or consider whether the RDI values are generally similar within a given population center or tend to vary in different portions of a population center. High level data could be combined with other statewide data such as crash data, transit stops, level of traffic stress data, destination data, etc. to analyze potential correlations. High level RDI data is less useful for analyzing a particular crossing location or recommending solutions to address high RDI values. A more detailed analysis is likely required when questions involve corridor studies or project evaluations. Detailed location information can refer to key destinations and crossing locations that are not captured using higher level network maps.The lowest RDI is 1 because a trip between those points can be made directly along an existing roadway. The actual methodology analyzed hypothetical trips where the start and end points were about a quarter mile apart relative to a straight line. In such a situation, an RDI of 2 would mean the trip is twice the distance it might otherwise be, or about one-half mile. Although one-half mile is not particularly far, the RDI is independent of the actual distance. We might start further down the road and if the RDI remained a 2 our trip distance would be twice as long as it could have been. The RDI thus measures the real or perceived burden or travel cost incurred by a person walking or bicycling.

This feature class represents the points that were used for the Route Directness Index calculation. These points were generated along the increasing state routes as represented by the 12/31/2023 WSDOT LRS. Points were only generated within Population Centers (using the Population Centers dataset obtained from the GIS Workbench in January 2025). Every 0.01 mile (52.8 feet) along the route a transect was created perpendicular to the route extending 500 feet on each side of the route. These points represent the midpoint of each transect. The Route Directness Index (RDI) is a ratio that compares the straight-line (crow-flies) distance from one point to another across a barrier to the actual distance imposed by the network of paths available to a traveler. RDI data is particularly relevant to pedestrian and/or bicyclist trips due to the extra time, physical energy, and exposure to weather that out of direction travel creates. A complete discussion of route directness, including potential applications to decision making, can be found Washington State Multimodal Permeability Pilot, August 2021 [https://wsdot.wa.gov/sites/default/files/2021-11/MultimodalPermeabilityPilotReport-Aug2021.pdf].RDI can be analyzed at different scales. A high-level analysis of RDI can address questions that compare population centers across the state or consider whether the RDI values are generally similar within a given population center or tend to vary in different portions of a population center. High level data could be combined with other statewide data such as crash data, transit stops, level of traffic stress data, destination data, etc. to analyze potential correlations. High level RDI data is less useful for analyzing a particular crossing location or recommending solutions to address high RDI values. A more detailed analysis is likely required when questions involve corridor studies or project evaluations. Detailed location information can refer to key destinations and crossing locations that are not captured using higher level network maps.The lowest RDI is 1 because a trip between those points can be made directly along an existing roadway. The actual methodology analyzed hypothetical trips where the start and end points were about a quarter mile apart relative to a straight line. In such a situation, an RDI of 2 would mean the trip is twice the distance it might otherwise be, or about one-half mile. Although one-half mile is not particularly far, the RDI is independent of the actual distance. We might start further down the road and if the RDI remained a 2 our trip distance would be twice as long as it could have been. The RDI thus measures the real or perceived burden or travel cost incurred by a person walking or bicycling.

Geotechnical reports are indexed within a database maintained by HPW-TEB Geotechnical Unit. Meta data associated to each geotechnical report are captured within this indexing table, including report reference number, title, author, highway and km start and end. The table has been modified to include columns that aid in georeferencing geotechnical reports. Added columns include route ID, Latitude, and Longitude. Transportation Engineering Branch is continually improving its geographical information systems with a major focus on creating linear referencing routes within ArcGIS. Georeferencing geotechnical reports will utilize the linear referencing routes in creating points and line shape files by referencing the highway number and km points or ranges as defined within the indexing table. Distributed from GeoYukon by the Government of Yukon . Discover more digital map data and interactive maps from Yukon's digital map data collection. For more information: geomatics.help@yukon.ca

The Geological Atlas of the Western Canada Sedimentary Basin was designed primarily as a reference volume documenting the subsurface geology of the Western Canada Sedimentary Basin. This GIS dataset is one of a collection of shapefiles representing part of Chapter 10 of the Atlas, Devonian Elk Point Group of the Western Canada Sedimentary Basin, Figure 3, Elk Point Isopach. Shapefiles were produced from archived digital files created by the Alberta Geological Survey in the mid-1990s, and edited in 2005-06 to correct, attribute and consolidate the data into single files by feature type and by figure.

Overview

Pittsburgh street centerlines data, in various formats. Mirrored from the City of Pittsburgh GIS Data Portal.

Data dictionary

Editor Tracking (created_date, created_user, last_edited_date, last_edited_user)

Automatically recorded information indicating the creation date and user and the last modified date and user.

From/To Street Name (fromstreet, tostreet)

Where the street segment ends or begins. The starting point of the line segment is the From Street and the end point of the line segment is the To Street. The names of the cross streets are used where applicable. If the segment does not begin or end at a cross street, CITY LIMIT and DEAD END can both be used. The name of the street itself can also be used in situations where the beginning or end of a segment is in between cross streets.

Functional Class (domi_class)

A general classification system used by the Department of Mobility and Infrastructure to stratify roads by significance.

• • Principal Arterial - Roadways with high traffic volumes such as interstate highways, freeways, and expressways; frequently the route of choice for intercity buses and trucks.
• • Minor Arterial – Roadways that serve trips of moderate length and smaller geographic areas than principal arterials.
• • Collector – Roadways that “collect” traffic from Local Roads and connect traffic to Arterial roadways. Typically, shorter than Arterial Routes but longer than Local Roads. Collectors provide traffic circulation within residential neighborhoods as well as commercial, industrial, or civic districts.
• • Local – Roadways that provide direct access to adjacent land, not intended for use in long distance travel. Locals roads provide access to higher systems, and typically don’t carry through traffic movement.
• • Alley - Streets intended to provide access to the rear or side of lots or buildings in urban areas and not intended for the purpose of vehicular through traffic.
• • Park Road – Roadways that provide access into and through parks.
• • Private Road – Privately owned and maintained roads. Private roads are often open to the public in spaces such as shopping malls, airports, and sports arenas. Public access can be restricted to private gated properties.
• • Unknown

Length (measurlgth)

The length of the segment measured in feet, projected using the NAD 1983 State Plane Pennsylvania South FIPS 3702 (US Feet) projection.

Most Recent Paving Date (replaced)

The date a segment was most recently resurfaced, repaved, or otherwise restored.

Number of Travel Lanes (num_lanes)

Number of travel lanes in any direction of travel on an undivided road. Divided roadways using more than one segment note number of lanes on the given segment only.

One Way Designation (oneway)

The direction of allowed traffic flow along a route

• • N: Travel allowed in both directions.
• • FT: One way travel allowed in the direction the line segment is drawn, from the beginning of the line (from) to the end of the line (to).
• • TF: One way travel allowed in the opposite direction the line segment is drawn, from the end of the line (to) to the beginning of the line (from).

Owner (owner)

The owner of a road, usually but not necessarily always responsible for maintenance activities and project initiation.

• • CITY
• • STATE
• • PRIVATE
• • MT OLIVER
• • COUNTY
• • PORT AUTHORITY
• • OTHER MUNICIPALITY
• • Unknown

Road Status (class)

The status of the road, typically indicating either the maintenance responsibility or if and why a segment cannot traversed by vehicle.

Right/Left Council District (council_rt, council_lt)

The Council District identifier to the right and left of a segment, when facing the direction the line segment has been drawn.

Right/Left Fire Zone (fire_zn_rt, fire_zn_lt)

The Bureau of Fire Zone identifier to the right and left of a segment, when facing the direction the line segment has been drawn.

Right/Left Neighborhood (hood_right, hood_left)

The Neighborhood identifier to the right and left of a segment, when facing the direction the line segment has been drawn.

Right/Left Police Zone (zone_right, zone_left)

The Bureau of Police identifier to the right and left of a segment, when facing the direction the line segment has been drawn.

Right/Left Street Maintenance Division (dpw_zon_rt, dpw_zon_lt)

The Department of Public Works Street Maintenance Division identifier to the right and left of a segment, when facing the direction the line segment has been drawn.

Right/Left Street Sweeping (sweep_right, sweep_left)

The Street Sweeping Route identifier to the right and left of a segment, when facing the direction the line segment has been drawn. The identifier consists of 3 parts: the Public Works Division, the route number, and the date of street sweeping (e.g. ‘5SW8-2W’ is done by the 5th Division, on route number 8, and completed on the 2nd Wednesday of each month).

Right/Left Voting District (vote_dt_rt, vote_dt_lt)

The Voting District identifier to the right and left of a segment, when facing the direction the line segment has been drawn.

Right/Left Ward (ward_rg, ward_lt)

The Ward identifier to the right and left of a segment, when facing the direction the line segment has been drawn.

Right/Left Zip Code (zipr, zipl)

The Zip Code identifier to the right and left of a segment, when facing the direction the line segment has been drawn.

Road Removal Date (retired)

The date indicating when a segment was removed from the street centerline dataset, usually indicating the road was removed due to new development or other changes in the immediate area.

Road Surface Width (roadwidth)

Surface width in feet. The measurement of the full traveled way and shoulders/auxiliary lanes.

Segment ID (carteid)

A unique identifier assigned to each street segment in the City of Pittsburgh.

Speed Limit (speedlimit)

The speed limit for traffic travelling on both sides of the road.

Street Name (streetname, prefix, name, type, suffix, dir)

The streetname field contains the name of a road (a combination of prefix, name, type, suffix, dir. Names in this field are written in all capital letters and their abbreviated type. (E.g. MAIN ST, E QUINN RD). The prefix field contains any prefix before the proper street name, usually an abbreviated cardinal direction (N, S, E, W). The name field contains the spelled out street name. The type field contains the type of street (e.g. road, avenue, way). The suffix field contains any suffix after the proper street name, usually an abbreviated cardinal direction (N, S, E, W). The dir field contains the direction of travel in relation to another segment, typically a tunnel, bridge, or highway.

Surface Material Type (paveclass)

The material used to build the street surface

• • Asphalt
• • Concrete
• • Brick
• • Blockstone
• • Unsurfaced
• • Metal Deck
• • Wood
• • Unknown

WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:

• Metadata is missing or incomplete for some layers at this time and will be continuously improved.
  
• We expect to update this layer roughly in line with CDTFA at some point, but will increase the update cadence over time as we are able to automate the final pieces of the process.

Purpose

County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, the coastline is used to separate coastal buffers from the land-based portions of jurisdictions. This feature layer is for public use.

Related Layers

This dataset is part of a grouping of many datasets:

1. Cities: Only the city boundaries and attributes, without any unincorporated areas
   • With Coastal Buffers
   • Without Coastal Buffers
2. Counties: Full county boundaries and attributes, including all cities within as a single polygon
   • With Coastal Buffers
   • Without Coastal Buffers
3. Cities and Full Counties: A merge of the other two layers, so polygons overlap within city boundaries. Some customers require this behavior, so we provide it as a separate service.
   • With Coastal Buffers (this dataset)
   • Without Coastal Buffers
4. Place Abbreviations
5. Unincorporated Areas (Coming Soon)
6. Census Designated Places (Coming Soon)
   
7. Cartographic Coastline
   • Polygon
   • Line source (Coming Soon)

Point of Contact

California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov

Field and Abbreviation Definitions

• COPRI: county number followed by the 3-digit city primary number used in the Board of Equalization"s 6-digit tax rate area numbering system
• Place Name: CDTFA incorporated (city) or county name
• County: CDTFA county name. For counties, this will be the name of the polygon itself. For cities, it is the name of the county the city polygon is within.
• Legal Place Name: Board on Geographic Names authorized nomenclature for area names published in the Geographic Name Information System
• GNIS_ID: The numeric identifier from the Board on Geographic Names that can be used to join these boundaries to other datasets utilizing this identifier.
• GEOID: numeric geographic identifiers from the US Census Bureau Place Type: Board on Geographic Names authorized nomenclature for boundary type published in the Geographic Name Information System
• Place Abbr: CalTrans Division of Local Assistance abbreviations of incorporated area names
• CNTY Abbr: CalTrans Division of Local Assistance abbreviations of county names
• Area_SqMi: The area of the administrative unit (city or county) in square miles, calculated in EPSG 3310 California Teale Albers.
• COASTAL: Indicates if the polygon is a coastal buffer. Null for land polygons. Additional values include "ocean" and "bay".
• GlobalID: While all of the layers we provide in this dataset include a GlobalID field with unique values, we do not recommend you make any use of it. The GlobalID field exists to support offline sync, but is not persistent, so data keyed to it will be orphaned at our next update. Use one of the other persistent identifiers, such as GNIS_ID or GEOID instead.

Accuracy

CDTFA"s source data notes the following about accuracy:

City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated

This pipe feature class represents current wastewater information of the mainline sewer in the City of Los Angeles. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most rigorous geographic information of the storm drain system using a geometric network model, to ensure that its storm drains reflect current ground conditions. The conduits and inlets represent the storm drain infrastructure in the City of Los Angeles. Storm drain information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Associated information about the wastewater Pipe is entered into attributes. Principal attributes include:PIPE_SUBTYPE: pipe subtype is the principal field that describes various types of lines as either Airline, Force Main, Gravity, Siphon, or Special Lateral.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary). Wastewater pipe lines layer was created in geographical information systems (GIS) software to display the location of sewer pipes. The pipe lines layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. The lines are entered manually based on wastewater sewer maps and BOE standard plans, and information about the lines is entered into attributes. The pipe lines are the main sewers constructed within the public right-of-way in the City of Los Angeles. The ends of line segments, of the pipe lines data, are coincident with the wastewater connectivity nodes, cleanout nodes, non-structures, and physical structures points data. Refer to those layers for more information. The wastewater pipe lines are inherited from a sewer spatial database originally created by the City's Wastewater program. The database was known as SIMMS, Sewer Inventory and Maintenance Management System. For the historical information of the wastewater pipe lines layer, refer to the metadata nested under the sections Data Quality Information, Lineage, Process Step section. Pipe information should only be added to the Wastewater Pipes layer if documentation exists, such as a wastewater map approved by the City Engineer. Sewers plans and specifications proposed under private development are reviewed and approved by Bureau of Engineering. The Department of Public Works, Bureau of Engineering's, Brown Book (current as of 2010) outlines standard specifications for public works construction. For more information on sewer materials and structures, look at the Bureau of Engineering Manual, Part F, Sewer Design, F 400 Sewer Materials and Structures section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf.List of Fields:STREET: This is the street name and street suffix on which the pipe is located.PIPE_LABEL: This attribute identifies the arc segment between two nodes, which represents the pipe segment. There could be any number of pipes between the same two maintenance holes and at least one. If there is more than one pipe between the same two maintenance holes, then a value other than 'A' is assigned to each pipe, such as the value 'B', 'C', and so on consecutively. Also, when a new pipe is constructed, some old pipes are not removed from the ground and the new pipe is added around the existing pipe. In this case, if the original pipe was assigned an 'A', the new pipe is assigned a 'B'.C_UP_INV: This is the calculated pipe upstream invert elevation value.PIPE_MAT: The value signifies the various materials that define LA City's sewer system. Values: • TCP - Terra Cotta pipe. • CMP - Corrugated metal pipe. • RCP - Reinforced concrete pipe. Used for sewers larger than 42inch, with exceptions. • PCT - Polymer concrete pipe. • CON - Concrete or cement. • DIP - Ductile iron pipe. • ABS - Acrylonitrile butadiene styrene. • STL - Steel. • UNK - Unknown. • ACP - Asbestos cement pipe. • RCL - Reinforced concrete pipe lined. • OTH - Other or unknown. • VCP - Vitrified clay pipe. • TRS - Truss pipe. • CIP - Cast iron pipe. • PVC - Polyvinyl chloride. • BRK - Brick. • RCPL - Lined Reinforced concrete pipe. Used for sewers larger than 42inch, with exceptions. • B/C - Concrete brick pipe. • FRP - Centrifugally cast fiberglass reinforced plastic mortar pipe.DN_INV: This is the downstream invert elevation value.PIPE_WIDTH: This value is the pipe dimension for shapes other than round.C_SLOPE: This is the calculated slope.ENABLED: Internal feature number.DN_STRUCT: This attribute identifies a number at one of two end points of the line segment that represents a sewer pipe. A sewer pipe line has a value for the UP_STRUCT and DN_STRUCT fields. This point is the downstream structure that may be a maintenance hole, pump station, junction, etc. Each of these structures is assigned an identifying number that corresponds to a Sewer Wye data record. The 8 digit value is based on an S-Map index map using a standardized numbering scheme. The S-Map is divided into 16 grids, each numbered sequentially from west to east and north to south. The first three digits represent the S-Map number, the following two digits represent the grid number, and the last three digits represent the structure number within the grid. This field also relates to the (name of table or layer) node attribute table.PIPE_SIZE: This value is the inside pipe diameter in inches.MON_INST: This is the month of the pipe installation.PIPE_ID: The value is a combination of the values in the UP_STRUCT, DN_STRUCT, and PIPE_LABEL fields. This is the 17 digit identifier of each pipe segment and is a key attribute of the pipe line data layer. This field named PIPE_ID relates to the field in the Annotation Pipe feature class and to the field in the Wye line feature class data layers.REMARKS: This attribute contains additional comments regarding the pipe line segment.DN_STA_PLS: This is the tens value of the downstream stationing.EASEMENT: This value denotes whether or not the pipe is within an easement.DN_STA_100: This is the hundreds value of the downstream stationing.PIPE_SHAPE: The value signifies the shape of the pipe cross section. Values: • SE - Semi-Elliptical. • O1 - Semi-Elliptical. • UNK - Unknown. • BM - Burns and McDonald. • S2 - Semi-Elliptical. • EL - Elliptical. • O2 - Semi-Elliptical. • CIR - Circular. • Box - Box (Rectangular).PIPE_STATUS: This attribute contains the pipe status. Values: • U - Unknown. • P - Proposed. • T - Abandoned. • F - As Built. • S - Siphon. • L - Lateral. • A - As Bid. • N - Non-City. • R - Airline.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • O - Out LA. • V - Valley Engineering District. • W - West LA Engineering District. • H - Harbor Engineering District. • C - Central Engineering District.C_PIPE_LEN: This is the calculated pipe length.OWNER: This value is the agency or municipality that constructed the pipe. Values: • PVT - Private. • CTY - City of LA. • FED - Federal Facilities. • COSA - LA County Sanitation. • OUTLA - Adjoining cities.CRTN_DT: Creation date of the line feature.TRTMNT_LOC: This value is the treatment plant used to treat the pipe wastewater.PCT_ENTRY2: This is the flag determining if the second slope value, in SLOPE2 field, was entered in percent as opposed to a decimal. Values: • Y - The value is expressed as a percent. • N - The value is not expressed as a percent.UP_STA_100: This is the hundreds value of the upstream stationing.DN_MH: The value is the ID of the structure. This point is the structure that may be a maintenance hole, pump station, junction, etc. The field name DN_MH signifies the structure is the point at the downstream end of the pipe line segment. The field DN_MH is a key attribute to relate the pipe lines feature class to the STRUCTURE_ID field in the physical structures feature class.SAN_PIPE_IDUSER_ID: The name of the user carrying out the edits of the pipe data.WYE_MAT: This is the pipe material as shown on the wye card.WYE_DIAM: This is the pipe diameter as shown on the wye card.SLOPE2: This is the second slope value used for pipe segments with a vertical curve.EST_YR_LEV: This value is the year installed level.EST_MATL: This is the flag determining if the pipe material was estimated.LINER_DATE: This value is the year that the pipe was re-lined.LAST_UPDATE: Date of last update of the line feature.SHAPE: Feature geometry.EST_YEAR: This is the flag indicating if the year if installation was estimated.EST_UPINV: This is the flag determining if the pipe upstream elevation value was estimated.WYE_UPDATE: This value indicates whether the wye card was updated.PCT_ENTRY: This is the flag determining if the slope was entered in percent as opposed to a decimal. Values: • N - The value is not expressed as a percent. • Y - The value is expressed as a percent.PROF: This is the profile drawing number.PLAN1: This is the improvement plan drawing number.PLAN2: This is the supplementary improvement plan drawing number.EST_DNINV: This is the flag determining if the pipe downstream elevation value was estimated.UP_STRUCT: This attribute identifies a number at one of two end points of the line segment that represents a sewer pipe. A sewer pipe line has a value for the UP_STRUCT and DN_STRUCT fields. This point is the upstream structure that may be a maintenance hole, pump station, junction, etc. Each of these structures is assigned an identifying number that corresponds to a Sewer Wye data record. The 8 digit value is based on an S-Map index map