The dataset contains locations and attributes of intersections created as part of the Master Address Repository (MAR) for the Office of the Chief Technology Officer (OCTO) and participating DC government agencies. The intersection points - MAR is primarily derived from DC Department of Transportation's (DDOT) intersection table in their Street Spatial Database (SSD). Regular at-grade intersections (TYPE = 'REGULAR') as well as overpasses (TYPE = 'OVERPASS'), underpasses (TYPE = 'UNDERPASS') and ramps (TYPE = 'RAMP') are included. The overpasses, underpasses, and ramps are based on street centerlines from DDOT. More information on the MAR can be found at https://opendata.dc.gov/pages/addressing-in-dc. The data dictionary is available: https://opendata.dc.gov/documents/2a4b3d59aade43188b6d18e3811f4fd3/explore. In the MAR 2, the IntersectionPt is called INTERSECTIONS_PT and is primarily based off of street data from DC Department of Transportation's Roads & Highways database. It also features additional useful information such as created date, last edited date, begin date, and more.

*The Location Based Response System (LBRS) is an initiative of the Ohio Geographically Referenced Information Program (OGRIP). The LBRS establishes partnerships between State and County government for the creation of spatially accurate street centerlines with address ranges and field verified site-specific address locations. Funding to support the development of LBRS compliant systems is available to counties through a Memorandum of Agreement (MOA) that establishes roles and responsibilities for program participation. Participating counties provide project management and QA/QC on road names, addresses, etc to develop data that is compatible with the state's legacy roadway inventory. The Ohio Department of Transportation is the LBRS Program Sponsor, providing technical guidance, support, and QA/QC services. The program is being administered by OGRIP, the state's coordinating body for Geographic Information System (GIS) activities. Through the collaborative efforts of State and Local government the LBRS program is producing highly accurate field verified data that is current, complete, consistent, and accessible. LBRS data is maintained as an Ohio asset by local resources and is provided to the state as part of a coordinated long-term effort by OGRIP to reduce redundant data collection by developing data that meets the needs of several levels of government. The LBRS supports a multi-jurisdictional approach to protecting the health, safety and welfare of the state’s constituents. *http://ogrip.oit.ohio.gov/ProjectsInitiatives/LBRS.aspx

This layer shows intersections on the road network stored in the Integrated Road Information System (IRIS). An intersection is a road junction where two or more roads either meet or cross at grade (they are at the same level).The layer also details the IRIS Intersection Number. This layer is provided for information only.Note that you are accessing this data pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes.Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material:- The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.Creative Commons CC BY 4.0 https://creativecommons.org/licenses/by/4.0/

Monthly extracts of historic Traffic Data at Signalised derived by SCATS.

SCATS (Sydney Coordinated Adaptive Traffic System) is an intelligent transportation system that manages the dynamic timing of signal phases at traffic signals in real time. The system estimates the number of vehicles passing through the intersection and other information related to traffic signal timing. There is no guarantee this data is accurate or was used to make internal decisions in SCATS.

The data is provided by controller site. Each site has its own parquet file for the month, which contains SCATS data produced by that site. The files use the LM site number format (e.g. – Site 1 is LM00001).

Note that you are accessing the data provided by the links below pursuant to a Creative Commons (Attribution) Licence which has a disclaimer of warranties and limitation of liability. You accept that the data provided pursuant to the Licence is subject to changes and may have errors.

Pursuant to section 3 of the Licence you are provided with the following notice to be included when you Share the Licenced Material:- “The Commissioner of Main Roads is the creator and owner of the data and Licenced Material, which is accessed pursuant to a Creative Commons (Attribution) Licence, which has a disclaimer of warranties and limitation of liability.”

A data dictionary is provided at the document link.

Monthly data extracts are in parquet format.

The locations of the traffic signals are found at the link below.

https://portal-mainroads.opendata.arcgis.com/datasets/traffic-signal-sitesAvailable in JSON format below.gisservices.mainroads.wa.gov.au/arcgis/rest/services/Connect/MapServer/0/query?where=1%3D1&outFields=*&returnGeometry=true&f=pjson

The mapping of the detectors to the strategic approaches at an intersection is given at the link below.

https://mainroadsopendata.mainroads.wa.gov.au/swagger/ui/index#/LmSaDetector

Further information, including SCATS graphics, is available via the Traffic Signal information on Main Roads TrafficMap

trafficmap - Main Roads WA

Point geometry with attributes displaying street intersections of all public and private named roads in East Baton Rouge Parish, Louisiana.

