Service Description: Crash data since 2012 along in select area in Auburn, ME. If there are sections that are considered to be Divided in the LRS and/or pass through a facility that is not a standard two way roadway segment. Divided sections would be coded to a different route in the LRS. Using a data driven bridge those crashes were calibrated to have primary route code mile points. This calibration is not completed using spatial methods, but is truly a tabular approach. Therefore if the distance of the Southbound (SB) route is different than the Northbound (NB) route than the calibration can be slightly off. In any case the goal of calibrating to a single route allows for simpler criteria to filter crashes.
Service ItemId: d887619e05de4718af6b8c86bf24a08e
Has Versioned Data: false
Max Record Count: 2000
Supported query Formats: JSON
Supports applyEdits with GlobalIds: False
Supports Shared Templates: True
All Layers and Tables
Layers:
Description: This crash dataset does include crashes from 2023 up until near the middle of July that have been reviewed and loaded into the Maine DOT Asset Warehouse. This crash dataset is static and was put together as an example showing the clustering functionality in ArcGIS Online. In addition the dataset was designed with columns that include data items at the Unit and Persons levels of a crash. The feature layer visualization by default will show the crashes aggregated by the predominant crash type along the corridor. The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash. Both the aggregation and standard Feature Layer configurations do include popup settings that have been configured.
As mentioned above, the Feature Layer itself has been configured to include a standard unique value renderer based on Crash Type and the layer also includes clustering aggregation configurations that
could be toggled on or off if the user were to add this layer to a
new ArcGIS Online Map. Clustering and aggregation options in ArcGIS Online provide functionality that is not yet available in the
latest version of ArcGIS Pro (<=3.1). This additional configuration includes how to show the popup content for the cluster of crashes. Users interested in learning more about clustering and aggregation in ArcGIS Online and some
more advanced options should see the following ESRI article (
https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/).
Popups have been configured for
both the clusters and the
individual crashes. The
individual crashes themselves do include multiple tables within a
single text element. The bottom table does include data items that pertain to at a maximum of three units for a crash. If a crash includes just one unit then this bottom table will include
only 2 columns. For each additional unit involved in a crash an additional column will appear listing out those data items that pertain to that unit up to a maximum of 3 units. There are crashes that
do include
more than 3 units and information for these additional units is
not currently included in the dataset at the moment.
The crash data items available in this Feature Layer representation includes many of the
same data items from the Crash Layer (10 Years) that are available for use in Maine DOT's Public Map Viewer Application that can be accessed from the following link(
https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years). However this crash data includes data items that are
not yet available in other GIS Crash Departments used in visualizations by the department currently. These additional data items can be aggregated using other presentation types such as a Chart, but could also be filtered in the map. Users should refer to the unit count associated to each crash and be aware when a units information
may not be visible in those situations where there are four or more units involved in a crash.
Copyright Text:
Spatial Reference: 26919 (26919)
Initial Extent:
XMin: 398796.840479127
YMin: 4881608.83784
XMax: 401646.361520873
YMax: 4883580.63756
Spatial Reference: 26919 (26919)
Full Extent:
XMin: 398939.3101
YMin: 4881698.4651
XMax: 401503.8919
YMax: 4883491.0103
Spatial Reference: 26919 (26919)
Units: esriMeters
Child Resources:
Info
SharedTemplates
Supported Operations:
Query
ConvertFormat
Get Estimates