<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>Fallon County</origin>
        <pubdate>20180629</pubdate>
        <title>Fallon_NG911_AOI</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <publish>Fallon County</publish>
        </pubinfo>
      </citeinfo>
    </citation>
    <descript>
      <abstract>Document area of interest polygons summarizing PSAP collaboration calls comparing Next Generation 9-1-1 required GIS layers at the common border of eleven neighboring public safety answering points in counties in Montana, North Dakota, South Dakota and Wyoming. Sixteen total counties participated that shared coincident borders with the Fallon PSAP in Montana which was formed of Fallon, Carter, Prairie and Wibaux counties. The Montana neighbors included Powder River, Custer, Garfield, McCone, Dawson, Richland PSAPS. The North Dakota collaborators included McKenzie, Golden Valley, Slope/Bowman. The South Dakota PSAPs included Harding and Butte. The Wyoming PSAP was Crook. The areas of interest summarized specific geographic observations on, near or crossing the common border between PSAPS for required Next Generation 9-1-1 GIS layers road centerline, site structure address points, and administrative boundaries including PSAP, Provisioning, emergency response for fire, emergency medical service and law enforcement. The geographic observations were gathered in a series of neighbor to neighbor WebEx sessions and conference calls comparing and discussing NG 9-1-1 data at the border supplemented by pre and post Webex session GIS data analysis and documentation.</abstract>
      <purpose>Document area of interest polygons summarizing PSAP collaboration calls comparing Next Generation 9-1-1 required GIS layers at the border of neighboring public safety answering points as a deliverable for a Montana Land Information Grant conducted by Fallon PSAP in fiscal year 2018.</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20180301</begdate>
          <begtime>080000</begtime>
          <enddate>20180427</enddate>
          <endtime>080000</endtime>
        </rngdates>
      </timeinfo>
      <current>Publication Date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>Unknown</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-106.244142</westbc>
        <eastbc>-103.772388</eastbc>
        <northbc>47.461153</northbc>
        <southbc>44.898315</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Categories</themekt>
        <themekey>structure</themekey>
        <themekey>transportation</themekey>
        <themekey>boundaries</themekey>
      </theme>
      <theme>
        <themekt>None</themekt>
        <themekey>boundaries, structure, transportation</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Montana, North Dakota, South Dakota, Wyoming</placekey>
      </place>
    </keywords>
    <accconst>None</accconst>
    <useconst>The polygon areas of interest were created by Geodata Services, Inc. derived from pre and post Webex session analysis of data provided by a some of the participating PSAPs, and from the most authoritative GIS data sources available for the required NG 9-1-1 data layers road centerline, site structure points and administrative boundaries. The areas of interest were modified and attributes populated based on the discussions between neighboring PSAPs in a series of Webex sessions held between February through April 2018. The areas of interest are general areas encompassing GIS data along the borders of the Fallon PSAP and were intended to generally include the data attributes of importance to the PSAPs in preparing their GIS data for Next Generation 9-1-1. The areas of interest attributes are primarily of interest to the participating PSAPS in their ongoing transition from Legacy 911 to NG 9-1-1 over the next several years. DISCLAIMER: The results of tis project were not authoritative, They were better described as exploratory. All areas of interest and specific data issues occurring along the common PSAP borders were not complete due to lack of authoritative data and varying stages of transition to NG 9-1-1. All the participating PSAPs were in various stages of preparation for NG 9-1-1. No counties had completed NG 9-1-1 GIS data at the time of this project, and only the North Dakota and South Dakota PSAPs had begun to transition from Legacy 911 to NG 9-1-1. Data sources were incomplete, and not every participating PSAP provided the most recent GIS data sources required for NG 9-1-1. Six of the PSAPs had local GIS staff and all of them participated in the Webex sessions. The remainder used state agencies or contracted GIS services for 911, and only one GIS contractor participated in the GIS sessions. A mixture of PSAP staff participated in the Webex sesions and contributed content including DES coordinators, sheriff offices, local addressing authorities and pother administrative staff. The areas of interest are of primary use by the participating PSAPS as they work through the transition from Legacy 911 to NG 9-1-1. All participants are advised to revisit and discuss the GIS data in each area of interest once they have prepared their NG 9-1-1 data and make authoritative decisions that require the neighboring collaboration. This work was based on the NENA Standard for NG9-1-1 GIS Data Model NENA-STA-006.1-20181 . Fallon County provides this product/service for informational purposes only. Fallon County did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. Fallon County provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Fallon County, Montana</cntorg>
          <cntper>Chuck Lee</cntper>
        </cntorgp>
        <cntpos>Department of Emergency Services Coordinator</cntpos>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>Box 846</address>
          <city>Baker</city>
          <state>Montana</state>
          <postal>59313</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>406-978-3911</cntvoice>
        <cntemail>clee@midrivers.com</cntemail>
        <hours>8-5</hours>
      </cntinfo>
    </ptcontac>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Geodata Services Inc.</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <city>Missoula</city>
          <state>MT</state>
          <postal>59807</postal>
        </cntaddr>
        <cntvoice>(406) 203-4684</cntvoice>
      </cntinfo>
    </ptcontac>
    <datacred>Montana State Library, Montana Land Information Act Grants. Montana Department of Natural Resources and Conservation, Montana Spatial Data Infrastructure, North Dakota Department of Emergency Services, South Dakota Department of Public Safety. US Census Bureau. Department of Emergency Services and GIS staff in the Montana counties of Fallon, Carter, Prairie and Wibaux, Powder River, Custer, Garfield, McCone, Dawson, Richland; North Dakota counties of McKenzie, Golden Valley, Slope, Bowman; South Dakota counties Harding and Butte; Crook County in Wyoming. Geodata Services, Inc.</datacred>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.6.0.8321</native>
  </idinfo>
  <dataqual>
    <logic>The conceptual consistency is consistent for the areas of interest</logic>
    <complete>The area of interests are complete</complete>
    <lineage>
      <procstep>
        <procdesc>Held pre conference phone calls with all PSAPs that provided GIS data and extended discussions on data sources and Next Generation 9-1-1 </procdesc>
        <procdate>20171117</procdate>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Geodata Services, Inc.</cntorg>
            </cntorgp>
            <cntaddr>
              <addrtype>mailing</addrtype>
              <city>Missoula</city>
              <state>MT</state>
              <postal>59807</postal>
            </cntaddr>
            <cntvoice>(406) 203.4684</cntvoice>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>Prepared a Survey 123 survey for neighbor participants to collect initial information on their GIS data required for NG 9-1-1,  their preparation steps to transition from legacy to NG 9-1-1, and the appropriate staff and consultants to participate in collaborative Webex sessions. Up to 5 emails and phone calls and repeats were made to potential participants to attempt to acquire data and schedule the Webex sessions.  </procdesc>
        <procdate>20171215</procdate>
      </procstep>
      <procstep>
        <procdesc>Geodata Services, Inc completed the area of interest documentation and published the area of interest polygons and associated data for review by participants.</procdesc>
        <procdate>20180202</procdate>
      </procstep>
      <procstep>
        <procdesc>Gathered source data for use in collaborative Webex sessions set up between each neighboring PSAP.  Required GIS layers for Next Generation 9-1-1 were requested from each PSAP via a Survey 123 survey and 4 follow up emails and phone call reminders.  Required layers included road centerline, site structure address points and emergency service polygons for law, fire and emergency medical services.  We received no data from Montana PSAPs, except for the Fallon PSAP.   The emergency service polygons for Fallon were in the form of a polygon layer and an ESN style spreadsheet with ESN numbers from MSAG which we converted ointo a GIS layer for fire and EMS.   Data for all North Dakota counties were obtained from the North Dakota Department of Emergency Services.  It was all in a near NG9-1-1 ready format and consistent from county to county. We received data from Harding County SD, but  it was existing Legacy GIS data.  We received data from Crook County, Wyoming, but it was Legacy GIS data not NG 911 ready data.  MSDI Transportation, Site Structures and Administrative Boundaries were obtained from the Montana State Library and used for reference.  Additional layers such as the US Census County Tiger files were also obtained.  All data sources were used as reference during Webex sessions, and in pre and post processing of areas of interest. </procdesc>
        <procdate>20180227</procdate>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Geodata Services, Inc.</cntorg>
            </cntorgp>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>Prepared draft areas of interest polygons along all the border areas of the Fallon PSAP including four counties in Southeast Montana: Fallon, Carter, Prairie and Wibaux. The area of interest polygons were created as polygons where ever roads or structures appeared to be near the border.  We also used the Montana cadastral to identify potential structure locations.  Fallon PSAP sire structures were located at driveway intersections with addressed roads, rather than on the building centroid locations.  The  MSDI structure data included both Fallon data and building centroids from previous work.  It was difficult to identify structures along border with precision due to their driveway location, so the border areas were scanned with an image backdrop at approximately 1:24,000 scale or finer to look for potential structures.  Wherever a structure was near the border or where a road was close to the border, coincident with it, or crossed a county or state border, we created an area of interest polygon.</procdesc>
        <procdate>20180308</procdate>
      </procstep>
      <procstep>
        <procdesc>Webex sessions we held with all neighboring PSAPs lasting about 2 hours each.  Participants were briefed on the portions of the NG 9-1-1 process of interest to the border areas and best practices and requirements of the NENA GIS data model regarding PSAP collaboration were reviewed.  These typically involved jurisdictional response for fire or EMS from adjoining PSAPs and provisional and PSAP boundary issues.   Each area of interest was discussed and specific road centerline, site structure address points influenced by border issues were documented.</procdesc>
        <procdate>20180405</procdate>
      </procstep>
      <procstep>
        <procdesc>Final metadata was prepared in FGDC format.</procdesc>
        <procdate>20180628</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>GT-polygon composed of chains</sdtstype>
        <ptvctcnt>109</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <mapproj>
          <mapprojn>NAD 1983 StatePlane Montana FIPS 2500</mapprojn>
          <lambertc>
            <stdparll>45.0</stdparll>
            <stdparll>49.0</stdparll>
            <longcm>-109.5</longcm>
            <latprjo>44.25</latprjo>
            <feast>600000.0</feast>
            <fnorth>0.0</fnorth>
          </lambertc>
        </mapproj>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.0001</absres>
            <ordres>0.0001</ordres>
          </coordrep>
          <plandu>meter</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>D North American 1983</horizdn>
        <ellips>GRS 1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>Fallon_NG911_AOI</enttypl>
        <enttypd>Counties of Montana</enttypd>
      </enttyp>
      <attr>
        <attrlabl>SHAPE_Length</attrlabl>
        <attrdef>Perimeter of polygon in meters.</attrdef>
        <attrdefs>Esri</attrdefs>
        <attrdomv>
          <udom>Positive real numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>SHAPE_Area</attrlabl>
        <attrdef>Area of polygon in square meters.</attrdef>
        <attrdefs>Esri</attrdefs>
        <attrdomv>
          <udom>Positive real numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>ID</attrlabl>
        <attrdef>Unique identifier for each area of interest</attrdef>
      </attr>
      <attr>
        <attrlabl>Comment</attrlabl>
        <attrdef>General comments about GIS features in the area of interest</attrdef>
      </attr>
      <attr>
        <attrlabl>F_County</attrlabl>
        <attrdef>The county within the Fallon PSAP that intersects the area of interest</attrdef>
      </attr>
      <attr>
        <attrlabl>N_County</attrlabl>
        <attrdef>The neighboring county that intersects the area of interest</attrdef>
      </attr>
      <attr>
        <attrlabl>AddressOrigin</attrlabl>
        <attrdef>The apparent source of the Left From and Left To address ranges from their originating location for the county in the Fallon PSAP</attrdef>
      </attr>
      <attr>
        <attrlabl>LeftParity</attrlabl>
        <attrdef>The parity of the Left From and Left To address ranges which would be one of the following: even, odd, both, or Z for the county within the Fallon PSAP</attrdef>
      </attr>
      <attr>
        <attrlabl>Boundary</attrlabl>
      </attr>
      <attr>
        <attrlabl>BoundryData</attrlabl>
        <attrdef>The status of the boundary of the Fallon PSAP compared to the neighboring PSAP boundary with values of either Road Gap or Road Overlap.  The baseline standard of comparison was the MSDI county and state boundary layer.  </attrdef>
      </attr>
      <attr>
        <attrlabl>NAddressOrigin</attrlabl>
        <attrdef>The apparent source of the Left From and Left To address ranges from their originating location for the county in the neighboring PSAP</attrdef>
      </attr>
      <attr>
        <attrlabl>NLeftParity</attrlabl>
        <attrdef>The parity of the Left From and Left To address ranges which would be one of the following: even, odd, both, or Z for the county within the neighboring PSAP</attrdef>
      </attr>
      <attr>
        <attrlabl>NBoundaryData</attrlabl>
        <attrdef>The status of the boundary of the neighboring PSAP compared to the Fallon PSAP boundary with values of either Road Gap or Road Overlap.  The baseline standard of comparison was the MSDI county and state boundary layer.  </attrdef>
      </attr>
      <attr>
        <attrlabl>RoadComments</attrlabl>
        <attrdef>Details on the road centerline features that were close to the boundary, coincident with the boundary or crossed the boundary.</attrdef>
      </attr>
      <attr>
        <attrlabl>StructureCOmmewnts</attrlabl>
        <attrdef>Details on the site structure address features that were close to the boundary or appeared to be accessed from an adjacent PSAP or other characteristics of structures.</attrdef>
      </attr>
      <attr>
        <attrlabl>RoadCoincident</attrlabl>
        <attrdef>Comments on road segments that had portions that appeared to be coincident with the boundary</attrdef>
      </attr>
      <attr>
        <attrlabl>RoadCrossing</attrlabl>
      </attr>
      <attr>
        <attrlabl>SHAPE</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>OBJECTID</attrlabl>
        <attrdef>Internal feature number.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Sequential unique whole numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
    </detailed>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntorgp>
          <cntorg>Fallon County</cntorg>
          <cntper>Chuck Lee</cntper>
        </cntorgp>
        <cntpos>Department of Emergency Services Coordinator</cntpos>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>Box 846</address>
          <city>Baker</city>
          <state>MT</state>
          <postal>59313</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>(406) 778-7121</cntvoice>
        <cntemail>clee@midrivers.com</cntemail>
        <hours>8-5</hours>
      </cntinfo>
    </distrib>
    <resdesc>Offline Data</resdesc>
    <distliab>This is not a survey product. No liability is assumed by Fallon County for the use of this product</distliab>
  </distinfo>
  <metainfo>
    <metd>20180629</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Fallon County</cntorg>
          <cntper>Chuck Lee</cntper>
        </cntorgp>
        <cntpos>DES Coordinator</cntpos>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>Box 846</address>
          <city>Baker</city>
          <state>Montana</state>
          <postal>59313</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>(406) 778-7121</cntvoice>
        <cntemail>clee@midrivers.com</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
  <Esri>
    <PublishedDocID>{73DC05A0-5509-42A4-BF57-1D830B6C37F9}</PublishedDocID>
  </Esri>
</metadata>