Displays the locations and attributes of SDOT intersections throughout the City. SDOT Intersections are used as reference when viewing nearby assets. Popup includes Street View of intersection.

Intersections within the City of Lynchburg's street centerline network. These points represent the intersection of any street segments and are not limited to controlled or signalized intersections. Signalized Intersections are offered as a separate download.

This intersection points feature class represents current intersections in the City of Los Angeles. Few intersection points, named pseudo nodes, are used to split the street centerline at a point that is not a true intersection at the ground level. 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.Intersection layer was created in geographical information systems (GIS) software to display intersection points. Intersection points are placed where street line features join or cross each other and where freeway off- and on-ramp line features join street line features. The intersection points layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a point feature class and attribute data for the features. The intersection points relates to the intersection attribute table, which contains data describing the limits of the street segment, by the CL_NODE_ID field. The layer shows the location of the intersection points on map products and web mapping applications, and the Department of Transportation, LADOT, uses the intersection points in their GIS system. The intersection attributes are used in the Intersection search function on BOE's web mapping application NavigateLA. The intersection spatial data and related attribute data are maintained in the Intersection layer using Street Centerline Editing application. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. List of Fields:Y: This field captures the georeferenced location along the vertical plane of the point in the data layer that is projected in Stateplane Coordinate System NAD83. For example, Y = in the record of a point, while the X = .CL_NODE_ID: This field value is entered as new point features are added to the edit layer, during Street Centerline application editing process. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline spatial data layer, then the intersections point spatial data layer, and then the intersections point attribute data during the creation of new intersection points. Each intersection identification number is a unique value. The value relates to the street centerline layer attributes, to the INT_ID_FROM and INT_ID_TO fields. One or more street centerline features intersect the intersection point feature. For example, if a street centerline segment ends at a cul-de-sac, then the point feature intersects only one street centerline segment.X: This field captures the georeferenced location along the horizontal plane of the point in the data layer that is projected in Stateplane Coordinate System NAD83. For example, X = in the record of a point, while the Y = .ASSETID: User-defined feature autonumber.USER_ID: The name of the user carrying out the edits.SHAPE: Feature geometry.LST_MODF_DT: Last modification date of the polygon feature.LAT: This field captures the Latitude in deciaml degrees units of the point in the data layer that is projected in Geographic Coordinate System GCS_North_American_1983.OBJECTID: Internal feature number.CRTN_DT: Creation date of the polygon feature.TYPE: This field captures a value for intersection point features that are psuedo nodes or outside of the City. A pseudo node, or point, does not signify a true intersection of two or more different street centerline features. The point is there to split the line feature into two segments. A pseudo node may be needed if for example, the Bureau of Street Services (BSS) has assigned different SECT_ID values for those segments. Values: • S - Feature is a pseudo node and not a true intersection. • null - Feature is an intersection point. • O - Intersection point is outside of the City of LA boundary.LON: This field captures the Longitude in deciaml degrees units of the point in the data layer that is projected in Geographic Coordinate System GCS_North_American_1983.

Roads and Highways manages intersections, however they are not singular points; RH creates a series of points - one for each intersecting road at that intersection. For DDOT, it is more useful to have a single intersection point representing the intersection. Through a custom DDOT script,the series of intersection points is reduced into a single representative point.For more information please visit DDOT's wiki page.

This dataset contains intersections located along Utah state highways. Descriptive information includes signalization and state route intersection flags. Location information includes x,y and route & milepost. This dataset is a Pathway data layer that was collected in the Summer of 2023 via LiDAR inventory. Data is updated on a two year cycle. For questions on the data please contact Ed Graves at edgraves@utah.gov. To download this data please visit UDOT"s Open Data Site.

Intersection Approach Segments are short segments of the route that approach an intersection, in other words, a short section of the road leading up to an intersection.Roads and Highways manages intersections, however they are not singular points; RH creates a series of points - one for each intersecting road at that intersection. For DDOT, it is more useful to have a single intersection point representing the intersection. Through a custom DDOT script,the series of intersection points is reduced into a single representative point.For more information please visit DDOT's wiki page.

A point feature layer with the locations and names of street intersections within Stark County, Ohio. This layer was initially developed so that police, fire, and EMS would be able to identify the closest street intersection for emergency calls. Within the attribute table, you will find the names for the intersecting streets; the primary and secondary streets are the only attributes that are populated. This data is a work in progress and will be updated periodically as new streets are added to our data. It is planned for each street intersection point to be eventually filled out for the whole county.

Street Intersection Points have been developed to facilitate tracking of completed or changing street intersections within the City of Johns Creek, GA.

Street Intersections within the City of Phoenix

