<?xml version="1.0" encoding="UTF-8" standalone="no"?><metadata xml:lang="en">
    <Esri>
        <CreaDate>20230804</CreaDate>
        <CreaTime>09420700</CreaTime>
        <ArcGISFormat>1.0</ArcGISFormat>
        <SyncOnce>TRUE</SyncOnce>
    </Esri>
    <dataIdInfo>
        <idCitation>
            <resTitle>Map</resTitle>
        </idCitation>
        <idAbs>&lt;span style='font-family:&amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size:16px;'&gt;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 &lt;/span&gt;&lt;b&gt;static &lt;/b&gt;&lt;span style='font-family:&amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size:16px;'&gt;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. &lt;/span&gt;&lt;span style='font-family:&amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size:16px;'&gt;The feature layer visualization by default will show the crashes aggregated by the &lt;/span&gt;&lt;b&gt;predominant &lt;/b&gt;&lt;span style='font-family:&amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size:16px;'&gt;crash type along the corridor.  The aggregation settings can be toggled off if desired and crashes can be viewed by the type of crash.  &lt;/span&gt;&lt;b&gt;Both &lt;/b&gt;&lt;span style='font-family:&amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size:16px;'&gt;the aggregation and standard Feature Layer configurations &lt;/span&gt;&lt;b&gt;do include &lt;/b&gt;&lt;span style='font-family:&amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size:16px;'&gt;popup settings that have been configured.&lt;/span&gt;&lt;div style='font-family:&amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size:16px;'&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style='font-family:&amp;quot;Avenir Next W01&amp;quot;, &amp;quot;Avenir Next W00&amp;quot;, &amp;quot;Avenir Next&amp;quot;, Avenir, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size:16px;'&gt;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 &lt;b&gt;could &lt;/b&gt;be toggled on or off if the user were to add this layer to a &lt;b&gt;new &lt;/b&gt;&lt;font style='font-family:inherit;'&gt;ArcGIS Online Map.  Clustering and aggregation options in ArcGIS Online provide functionality that is &lt;/font&gt;&lt;b&gt;not &lt;/b&gt;yet available in the &lt;b&gt;latest &lt;/b&gt;version of ArcGIS Pro (&amp;lt;=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 &lt;i&gt;more &lt;/i&gt;advanced options should see the following ESRI article (&lt;a style='color:rgb(0, 121, 193); font-family:inherit;' target='_blank' rel='noopener noreferrer'&gt;https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/summarize-and-explore-point-clusters-with-arcade-in-popups/&lt;/a&gt;).&lt;br /&gt;&lt;br /&gt;Popups have been configured for &lt;b&gt;both &lt;/b&gt;the clusters and the &lt;b&gt;individual &lt;/b&gt;crashes.  The &lt;b&gt;individual &lt;/b&gt;crashes themselves do include multiple tables within a &lt;b&gt;single &lt;/b&gt;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 &lt;b&gt;only &lt;/b&gt;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 &lt;b&gt;do &lt;/b&gt;include &lt;b&gt;more &lt;/b&gt;than 3 units and information for these additional units is &lt;b&gt;not &lt;/b&gt;currently included in the dataset at the moment.  &lt;br /&gt;&lt;br /&gt;The crash data items available in this Feature Layer representation includes many of the &lt;b&gt;same &lt;/b&gt;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(&lt;a style='color:rgb(0, 121, 193); font-family:inherit;' target='_blank' rel='noopener noreferrer'&gt;https://www.maine.gov/mdot/mapviewer/?added=Crashes%20-%2010%20Years&lt;/a&gt;).  However this crash data includes data items that are &lt;b&gt;not &lt;/b&gt;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 &lt;b&gt;may &lt;/b&gt;not be visible in those situations where there are four or more units involved in a crash.&lt;/div&gt;</idAbs>
        <searchKeys>
            <keyword>Crash</keyword>
            <keyword>Safety</keyword>
            <keyword>MaineDOT</keyword>
        </searchKeys>
        <idPurp>Crash data since 2012 along State Route 1A from Brewer to Ellsworth (0001A 38.94 – 64.91). If there are sections of State Route 1A 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 (0001A) in the LRS. Using a data driven bridge those crashes coded to 0001A were calibrated to have 0001A 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.</idPurp>
        <idCredit/>
        <resConst>
            <Consts>
                <useLimit/>
            </Consts>
        </resConst>
    </dataIdInfo>
    <Binary>
        <Thumbnail>
            <Data EsriPropertyType="PictureX">iVBORw0KGgoAAAANSUhEUgAAASwAAADICAYAAABS39xVAAAAAXNSR0IB2cksfwAAAAlwSFlzAAAO
xAAADsQBlSsOGwAAAqpJREFUeJzt1DENADAMwLAd5U+5o7BvimQjyJXZ3T0AAfM7AOCVYQEZhgVk
GBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFY
QIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZ
hgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgW
kGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECG
YQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYF
ZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBh
WECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEB
GYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQY
FpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhA
hmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmG
BWQYFpBhWECGYQEZhgVkGBaQYVhAhmEBGYYFZBgWkGFYQIZhARmGBWQYFpBhWECGYQEZhgVkGBaQ
YVhAhmEBGYYFnIoLreIHHblfYqUAAAAASUVORK5CYII=</Data>
        </Thumbnail>
    </Binary>
</metadata>