Participants in the Public Safety Highway Incident breakout group:

Ken Brooke, Mitretek

John Lau, (Convener), Viggen Corporation

Becky Brock, Knoxville Police Department, Dept. of Safety

Susan Scott, Jet Propulsion Laboratory

Cecil Goodwin, Viggen Corporation

Ernie Peirce, City of Knoxville

  Use of Spatial Data (densified local Intelligent Transportation System Datum)

• Locating incidents on the network so they can be remedied.
• Locating assets used in incident remediation.
• Network definition.
• User location determination - user should be able to "see" the datum so they can describe their location (nodes should be physically labeled by signage).

Impact possible of ambiguity

• Possible death.
• Probable lawsuits.
• PSHI System effectiveness degradation.
• Increases to traffic congestion.

Institutional and technical barriers to interoperability

• Integration of ITS Datum with existing systems --
• indicates need for simple and Open Datum architecture.
• Need for non-jurisdictional nature to Datum node definition and/or location --
• need for Datum labeling scheme, which will be name independent.
• node naming issue within datum description --(consensus not reached).
• Unwillingness to share existing data (a cost sharing issue - something the datum should help address or prevent if it intends to succeed).

 Operations and planning needs

• Must be easy to create datum network (follow the rules of placement unambiguously).
• Must be able to use Datum rules at region/city level to produce seamless use of the datum for a wider variety of problems such as Mutual Aid.

Special requirements for node placement rules

• Need for Datum placement rules to address any transportation venue (all pavement types/rural-gravel roads/temporary roads/hiking trails etc).
• Need for a category of non-planar nodes for Weather related issues/at grade rail crossings/Bridges/Mountains/Low Water tunnels, approach corridor boundaries, etc.
• Need node/rules for representing important PSHI facilities (Hospitals/fire station/etc.).
• For purpose of unambiguous referencing on the network, the nodes need to be on the network.
• Need consistent, usable, unambiguous set of placement rules.
• Physical signage monuments need to be readily and safely accessible to the public and road maintenance crews.
• Signage standards are required for datum labels, ramp numbering, etc.
• Datum nodes may be required to be placed at existing mile markers (subject for further study).

Special requirements for node accuracy

• Nodes must assist in determining side of the road and link without ambiguity so services can be deployed effectively.
• Lane width/side of highway/shoulder.
• No topological errors.
• There can be different levels of accuracy of nodes depending on application(e.g., control points/intersections may require accurate, surveyed nodes, hospital nodes may not).
• Node attribute field contains accuracy. Levels of accuracy in accuracy field per node of any kind.
• Standard specifies survey methods acceptable in terms of 2drms.
• Survey date field is required.
• There will be a need to map accuracy levels to nodes selected.

Special requirements for node density

• Datum nodes must be locally densifiable.
• National level system must reflect into each emergency operating zone to the greatest extent possible.

Support for interoperability within and between functions

• Datum should support users in providing support to neighboring jurisdictional area.
• Real time Datum transfer should be possible to assist interregional asset deployment.
• Support registration of local GIS Systems with National/densifiable Datum.

Coverage - Freeways, arterials, side streets, etc.

• As stated above, any transportation venue (e.g., includes rail, bridge, tunnel, pedestrian trail).

Implementation issues - both technical and institutional

• Datum format should be useable by any system (Flat ASCII)

Outreach / further requirement generation plans

• Contact and solicit inputs from:
• National Emergency Number Association (NENA).
• Federal Emergency Management Agency (FEMA) - State EMA.
• Federal Railroad Administration (FRA).
• Federal Department of Transportation ( and state DOT).
• National Institute of Transportation Safety Analysis (NITSA).
• Department of Justice (DOJ)/National Institute for Justice (Alert project).
• Seattle Incident Management office.
• Look into systems such as ARTS and IVI for requirements.
• Look at NFPA 1221 - standards for CAD/PHSI Mapping standards/etc.