The Los Angeles Department of Transportation identify a list of 60 prioritized intersections for the development of safety projects. Develop physical design and engineering countermeasures that would most effectively address each intersection.

The FDOT GIS Intersection feature class provides spatial information on Florida intersections. This information includes intersection direction and surface type. This direction data is required for all roads. The surface type is required for all functionally classified roadways on the SHS and major roadway intersections on HPMS standard sample sections, including Active Off the SHS. This dataset is maintained by the Transportation Data & Analytics office (TDA). The source spatial data for this hosted feature layer was created on: 11/01/2025.For more details please review the FDOT RCI Handbook Download Data: Enter Guest as Username to download the source shapefile from here: https://ftp.fdot.gov/file/d/FTP/FDOT/co/planning/transtat/gis/shapefiles/intersection.zip

The top 200 locations where reported collisions occurred at intersections have been identified. The crash cluster analysis methodology for the top intersection clusters uses a fixed meter search distance of 25 meters (82 ft.) to merge crash clusters together. This analysis was based on crashes where a police officer specified one of the following junction types: Four way intersection, T-intersection, Y-intersection, five point or more. Furthermore, the methodology uses the Equivalent Property Damage Only (EPDO) weighting to rank the clusters. EPDO is based any type of injury crash (including fatal, incapacitating, non-incapacitating and possible) having a weighting of 21 compared to a property damage only crash (which has weighting of 1). The clusters were reviewed in descending EPDO order until 200 locations were obtained. The clustering analysis used crashes from the three year period from 2017-2019. The area encompassing the crash cluster may cover a larger area than just the intersection so it is critical to view these spatially.

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.

Road edges are defined as the edge of the improved surface including the improved shoulder but do not include the unimproved shoulder, only the travel part of the road. The road network is compiled to include all open intersections. Features do not overlap sidewalks, but have the sidewalk area cut out of the road polygons. Overlapping features are acceptable if one of the features is hidden. Road: A generally named thoroughfare, that is usually paved and can be public or private. Unimproved thoroughfares are excluded. Road polygons are formed by a combination of road edge, curb, sidewalk, street intersection closure line, and map sheet edge. Paved Median Island: Perimeter of non-traffic paved areas that separate traffic lanes in opposing directions. Unpaved Median Island: Perimeter of non-traffic grassy, unpaved areas that separate traffic lanes in opposing directions. Paved Traffic Island: Perimeter of non-traffic concrete areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Unpaved Traffic Island: Perimeter of non-traffic unpaved, grassy areas in the middle of streets designed to segregate traffic flow. This does not include linear barriers, e.g., Jersey barriers, walls or guardrails, or point barriers, such as impact attenuators. Features do not overlap sidewalks. Alley: Perimeter of alleys first plotted photogrammetrically from other indicators such as building footprints, fence lines, curb lines, walls, paved or unpaved drives, and map sheet edge. Alley polygons are closed along the lines where they intersect with road polygons. Paved Drive: A paved driveway for a building or entranceway for a parking lot. Driveways are neither streets nor alleys, but provide access to public facilities, such as a drive to a monument, museum, hotel, large estate, sports field or golf course, grounds of the U.S. Capitol, etc. If a driveway is less than 200 feet and leads to a parking lot, the entire paved area is captured as Parking Lot. Driveways are photogrammetrically compiled as polygons and not compiled from individual vectors on different levels. Parking Lot: Generally paved surfaces used for cars to park on. Paved drives usually form entrances to these features, if the drive is more than 200 feet. If the driveway is less than 200 feet leading into the parking lot, the entire paved area is captured as Parking Lot. Parking lots sharing a common boundary with linear features must have the common segment captured once, but coded as both polygon and line. Small parking areas, where individuals park their cars in the middle of a block off a public alley, are not captured as parking lots. These are either public space (e.g., alleys) or private space where owners permit parking to occur. Intersection: A location where more than one road comes together. For standard cross streets, intersection polygons are bounded by curbs and four closure lines at street intersection crosswalks (outer line) or placed arbitrarily where crosswalks could logically be placed. For "T" intersections, the polygons are bounded by curbs and three such closure lines. Complex intersections can have more closure lines. Entire traffic circles are coded as intersections. Hidden Road: A section of a road that passes underneath a bridge or overpass and is not visible in an aerial photograph, but the location can be interpreted based on the road on either side of the bridge. Hidden Median: A road median that exists underneath a bridge or overpass and is not fully visible in an aerial photograph, but the location can be interpreted based on the information visible on either side of the bridge.

Wake County Street Intersection Points, updated weekly.