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.

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.

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

This point layer contains start and end nodes for all of the street segments in Cambridge. It also contains street names for all intersections.Explore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription NodeNumber type: Doublewidth: 8precision: 38 Node ID - relates to "FromNode" and "ToNode" of each street segment

Intersection type: Stringwidth: 75precision: 0 Intersecting street names separated by "&"

IntersectingStreetCount type: Integerwidth: 4precision: 10 Number of intersecting streets at the node

TurnRestriction type: Stringwidth: 10precision: 0 Vehicle turning restrictions at intersection

P_X type: Doublewidth: 8precision: 38 X coordinate of point

P_Y type: Doublewidth: 8precision: 38 Y coordinate of point

Street1 type: Stringwidth: 30precision: 0 Unpopulated

EditDate type: Stringwidth: 4precision: 0

Street2 type: Stringwidth: 30precision: 0 Unpopulated

created_date type: Datewidth: 8precision: 0

last_edited_date type: Datewidth: 8precision: 0

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.

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

2014 - 2016 Top 200 Intersection Crash Cluster Locations.The top locations where reported collisions occurred have been identified. The crash cluster analysis methodology for the crashes uses a fixed meter search distance of 25 meters (82 ft.) to merge crash clusters together. The analysis method finds nearby crashes and merges their areas together, thus creating clusters. If two distinct clusters are found to share a common crash, the two clusters are merged into a single cluster. This method of search-and-merge results in a set of many distinct clusters of different sizes and shapes Furthermore, the methodology uses the Equivalent Property Damage Only (EPDO) weighting to rank the clusters. Additionally, due to the large geographic area encompassed by the crash clusters, it was difficult to name them so they were left unnamed but can be viewed spatially. A review of each location was required to make that determination of the top at grade intersection clusters. Generally, a location was determined to be an “intersection” if the cluster did not contain roadways with grade separation (interchange) nor weaving sections (rotaries or ramps). Intersections located at the ends of off-ramps or traffic circles/rotaries were generally not included. The clusters were reviewed in descending EPDO order until 200 locations were obtained.

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

Rates of long-term and short-term shoreline change were generated in a GIS using the Digital Shoreline Analysis System (DSAS) version 3.0; An ArcGIS extension for calculating shoreline change: U.S. Geological Survey Open-File Report 2005-1304, Thieler, E.R., Himmelstoss, E.A., Zichichi, J.L., and Miller, T.M. The extension is designed to efficiently lead a user through the major steps of shoreline change analysis. This extension to ArcGIS contains three main components that define a baseline, generate orthogonal transects at a user-defined separation along the coast, and calculate rates of change (linear regression, endpoint rate, average of rates, average of endpoints, jackknife).

Proposed intersections throughout Sarpy County as described in the Sarpy County Comprehensive PlanData current as of the last business day.

(Link to Metadata) Intersection points of the VAST trail network with intersection identifiers.

Enclosures with an incidence corresponding to the intersection with the "Dumping basins for reservoirs for domestic use", that is, "surface water protection areas intended to obtain drinking water for human consumption and river plantations".

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.

The Street Intersection Node data represents the point locations where the street centreline segments intersect and at various crossings (ex. railway, river).This dataset will be updated quarterly.

2018 Intersection Volumes in Average Annual Daily Traffic (AADT)

The Vulnerable Road User Safety Assessment is an assessment of the safety performance of the state of Iowa with respect to vulnerable road users and the plan of the state of Iowa to improve the safety of vulnerable road users. It is required by law and is described under 23 U.S.C. 148(1).The assessment is driven by demographic and performance-related data developed in consultation with local governments that represent high-risk areas. This assessment is used to identify areas of high risk to vulnerable road users, and then utilize that assessment to drive strategy and investment decisions around further safety improvements to mitigate identified safety risks.VRU Safety Assessment GoalsIdentify areas of higher risk for bicyclist and pedestrian crashesProvide insight on areas of necessary infrastructure improvements on Iowa roadsFurther the objective of achieving zero fatalities on the nation’s Roads

Intersection Treatments include:Bike BoxesBike ChevronsBike CrossingsProtected IntersectionsRoundaboutsTraffic CirclesTwo Stage Bike Turns