vDRAFTAll Committeedoc NENA .doc

Document Sample
vDRAFTAll Committeedoc  NENA .doc Powered By Docstoc
					 1
 2
 3
 4


 5                                      NENA
 6                    Standard Data Formats
 7                    For 9-1-1 Data Exchange
 8                        & GIS Mapping
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25



26
27
28   NENA Standard Data Formats for 9-1-1 Data Exchange & GIS Mapping
29   NENA-02-010, Version 9, January 6, 2010
30
31   Prepared by:
32   National Emergency Number Association (NENA) Technical Committee Chairs
33
34   Published by NENA
35   Printed in USA
36
37
38
39
40
                                                                               NENA Standard Data Formats for
                                                                           9-1-1 Data Exchange & GIS Mapping
                                                                                      NENA 02-010, Version 9,
                                                                                               January 6, 2010



41                                           NENA STANDARDS
42
43                                                  NOTICE
44
45   The National Emergency Number Association (NENA) publishes this document as a guide for the
46   designers and manufacturers of systems to utilize for the purpose of processing emergency calls. It
47   is not intended to provide complete design specifications or parameters nor to assure the quality of
48   performance of such equipment.
49   NENA reserves the right to revise this NENA STANDARD for any reason including, but not limited
50   to:
51         conformity with criteria or standards promulgated by various agencies
52         utilization of advances in the state of the technical arts
53         or to reflect changes in the design of equipment or services described herein.
54   It is possible that certain advances in technology will precede these revisions. Therefore, this NENA
55   STANDARD should not be the only source of information used. NENA recommends that readers
56   contact their Telecommunications Carrier representative to ensure compatibility with the 9-1-1
57   network.
58   Patents may cover the specifications, techniques or network interface/system characteristics
59   disclosed herein. No license expressed or implied is hereby granted. This document shall not be
60   construed as a suggestion to any manufacturer to modify or change any of its products, nor does this
61   document represent any commitment by NENA or any affiliate thereof to purchase any product
62   whether or not it provides the described characteristics.
63   This document has been prepared solely for the voluntary use of E9-1-1 Service System Providers,
64   network interface and system vendors, participating telephone companies, etc.
65   By using this document, the user agrees that NENA will have no liability for any consequential,
66   incidental, special, or punitive damages arising from use of the document.
67   NENA‟s Technical Committee has developed this document. Recommendations for change to this
68   document may be submitted to:
69   National Emergency Number Association
70   4350 N. Fairfax Drive, Suite 750
71   Arlington, VA 22203-1695
72   800-332-3911
73   or: techdoccomments@nena.org
74




     Version 9, January 6, 2010                                                              Page 2 of 88
                                                                             NENA Standard Data Formats for
                                                                         9-1-1 Data Exchange & GIS Mapping
                                                                                    NENA 02-010, Version 9,
                                                                                             January 6, 2010


75   Acknowledgments:
76
77   The National Emergency Number Association (NENA) Data Technical Committee, Data Exchange
78   Working Group and GIS Data Model Working Group, developed this document.
79   NENA recognizes the following industry experts and their companies for their contributions in
80   development of this document.
81
82   Version 9, Approved MM/DD/YYYY
     Members                                                        Company
     Erica Aubut, Data Technical Committee Vice-Chair, GIS          State of Vermont
     Working Group Leader and Technical Editor
     Delaine Arnold, Data Technical Committee Chair                 Arnold 9-1-1 Consulting
     Patty Bluhm, Data Exchange Formats Working Group Leader        Intrado
     and XML Editor
     Marc Berryman                                                  Data Digital Technologies, Inc.
     Carlton B. Walls, III                                          Lancaster County-Wide
                                                                    Communications
     Gordon Chinander                                               Metropolitan Emergency
                                                                    Services Board
     Kathy Lillequist                                               Geo-Comm
     Sharon Nichol-Jost                                             Bexar Metro 9-1-1
     Carl Reed                                                      Open Geospatial Consortium
     Robert White                                                   State of Maine
     Adam Iten                                                      State of Arizona
     Robert Long                                                    Bexar Metro 9-1-1
83
84   This committee would also thank Tom Breen, Technical Committee Chair/Liaison, Tony Busam,
85   Technical Committee Vice-Chair/Liaison, and Roger Hixson, Technical Issues Director, for their
86   support and assistance. The committee/working group would also like to give a special thank you to
87   Patty Bluhm and Open Geospatial Consortium for all their efforts, support & assistance in
88   developing the NG9-1-1 GIS Data Model.
89
90
91
92
93
94
95
96
97

     Version 9, January 6, 2010                                                           Page 3 of 88
                                                                                                                                       NENA Standard Data Formats for
                                                                                                                                   9-1-1 Data Exchange & GIS Mapping
                                                                                                                                              NENA 02-010, Version 9,
                                                                                                                                                       January 6, 2010



 98
 99                                                                     TABLE OF CONTENTS
100
101   1       EXECUTIVE OVERVIEW .............................................................................................................................. 7
102   1.1     PURPOSE AND SCOPE OF DOCUMENT .................................................................................................................... 7
103   1.2     REASON TO IMPLEMENT........................................................................................................................................ 7
104   1.3     BENEFITS .............................................................................................................................................................. 8
105   2       INTRODUCTION .............................................................................................................................................. 9
106   2.1     OPERATIONAL IMPACTS SUMMARY ...................................................................................................................... 9
107   2.2     SECURITY IMPACTS SUMMARY ............................................................................................................................. 9
108   2.3     DOCUMENT TERMINOLOGY .................................................................................................................................. 9
109   2.4     REASON FOR ISSUE ............................................................................................................................................... 9
110   2.5     RECOMMENDATION FOR ADDITIONAL DEVELOPMENT WORK ............................................................................ 14
111   2.6     DATE COMPLIANCE ............................................................................................................................................ 14
112   2.7     ANTICIPATED TIMELINE ...................................................................................................................................... 14
113   2.8     COSTS FACTORS ................................................................................................................................................. 14
114   2.9     FUTURE PATH PLAN CRITERIA FOR TECHNICAL EVOLUTION .............................................................................. 14
115   2.10      COST RECOVERY CONSIDERATIONS ............................................................................................................... 15
116   2.11      ADDITIONAL IMPACTS (NON COST RELATED .................................................................................................. 15
117   2.12      INTELLECTUAL PROPERTY RIGHTS POLICY .................................................................................................... 15
118   2.13      ACRONYMS/ABBREVIATIONS ......................................................................................................................... 16
119   3       TECHNICAL DESCRIPTION ....................................................................................................................... 17
120   3.1 TYPES OF DATA EXCHANGE FORMATS ............................................................................................................... 17
121      Common Considerations: ....................................................................................................................................... 17
122      3.1.1 Version 1 & 2 formats: ............................................................................................................................. 18
123      3.1.2 Version 3 data formats: ............................................................................................................................ 18
124      3.1.3 Version 4 Description Summary: .............................................................................................................. 19
125   4       RECOMMENDED READING AND REFERENCES.................................................................................. 20
126   5       EXHIBITS ........................................................................................................................................................ 21
127   EXHIBIT 1 ................................................................................................................................................................. 21
128   VERSION 1 FORMAT FOR DATA EXCHANGE (OBSOLETE – DO NOT USE) ................................................... 21
129   EXHIBIT 2 ................................................................................................................................................................. 24
130   VERSION 1 FORMAT FOR MSAG DATA EXCHANGE (OBSOLETE – DO NOT USE) ....................................... 24
131   EXHIBIT 3 ................................................................................................................................................................. 25
132   VERSION 1 HEADER FORMAT FOR DATA EXCHANGE (OBSOLETE – DO NOT USE) .................................. 25
133   EXHIBIT 4 ................................................................................................................................................................. 26
134   VERSION 1 TRAILER FORMAT FOR DATA EXCHANGE (OBSOLETE – DO NOT USE) .................................. 26
135   EXHIBIT 5 ................................................................................................................................................................. 27
136   VERSION 2.0 FORMAT FOR DATA EXCHANGE .................................................................................................. 27
137   VERSION 2.0 FORMAT FOR MSAG DATA EXCHANGE ..................................................................................... 27
138   VERSION 2.0 HEADER FORMAT FOR DATA EXCHANGE ................................................................................. 27
      Version 9, January 6, 2010                                                                                                                                 Page 4 of 88
                                                                                                                                        NENA Standard Data Formats for
                                                                                                                                    9-1-1 Data Exchange & GIS Mapping
                                                                                                                                               NENA 02-010, Version 9,
                                                                                                                                                        January 6, 2010


139   VERSION 2.0 TRAILER FORMAT FOR DATA EXCHANGE ................................................................................ 27
140   EXHIBIT 6 ................................................................................................................................................................. 28
141   VERSION 2.1 FORMAT FOR DATA EXCHANGE .................................................................................................. 28
142   EXHIBIT 7 ................................................................................................................................................................. 32
143   VERSION 2.1 FORMAT FOR MSAG DATA EXCHANGE ..................................................................................... 32
144   EXHIBIT 8 ................................................................................................................................................................. 34
145   VERSION 2.1 HEADER FORMAT FOR DATA EXCHANGE ................................................................................. 34
146   EXHIBIT 9 ................................................................................................................................................................. 35
147   VERSION 2.1 TRAILER FORMAT FOR DATA EXCHANGE ................................................................................ 35
148   EXHIBIT 10 ............................................................................................................................................................... 36
149   VERSION 3.1 FORMAT FOR DATA EXCHANGE .................................................................................................. 36
150     5.1.1  Data Record Format Example: ................................................................................................................ 41
151   EXHIBIT 11 ............................................................................................................................................................... 42
152   VERSION 3.1 FORMAT FOR MSAG DATA EXCHANGE ..................................................................................... 42
153   EXHIBIT 12 ............................................................................................................................................................... 44
154   VERSION 3.1 HEADER FORMAT FOR DATA EXCHANGE ................................................................................. 44
155     5.1.2  Header Record Format Example: ............................................................................................................ 44
156   EXHIBIT 13 ............................................................................................................................................................... 45
157   VERSION 3.1 TRAILER FORMAT FOR DATA EXCHANGE ................................................................................ 45
158     5.1.3  Version 3.1 Trailer Record Format Example: .......................................................................................... 45
159   EXHIBIT 14 ............................................................................................................................................................... 46
160   VERSION 3.1 WIRELESS DATA EXCHANGE ....................................................................................................... 46
161     5.1.4  Dynamic Updates of the ALI Database .................................................................................................... 46
162   EXHIBIT 15 ............................................................................................................................................................... 51
163   VERSION 4 XML FORMAT FOR DATA EXCHANGE ........................................................................................... 51
164     5.1.5  The XML Schema ...................................................................................................................................... 51
165     5.1.6  Schema Version Control ........................................................................................................................... 51
166     5.1.7  Schema Design ......................................................................................................................................... 51
167     5.1.8  Schema Extensions ................................................................................................................................... 52
168     5.1.9  Schema Validation .................................................................................................................................... 52
169     5.1.10    Validation Point ................................................................................................................................... 52
170     5.1.11    Redefining of Data Elements ............................................................................................................... 52
171     5.1.12    Two examples of this redefining are described below. ........................................................................ 52
172     5.1.13    Transmission Protocol ......................................................................................................................... 53
173     5.1.14    XML Schema Location ......................................................................................................................... 53
174     5.1.15    Example of the relationship between schema Generations and subsequent Releases ......................... 55
175     5.1.16    All schemas: ......................................................................................................................................... 56
176   6       ALI SCHEMAS ................................................................................................................................................ 56
177       6.1.1        ALI.xsd ...................................................................................................................................................... 56

      Version 9, January 6, 2010                                                                                                                                  Page 5 of 88
                                                                                                                                          NENA Standard Data Formats for
                                                                                                                                      9-1-1 Data Exchange & GIS Mapping
                                                                                                                                                 NENA 02-010, Version 9,
                                                                                                                                                          January 6, 2010


178        6.1.2       ALITypeLib.xsd ......................................................................................................................................... 57
179        6.1.3       ALI Query Service Directory and Schemas .............................................................................................. 58
180        6.1.4       AQS and AQS.WS Removed ...................................................................................................................... 58
181        6.1.5       MSAGRecord.xsd...................................................................................................................................... 58
182   7       I2 SCHEMAS ................................................................................................................................................... 58
183      7.1.1    Geopriv Directory and Schemas ............................................................................................................... 58
184      7.1.2    GML-3.1.1 Directory and Schemas .......................................................................................................... 58
185      7.1.3    All I2 Schemas .......................................................................................................................................... 58
186      7.1.4    V2.xsd ....................................................................................................................................................... 59
187      7.1.5    V7.xsd ....................................................................................................................................................... 59
188      7.1.6    V8.xsd ....................................................................................................................................................... 59
189      7.1.7    V9.xsd ....................................................................................................................................................... 59
190   EXHIBIT 22 ................................................................................................................................................................ 60
191   GIS DATA MODEL, VERSION 2.0 ........................................................................................................................... 60
192      1.0 Preface .......................................................................................................................................................... 60
193   1.2 9-1-1 SPATIAL ATTRIBUTES FOR LINE DATA........................................................................................... 61
194   1.2.1B.     RAILROAD LAYER (OPTIONAL) ................................................................................................................. 64
195   1.2.1C.     HYDROLOGY LAYER (OPTIONAL) ............................................................................................................. 64
196   1.3.     9-1-1 SPATIAL ATTRIBUTES FOR POINT DATA ................................................................................... 65
197   1.3. A EMERGENCY SERVICE AGENCY LOCATION LAYER (REQUIRED) .................................................................... 65
198   1.3 B. CELL SITE LOCATION LAYER (REQUIRED) ..................................................................................................... 66
199   1.3 C. MILE MARKER LOCATION LAYER (OPTIONAL) .............................................................................................. 67
200   1.3 E. SITE/STRUCTURE LOCATION LAYER (OPTIONAL) .............................................................................................. 67
201   1.4.     9-1-1 SPATIAL ATTRIBUTES FOR POLYGON DATA ............................................................................ 68
202   1.4 A. COUNTY BOUNDARY LAYER (REQUIRED) ...................................................................................................... 68
203   1.4 B. EMERGENCY SERVICE ZONE BOUNDARY LAYER (REQUIRED) ....................................................................... 69
204   1.4 C. MUNICIPAL BOUNDARY LAYER (REQUIRED) ................................................................................................. 69
205   1.4 D. EMERGENCY SERVICE AGENCY BOUNDARY LAYER (REQUIRED) .................................................................. 69
206   1.4 E. CELL SITE COVERAGE LAYER (REQUIRED) .................................................................................................... 70
207           1.4 F.         Hydrology Layer (Optional) ................................................................................................................................ 71
208   99      PREVIOUS ACKNOWLEDGMENTS .......................................................................................................... 88
209
210
211




      Version 9, January 6, 2010                                                                                                                                    Page 6 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010




212   1   Executive Overview
213    1.1 Purpose and Scope of Document
214   This document sets forth NENA standard formats for Automatic Location Identification (ALI) data
215   exchange between Service Providers and Data Base Management System Providers, a GIS data
216   model, a Data Dictionary, and formats for data exchange between the ALI Database and PSAP
217   Controller equipment.
218   Movement of ALI data between Service Providers and/or Data Base Management System Providers
219   is a necessary and common activity for the activation of E9-1-1 systems. Means of moving such
220   data is varied and many. This document contains data exchange formats recommended for creation
221   and transporting of 9-1-1 data.
222   This recommendation advocates the use of one of two common protocols (KERMIT and NDM) for
223   use in the near term and with a move toward one common protocol (TCP/IP) in the future. The
224   recommendation unfolded in this manner with the recognition that as a goal NENA acknowledges
225   the advantage of one protocol, but that existing systems are in place so an evolution plan must be put
226   in place and that no single protocol can satisfy all applications.

227    1.2 Reason to Implement
228   Industry adoption of the standard will:
229          Minimize costs incurred in providing E9-1-1 data base services.
230          Ensure timely activation of E9-1-1 data base systems.
231          Ensure consistent provision of ALI data.
232          Enable data compatibility for system integration of E9-1-1 products and services.
233          Minimize set-up time
234          Aid companies in future planning
235
236   When to Implement
237   Since many Service Providers, Data Base Management System Providers and equipment vendors are
238   currently utilizing the original Version 1 and 2 data exchange formats defined herein, it is strongly
239   recommended that Version 4 XML formats be implemented to provide for future data needs. Service
240   Providers and the respective Data Base Management System Provider must jointly determine the
241   data format most relevant to the system software being utilized.
242   A goal of January 1, 2000 was recommended as the date when Service Providers would be capable
243   of sending data utilizing the revised Version 2.0 (now 2.1) format and Version 3.0 format to the Data
244   Base Management System.


      Version 9, January 6, 2010                                                             Page 7 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010


245   It was further understood that many in-service data flows were unable to conform to the NENA
246   formats by the target date, but the Data Technical Committee strongly recommends that every effort
247   be made to conform to at least one of the NENA data exchange formats preferably the most current
248   Generation of Version 4 as found on the NENA Internet site at
249   http://www.nena.org/xml_schemas/nena.htm.
250   July 1, 1994 was established as the date when Service Providers and Data Base Management Service
251   Providers should be capable of using the transmission protocol options. All future plans should
252   include the ability to use these options.
253   Version 4 Data Exchange Format should be implemented in conjunction with wireless phase II.

254    1.3 Benefits
255   The benefits that will be realized by implementing the newly defined NENA Version 4 standard in
256   this document may not be immediately discernable. While all NENA standards promote a consistent
257   view of 911 data, this release of the NENA 02-010 document provides the first major departure from
258   the previously held standard for data exchange by introducing the XML data exchange format
259   coordinated between 911 data source technologies. This release of NENA Version 4 lays the
260   groundwork necessary to support the ever growing and changing sources of 911 data.
261   Utilizing the changes outlined in this document will allow the use of industry standard tools for
262   XML data processing. While this will not eliminate the need for future programming effort it does
263   provide a standard approach to the identification, transmission and processing of data from many
264   sources each with its unique data format and structure.
265   NENA Version 4 Data Exchange Format is an industry standard XML data format. NENA XML
266   (Extensible Markup Language) documents have been adapted from SGML (Standard Generalized
267   Markup Language) by the World Wide Web Consortium. Version 4 Data Exchange Format has been
268   created to bring the NENA Data Exchange Format in line with industry standard implementation
269   methods, to introduce versioning control and promote reusability of previous work.
270   In addition to the XML changes this document introduces a new field to the previous NENA version
271   2.1. As a result of the implementation of private switch 911 and the common use of the NENA 2.1
272   format, we have added a field for NENA Data Provider ID (Company ID 2) and renamed the
273   existing Dial Tone Provider field to Access Infrastructure Provider (Company ID 1). The character
274   space for new data field was taken from the last 5 character positions in the NENA Reserved data
275   field. Since these character positions were reserved for NENA only use there should be no impact on
276   operating systems. For those companies utilizing Private Switch 911, this change provides a location
277   for both the Access Infrastructure Provider (Company ID 1) and the provider of the PBX station data
278   provider. (Company ID 2)




      Version 9, January 6, 2010                                                           Page 8 of 88
                                                                               NENA Standard Data Formats for
                                                                           9-1-1 Data Exchange & GIS Mapping
                                                                                      NENA 02-010, Version 9,
                                                                                               January 6, 2010



279   2   Introduction
280    2.1 Operational Impacts Summary
281   Due to the increased volume and unique format of XML data, implementing the current changes to
282   NENA 4 will impact all systems and network elements associated with the creation, transport and
283   processing of 911 XML data.
284   Change to the NENA Reserved field should have no impact on operating systems since these
285   character positions were reserved for NENA use and should be space filled where not being used.

286    2.2 Security Impacts Summary
287   Security is handled by the appropriate 9-1-1 Data Base Management System Provider and the
288   appropriate 9-1-1 data providers as deemed by their internal IT security procedures and processes.

289    2.3 Document Terminology
290   The terms “shall “, “must” and “required” are used throughout this document to indicate required
291   parameters and to differentiate from those parameters that are recommendations. Recommendations
292   are identified by the words “desirable” or “preferably”.

293    2.4 Reason for Issue
294   NENA reserves the right to modify this document. Upon revision, the reason(s) will be provided in
295   this paragraph.
296
           Version             Date        Reason For Changes
           Original        06/15/1991      Initial Document defined NENA Version 1 Data Exchange
                                           Format. The original Version 1 Data Exchange format was
                                           created to provide established formats for exchange of 9-1-1
                                           data between Service Providers and the Data Base
                                           Management System Providers. The format was created in a
                                           fixed format with 232 characters available within the record
                                           format for ALI data.
               2           06/15/1993      NENA Version 2 Data Exchange Format created.
               3           06/30/1998      Version 1 has been changed to reflect current terminology
                                           in format description fields.

                                           Version 2 has been changed to Version 2.1 to reflect new
                                           fields which reflect the “year 2000” date identification and
                                           definition of the “Alt #” field for the “ALT#” associated
                                           with Interim Number Portability, to identify the Function of
                                           Change indicators of “U”nlock and “M”igrate for Local

      Version 9, January 6, 2010                                                            Page 9 of 88
                                                                      NENA Standard Data Formats for
                                                                  9-1-1 Data Exchange & GIS Mapping
                                                                             NENA 02-010, Version 9,
                                                                                      January 6, 2010



                                  Number Portability and to reflect current terminology in
                                  format description fields. This will be the last update to
                                  Version 2.

                                  Version 3 Data Exchange Formats were added June 1998
                                  due to the difficulty in modifying Version 2 standards.
                                  Version 3.0 has been created to reflect data formats utilizing
                                  a “Tag Data” concept, which creates a variable length
                                  record dependent upon the data fields being utilized
                                  between Service Providers and Data Base Management
                                  System Providers. Version 3 formats include additional
                                  fields and updated field names to better reflect industry
                                  trends.
        4            05/30/1999   This standard has been created to merge and replace the
                                  original NENA 02-001 NENA Recommended Formats for
                                  Data Exchange and NENA 02-003 NENA Recommended
                                  Protocols for Data Exchange into a common document to
                                  facilitate ease of use based upon the user community. There
                                  has been no intentional change made to the existing
                                  standards. The original standards documents 02-001
                                  and 02-003 will be removed from service.
        5            01/22/2002   Version 3.0 formats were changed to Version 3.1 with the
                                  introduction of Version 4, and the need to change existing
                                  labels and add new labels due to technology changes.`

                                  This standard has been updated with a Version 4 Data
                                  Exchange that is based on Version 3.1 tags with XML
                                  formatting. Version 3.1 and Version 4 tags are meant to be
                                  mirrors of each other with the only difference being the tag
                                  versus XML formatting. This document has also been
                                  updated with Version 1.0 of the GIS Data Model Format
                                  and Version 1.0 of the Format for Data Exchange between
                                  ALI Database and PSAP Controller Equipment.

                                  Version 4 Data Exchange Format is an industry standard
                                  XML data format. NENA XML (Extensible Markup
                                  Language) documents have been adapted from SGML
                                  (Standard Generalized Markup Language) by the World
                                  Wide Web Consortium. Version 4 Data Exchange Format
                                  was created to bring the NENA Data Exchange Format in
                                  line with industry standard implementation methods, to

Version 9, January 6, 2010                                                         Page 10 of 88
                                                                     NENA Standard Data Formats for
                                                                 9-1-1 Data Exchange & GIS Mapping
                                                                            NENA 02-010, Version 9,
                                                                                     January 6, 2010



                                  introduce versioning control and promote reusability of
                                  previous work. All existing NENA 4 information has been
                                  removed from this document and moved to an easily
                                  accessible area on the NENA web site.
                                  http://www.nena.org/xml_schemas/nena.htm.
        6            11/09/2004   The NENA Version 4 XML Data Exchange Format has
                                  been revised to include:
                                       Industry standard tag naming conventions
                                       A schema library document to define XML tag
                                          names and their respective data types
                                       An XML schema document for use in validation of
                                          XML documents
                                       A redesigned XML schema to promote the
                                          reusability of defined XML data structures.
                                       A process that will allow changes to existing data
                                          definitions that will not require reprogramming of
                                          applications.
                                       Establishment of Generation and Release control
                                          methods that promotes backward compatibility
                                  The Data Provider ID (Company ID 2) field is used to carry
                                  the NENA Company ID of a PS/911data provider or a
                                  reseller. The NENA Reserved field has been reduced by 5
                                  bytes to accommodate the Data Provider ID (Company ID
                                  2) field. In addition the “Company ID” field that represents
                                  the “Company ID 1” field has been renamed to Access
                                  Infrastructure Provider ID and the definition clarified.




Version 9, January 6, 2010                                                        Page 11 of 88
                                                                      NENA Standard Data Formats for
                                                                  9-1-1 Data Exchange & GIS Mapping
                                                                             NENA 02-010, Version 9,
                                                                                      January 6, 2010



        7            02/25/2006   Established new Classes of Service for VoIP. There have
                                  been 4 types of VoIP users identified:
                                      1. Fixed (static) - VoIP service sold as not having
                                          nomadic capability
                                      2. Enterprise – IP/PBX, VoIP service sold as not
                                          having nomadic capability
                                      3. Nomadic – VoIP service that has the capability to be
                                          moved
                                      4. Mobile – example: like wireless, designed to operate
                                          from multiple locations

                                  Seven new Class of Service have been identifies for VoIP.
                                  With the understanding that most VoIP providers do not
                                  have the capability of delivering the specific Class of
                                  Service at this time, a default Class of Service has been
                                  developed.

                                  V = VoIP Services default Class of Service. (preferably
                                  with VOIP being displayed at the PSAP)

                                  The other new Class of Service one byte characters are:
                                      C= VoIP Residential (preferably with VRES being
                                         displayed at the PSAP)
                                      D= VoIP Business (preferably with VBUS being
                                         displayed at the PSAP)
                                      E = VoIP Coin/Pay Phone (preferably with VPAY
                                         being displayed at the PSAP)
                                      F = VoIP Wireless (preferably with VMBL being
                                         displayed at the PSAP)
                                      J = VoIP Nomadic (preferably with VNOM being
                                         displayed at the PSAP)
                                      K = VoIP Enterprise Solutions –Centrex & PBX
                                         (preferably with VENT being displayed at the
                                         PSAP)

                                  All VoIP Class of Service are for both static and nomadic
                                  services with the exception of J=VoIP Nomadic. This will
                                  be used when a customer is moving from one location to
                                  another and is unsure of the class of service they should be
                                  using at that time, as it is different than their
                                  normal/predominant class of service.

Version 9, January 6, 2010                                                         Page 12 of 88
                                                                     NENA Standard Data Formats for
                                                                 9-1-1 Data Exchange & GIS Mapping
                                                                            NENA 02-010, Version 9,
                                                                                     January 6, 2010



                                  Exhibit 22 for GIS mapping was unintentionally omitted
                                  from the last version of the 02-010 document. Exhibit 22
                                  has been re-inserted into this version, no changes were
                                  made to Exhibit 22.

                                  New Class of Service for Wireless Phase II – added COS
                                  “I” that tells the PSAP the call is from a Phase II capable
                                  service, but only phase I information was available. Re-bid
                                  ALI for phase II information. Note, re-bid will not
                                  guarantee phase II information will be provided.

                                  XML Release 4.1 to accommodate I2 standard which was
                                  developed by NENA to handle VoIP calls in the current E9-
                                  1-1 system. The I2 directory includes schemas used by the
                                  I2 web services definitions (WSDLs) as well as the I2
                                  WSDLs. http://www.nena.org/xml_schemas/nena.htm
        8            03/30/2007   Establish Function of Change for MSAG Data Exchange

                                  Function of Change for MSAG options: Insert a range:
                                    FOC=I defines the current image to be inserted

                                  Delete a single range:
                                    FOC=D defines the current image to be deleted

                                  Place footer in document with reference to name formatting
                                  when sending in data to the DBMS. Last, First format is the
                                  recommended format for residential customer names.

                                  The document name has been changed to reflect the new
                                  NENA ALI Query Service standard; the document
                                  describes data formats and not protocols.

                                  The ALI Query Service Standard is available at
                                  http://www.nena.org/pages/Content.asp?CID=76&CTID=5.
                                  The formal document name is “04-005 NENA ALI Query
                                  Service Standard”.
       8.1           01/08/2008   Correction to MSAG Data exchange reserved field length.
                                  The reserved field should have been shortened 1 character
                                  due to the addition of FOC in Revision 8.
       8.2           06/10/2009   Updated all urls to agree with new web pages.



Version 9, January 6, 2010                                                        Page 13 of 88
                                                                                                NENA Standard Data Formats for
                                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                                       NENA 02-010, Version 9,
                                                                                                                January 6, 2010



               9           XX/XX/XXX         Modified Exhibit 22, GIS Data Model, Version 2.
                               X
                                             Updated to most current template by adding the following
                                             new sections:
                                             2.2 SECURITY IMPACTS SUMMARY ....................................................................................
                                             2.5 RECOMMENDATION FOR ADDITIONAL DEVELOPMENT WORK .....................................
                                             2.9 FUTURE PATH PLAN CRITERIA FOR TECHNICAL EVOLUTION .......................................
                                             2.11  ADDITIONAL IMPACTS (NON COST RELATED............................................................


297    2.5 Recommendation for Additional Development Work
298   The evolution of 9-1-1 call and data delivery from analog to IP will require additional
299   development to meet the needs of a Next Generation 9-1-1 system. New databases, processes,
300   architecture, and interfaces will require this document be updated to accommodate these
301   changes.

302    2.6 Date Compliance
303   All systems that are associated with the 9-1-1 process shall be designed and engineered to ensure
304   that no detrimental, or other noticeable impact of any kind, will occur as a result of a date/time
305   change up to 30 years subsequent to the manufacture of the system. This shall include embedded
306   application, computer based or any other type application.
307   To ensure true compliance the manufacturer shall upon request provide verifiable test results to an
308   industry acceptable test plan such as Telcordia GR-2945 or equivalent.

309    2.7 Anticipated Timeline
310   Deployment or implementation of this standard will take place as required.

311    2.8 Costs Factors
312   The implementation of the XML portion of this standard will require programming changes to all
313   applications involved in the transport and processing of XML data and may require enhancements to
314   the 911 network such as to support increased volumes of data.

315    2.9 Future Path Plan Criteria for Technical Evolution
316   In present and future applications of all technologies used for 9-1-1 call and data delivery, it is a
317   requirement to maintain the same level or improve on the reliability and service characteristics
318   inherent in present 9-1-1 system design.
319   New methods or solutions for current and future service needs and options should meet the criteria
320   below. This inherently requires knowledge of current 9-1-1 system design factors and concepts, in
321   order to evaluate new proposed methods or solutions against the Path Plan criteria.
322   Criteria to meet the Definition/Requirement:


      Version 9, January 6, 2010                                                                                     Page 14 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010


323      1. Reliability/dependability as governed by NENA‟s technical standards and other generally
324         accepted base characteristics of E9-1-1 service
325      2. Service parity for all potential 9-1-1 callers
326      3. Least complicated system design that results in fewest components to achieve needs
327         (simplicity, maintainable)
328      4. Maximum probabilities for call and data delivery with least cost approach
329      5. Documented procedures, practices, and processes to ensure adequate implementation and
330         ongoing maintenance for 9-1-1 systems
331   This basic technical policy is a guideline to focus technical development work on maintaining
332   fundamental characteristics of E9-1-1 service by anyone providing equipment, software, or services.

333    2.10 Cost Recovery Considerations
334   Normal business practices shall govern the cost recovery.

335    2.11 Additional Impacts (non cost related
336   The information or requirements contained in this NENA document are known to have XXX
337   impacts, based on the analysis of the authoring group, and development has been started. The
338   primary impacts include:
339         Improved coordination, communication, collaboration, and cooperation between 9-1-1
340          authorities, addressing authorities and other entities involved in 9-1-1 data development and
341          data delivery will be required

342    2.12 Intellectual Property Rights Policy
343   NENA takes no position regarding the validity or scope of any Intellectual Property Rights or other
344   rights that might be claimed to pertain to the implementation or use of the technology described in
345   this document or the extent to which any license under such rights might or might not be available;
346   nor does it represent that it has made any independent effort to identify any such rights.
347   NENA invites any interested party to bring to its attention any copyrights, patents or patent
348   applications, or other proprietary rights that may cover technology that may be required to
349   implement this standard.
350   Please address the information to:
351   National Emergency Number Association
352   4350 N Fairfax Dr, Suite 750
353   Arlington, VA 22203-1695
354   800-332-3911
355   techdoccomments@nena.org



      Version 9, January 6, 2010                                                             Page 15 of 88
                                                                            NENA Standard Data Formats for
                                                                        9-1-1 Data Exchange & GIS Mapping
                                                                                   NENA 02-010, Version 9,
                                                                                            January 6, 2010



356    2.13 Acronyms/Abbreviations
357   Some acronyms/abbreviations used in this document have not yet been included in the master
358   glossary. After initial approval of this document, they will be included. See NENA 00-001 - NENA
359   Master Glossary of 9-1-1 Terminology located on the NENA web site for a complete listing of terms
360   used in NENA documents.
361




      Version 9, January 6, 2010                                                         Page 16 of 88
                                                                                 NENA Standard Data Formats for
                                                                             9-1-1 Data Exchange & GIS Mapping
                                                                                        NENA 02-010, Version 9,
                                                                                                 January 6, 2010




362   3   Technical Description
363    3.1 Types of Data Exchange Formats
364   All data exchange formats utilize ASCII characters. The NENA Data Technical Committee has
365   established 4 versions of standard data formats for use by Service Providers and Data Base
366   Management System Providers when exchanging E9-1-1 data base information. Four (4) versions of
367   standard format have been defined for each of the following; ALI data exchange, MSAG data
368   exchange, Header and trailer records, Wireless data formats are included in Versions 3.1 and 4.
369   A new standard format Version 1.0 has been defined for the ALI Request Response message sent to
370   the PSAP screen.
371   Version 1 formats are the original NENA recommended formats utilizing the 240 character format
372   for Data Exchange; 160 character format for MSAG Data Exchange and 160 character format for
373   Header and Trailer records.
374   Version 2 formats recognize that the original formats needed to be expanded to accommodate
375   additional data fields critical to some data providers and also recognizing that NENA must position
376   the standard record for the future. Version 2 formats contain all data fields resident in Version 1
377   formats utilizing a 512 character format for Data Exchange; 200 character format for MSAG Data
378   Exchange and 200 character formats for Header and Trailer records.
379   Version 3 formats recognize that the previous formats were limiting distribution of data as
380   technology evolved and the Data Technical Committee, after much discussion, arrived at the present
381   NENA Version 3 format, included in this document. This format takes a “Tag Data” approach to
382   information exchange for both wireline and wireless data distribution. Benefits include flexibility,
383   faster programming changes, more efficient data transmission and smaller file sizes.
384   Version 4 formats recognize the need for an industry standard naming convention, greater flexibility
385   and faster programming changes. NENA Version 4 has been revised to support these needs and to
386   introduce reusability of defined data elements, a method to introduce Schema changes that are
387   backward compatible and do not impact operating applications. This revised XML format can be
388   supported by off the shelf XML tools to perform proper validation of XML documents. The revised
389   NENA Version 4 establishes a design philosophy for all new XML schema and data development.
390   The NENA Data Technical Committee requires that Service Providers maintain consistency by
391   utilizing formats consistent to one version; i.e. Header and Trailer records must be the same version
392   format as the Data or MSAG Exchange formats utilized.

393   Common Considerations:
394   All data exchange formats utilize ASCII characters. ASCII characters used in alpha only and
395       alpha/numeric fields should be limited to A thru Z, a thru z (some legacy systems will not
396       understand lower case), 0 thru 9, comma „, ‟, forward slash „ / ‟, semi colon „; „, ampersand „&‟,
397       and apostrophe „ ‟ ‟. Spaces are allowed with one exception----the first character of a field may

      Version 9, January 6, 2010                                                              Page 17 of 88
                                                                                    NENA Standard Data Formats for
                                                                                9-1-1 Data Exchange & GIS Mapping
                                                                                           NENA 02-010, Version 9,
                                                                                                    January 6, 2010


398      not be a space. Spaces between words are acceptable. Other characters may impact the accurate
399      processing of data.
400   Data Base Management System Providers should document how they utilize versions 1, 2, 3 and 4
401      and the fields that their software systems can utilize.
402   The “General Use” field may be used when exchange partners agree to exchange information not
403      defined.
404   Header and Trailer records must be the same version format as the Data or MSAG Exchange formats
405      utilized.
406   A full update record must be provided for all data exchange versions and function-of-change
407      updates.
408   Data TYPE indicators are as follows: A= Alpha, N=Numeric, V=Variable, AN=Alpha Numeric,
409      AV=Alpha Variable

410   3.1.1 Version 1 & 2 formats:
411        Standard field location.
412         Fixed record lengths.
413         Data exchange formats require that complete data records be exchanged.
414         All data fields are treated as “left-justified” with trailing spaces.
415         Unused fields are space-filled.

416   3.1.2 Version 3 data formats:
417        A tag data record is a record of varying length, comprised of pre-defined tag labels and the
418         associated data elements.
419         There is no particular sequence of the tag/data combinations within a Tag Data Record.
420         Each tag and its associated data is separated from all other tag/data combinations by a pre-
421          defined field separator.
422         A pre-defined End of Record character follows each Tag Data Record.
423         The receiving Data Base Management System Provider will specify the minimum set of
424          tag/data elements required by that system to uniquely identify and process the record.
425         If the field is not being used (I.E: “Street Suffix”, “Post Directional”, “Customer Code”) then
426          the label is not used.
427         Data Technical Committee authorized new tags may be added to the record without changing
428          the file format.
429         Header records will employ cycle counting to ensure a cycle of updates is not missed.

      Version 9, January 6, 2010                                                                 Page 18 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010



430         Trailer records will employ record counting to ensure a record within an update file is not
431          missed.

432   3.1.3 Version 4 Description Summary:
433        Tags are angled brackets with the data between them. An example of a start-tag and end-tag
434         is <NAM></NAM>.
435         Content is the data between the start-tag and end-tag.
436         An Element is the combination of start-tag, data and end-tag. An example of an element is
437          <NAM>JOHN DOE</NAM>.
438         Tags can have Attributes. An example is <RECORD Num=”1”> which indicates that the
439          elements for record number 1 follow this tag.
440         Elements may contain other elements. A “StreetAddressType” is an example of container
441          element with sub-elements in a group that identify the component parts for a street address
442          and can be reused wherever a “StreetAddressType” element is needed.
443
                       <xs:complexType                                    Individual components or elements
                       name=”StreetAddressType”>                          that make up a street address are
                        <xs:all>                                          housed is a container element called
                         <xs:element name=”HouseNum”/>                    StreetAddressType.
                         <xs:element name=”HouseNumSuffix/>
                         <xs:element name=”PrefixDirectional/>            This example is intended to show
                         <xs:element name=”StreetName”/>                  how related data elements may be
                         <xs:element name=”StreetSuffix/>                 grouped together and is not
                         <xs:element name=”PostDirectional”/>             intended to be accurate in form
                         <xs:element name=”MSAGCommunity”/>               or structure.
                         <xs:element name=”PostalCommunity”/>
                         <xs:element name=”StateProvince”/>               Refer to the actual XML documents
                         <xs:element name=”County”/>                      located on the NENA web site at
                         <xs:element name=”TARCode”/>                     http://www.nena.org/xml_schemas/
                         <xs:element name=”PostalZipCode”/>               nena.htm
                        </xs:all>
                       </xs:complexType>
444
445         In XML, records are referred to as “documents”.
446         The XML schema defines the structure, sequence and required elements within an XML
447          document.
448         The receiving Data Base Management System provider will determine the minimum set of
449          elements required by that system to uniquely identify and process the record.

      Version 9, January 6, 2010                                                             Page 19 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010



450          If the data is not being used (I.E: “Street Suffix”, “Post Directional”, “Customer Code”) then
451           the Element may be omitted.
452          If data is present in an XML data element but the receiving Database Management System
453           does not use the data element, the receiving Database Management System will ignore it.
454          Version 4 utilizes Generation and Release controls. A Release is a subset of a Generation. A
455           Release may be changed such as adding new tags without effecting working applications.
456           Generation changes will affect backward compatibility. A schema from a newer Generation
457           cannot be used to validate documents from a previous Generation. The NENA Data
458           Technical Committee will coordinate all Generation and Release changes.
459          Header elements will employ cycle counting to ensure a cycle of updates is not missed.
460          Trailer elements will employ record counting to ensure a record within an update file is not
461           missed.
462          Supporting documentation for the most current and all previous XML schema Generations
463           and Release s will be available on the NENA web site.
464          This document does not contain a complete description of XML elements and features.
465          Details on each XML Generation, Release, Element Type Definition and Schema
466           documentation is available on the NENA web site at
467           http://www.nena.org/xml_schemas/nena.htm. More information on XML may be found at
468           http://www.w3.org/XML/.

469   4   Recommended Reading and References
470   Refer to the NENA Master Glossary of 9-1-1 Terminology NENA-01-002 for definitions of the
471   terms used in this document.
472   Refer to the NENA 04-005 NENA ALI Query Service Standard for specifications on XML ALI
473   data exchange.




      Version 9, January 6, 2010                                                             Page 20 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010



474

475   5    Exhibits

476                                            EXHIBIT 1
477                   VERSION 1 FORMAT FOR DATA EXCHANGE (Obsolete – DO NOT USE)
478
       FIELD NAME          POSITION    BYTES   TYPE                         DESCRIPTION
      Function Code            1         1      A     Type of activity the record is being submitted for. Valid
                                                      entries:
                                                                C = Change
                                                                D = Delete
                                                                I = Insert

      NPA                      2-4      3        N    Three digit area code of the Calling Number
      Calling Number          5-11      7        N    Seven digit telephone number of the Calling Number
      House Number            12-21     10      AN    House Number. The field should be space filled if no house
                                                      number is available.
                                                      NOTE: Although the House Number field is ten
                                                      characters, it is understood that telephone companies may
                                                      only support up to 8 characters.
      House Number            22-25      4      AN    House number extension (e.g. ½). The field should be
      Suffix                                          spaced filled if no suffix applies.
      Prefix Directional      26-27      2      A     Leading street direction prefix. The field should be space
                                                      filled if no prefix applies. Valid entries:
                                                                    N        S         E       W
                                                                    NE       NW        SE      SW

      Street Name             28-67     40      AN    Valid service address of the Calling Number.
      Street Suffix           68-71     4        A    Valid street abbreviation, as defined by the U.S. Postal
                                                      Service Publication 28, Appendix C. (e.g. AVE)
      Post Directional        72-73      2      A     Trailing street direction suffix. The field should be space
                                                      filled if no suffix applies. Valid entries:
                                                                    N        S         E       W
                                                                    NE       NW        SE      SW

      Community Name         74-105     32      A     Valid service community of the street name/house number
                                                      as designated by the MSAG.
      State                  106-107    2        A    Alpha state abbreviation (e.g. TX)
      Location               108-127    20      AN    Additional address information (free formatted) describing
                                                      the exact location of the Calling Number (e.g. Apt 718)
      Customer Name          128-159    32      AN    Subscriber name associated with the Calling Number.
479
480
481
      Version 9, January 6, 2010                                                              Page 21 of 88
                                                                           NENA Standard Data Formats for
                                                                       9-1-1 Data Exchange & GIS Mapping
                                                                                  NENA 02-010, Version 9,
                                                                                           January 6, 2010


482
483                  VERSION 1 FORMAT FOR DATA EXCHANGE (Obsolete – DO NOT USE)
484
      Class of Service       160       1      AN   Value of:
                                                    1 = Residence               6   =    Coin 1 Way out
                                                    2 = Business                7   =    Coin 2 Way
                                                    3 = Residence PBX           8   =    Mobile
                                                    4 = Business PBX            9   =    Residence OPX
                                                    5 = Centrex                 0   =    Business OPX

      Type of Service        161       1      N    Value of:
                                                     0   = Not FX nor Non-Published
                                                     1   = FX in 911 serving area
                                                     2   = FX outside 911 serving area
                                                     3   = Non-Published
                                                     4   = Non-Published FX in serving area
                                                     5   = Non-Published FX outside 911 serving area
      Exchange              162-165    4      AN   Local Exchange Carrier exchange identifier for the serving
                                                   telephone office of the customer.
      ESN                   166-170    5      AN   Emergency Service Number associated with the House
                                                   Number and Street Name.

                                                   NOTE: ESN field may be space filled when the Data Base
                                                   Management System Provider is validating the address.
                                                   The Service Provider providing the E9-1-1 Selective
                                                   Routing will provide a list of ESNs available for
                                                   assignment.
      Main NPA              171-173    3      N    Three-digit area code of the Main Number associated with
                                                   the Calling Number.
      Main Number           174-180    7      N    Seven Digit telephone number of the Main Number
                                                   associated with the Calling Number.
      Order Number          181-190   10      AN   Service order number for the activity establishing this
                                                   record.
      Extract Date          191-196    6      N    Date on which the record was created in the format.
                                                   MMDDYY
      County ID             197-200    4      AN   County Identification code (usually the FIPS code)

                                                   NOTE: County Identification field is used to identify the
                                                   county of call origination. The Subcommittee recommends
                                                   use of the FIPS code assigned to each county by the U S
                                                   Census Bureau.
      Company ID            201-205    5      AN   NENA registered Company Identification code.
      Source ID               206      1      AN   Code that indicates whether data is part of the initial data
                                                   base creation process or part of the daily update process.
                                                   Daily = Space, Initial Load = C
485



      Version 9, January 6, 2010                                                           Page 22 of 88
                                                                                      NENA Standard Data Formats for
                                                                                  9-1-1 Data Exchange & GIS Mapping
                                                                                             NENA 02-010, Version 9,
                                                                                                      January 6, 2010


486                   VERSION 1 FORMAT FOR DATA EXCHANGE (Obsolete – DO NOT USE)
487
      Zip Code              207-211         5          AN      Postal Zip Code
      Zip + 4               212-215         4          AN      Postal Zip Code Extension
      General Use           216-226         11         AN      This field will be mutually used by data exchange partners
                                                               to pass information not defined in previous fields.
      Reserved              227-239         13         AN      This field is reserved for the Data Base Management
                                                               Systems Provider‟s use.
      End of Record           240           1          AN      Always an asterisk (*).
488
489   NOTE:           All fields are left justified, with trailing spaces.
490
491




      Version 9, January 6, 2010                                                                      Page 23 of 88
                                                                                 NENA Standard Data Formats for
                                                                             9-1-1 Data Exchange & GIS Mapping
                                                                                        NENA 02-010, Version 9,
                                                                                                 January 6, 2010




492                                              EXHIBIT 2
493         VERSION 1 FORMAT FOR MSAG DATA EXCHANGE (Obsolete – DO NOT USE)
494
495
496                           NAME            POSITION        BYTES           TYPE
497                      Prefix Directional       1-2            2             AN
                         Street Name             3-42            40            AN
498                      Street Suffix           43-46           4             AN
499                      Post Directional        47-48           2             AN
500                      Low Range               49-58           10            AN
501                      High Range              59-68           10            AN
                         Community Name         69-100           32             A
502                      State                  101-102          2              A
503                      Odd/Even                 103            1          O, E OR B
504                      ESN                    104-108          5             AN
                         Extract Date           109-114          6          MMDDYY
505
                         PSAP ID                115-118          4             AN
506                      County ID              119-122          4             AN
507                      Exchange               123-126          4             AN
508                      General Use            127-146          20            AN
                         Reserved               147-159          13            AN
509                      End of Record            160            1          Always “*”
510
511                     NOTE: All fields are left justified, with trailing spaces.
512




      Version 9, January 6, 2010                                                              Page 24 of 88
                                                                                             NENA Standard Data Formats for
                                                                                         9-1-1 Data Exchange & GIS Mapping
                                                                                                    NENA 02-010, Version 9,
                                                                                                             January 6, 2010



513                                                     EXHIBIT 3
514       VERSION 1 HEADER FORMAT FOR DATA EXCHANGE (Obsolete – DO NOT USE)
515
                              NAME                POSITION            BYTES                TYPE
                       Header Indicator                 1-5                5              “UHL”
                       Extract Date                    6-11                6             MMDDYY
                       Company Name                    12-61              50                 AN
                       Cycle Counter                   62-67               6                  N
                       County ID                       68-71               4                 AN
                       State                           72-73               2                  A
                       General Use                     74-93              20                 AN
                       Reserved                       94-159              66                AN
                       End of Record                   160                 1             Always “*”
516
517           NOTE: All fields are left-justified, with trailing spaces, except the Cycle Counter, this field will
518                 be right-justified with leading spaces.
519                    Header records will employ cycle counting to ensure a cycle of updates is not missed.
520                    When used with an ALI data file, the reserved field will be expanded to 146 bytes.

521
522
523
524
525
526
527
528
529
530
531




      Version 9, January 6, 2010                                                                             Page 25 of 88
                                                                                              NENA Standard Data Formats for
                                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                                     NENA 02-010, Version 9,
                                                                                                              January 6, 2010



532

533                                                      EXHIBIT 4
534       VERSION 1 TRAILER FORMAT FOR DATA EXCHANGE (Obsolete – DO NOT USE)
535
536                              NAME               POSITION             BYTES               TYPE
                          Trailer Indicator               1-5                5               “UTL”
537
                          Extract Date                    6-11               6             MMDDYY
538
                          Company Name                   12-61               50                  AN
539                       Record Count                   62-70               9                   N
540                       Reserved                      71-159               89                  AN
541                       End of Record                   160                1             Always “*”
542
543           NOTE: All fields are left justified, with trailing spaces, except for the Record
544                  Count; this field will be right-justified with leading spaces.
545           Trailer records will employ record counting to ensure a record within an update
546                    file is not missed
547                    When used with an ALI data file, the „Reserved‟ field will be expanded
548                    to 169 bytes.

549




      Version 9, January 6, 2010                                                                           Page 26 of 88
                                                                       NENA Standard Data Formats for
                                                                   9-1-1 Data Exchange & GIS Mapping
                                                                              NENA 02-010, Version 9,
                                                                                       January 6, 2010



550                                            EXHIBIT 5
551                                VERSION 2.0 FORMAT FOR DATA EXCHANGE
552                          VERSION 2.0 FORMAT FOR MSAG DATA EXCHANGE
553                        VERSION 2.0 HEADER FORMAT FOR DATA EXCHANGE
554                        VERSION 2.0 TRAILER FORMAT FOR DATA EXCHANGE
555
556                     Have Been Replaced by Version 2.1 Formats
557                             See Exhibits 6 through 9
558
559




      Version 9, January 6, 2010                                                    Page 27 of 88
                                                                             NENA Standard Data Formats for
                                                                         9-1-1 Data Exchange & GIS Mapping
                                                                                    NENA 02-010, Version 9,
                                                                                             January 6, 2010




560                                           EXHIBIT 6
561                           VERSION 2.1 FORMAT FOR DATA EXCHANGE
562
       FIELD NAME          POSITION   BYTES   TYPE   DESCRIPTION
      Function Code            1        1      A     Type of activity the record is being submitted for.
                                                     Valid entries:
                                                                C      = Change
                                                                D      = Delete
                                                                 I     = Insert
                                                                U      = Unlock
                                                                M      = Migrate
      NPA                     2-4      3        N    Three-digit area code of the Calling Number.
      Calling Number         5-11      7        N    Seven-digit telephone number of the Calling Number.
      House Number           12-21     10      AN    House number. The field should be space filled if no house
                                                     number is available.

                                                     NOTE: Although the House Number field is ten
                                                     characters, it is understood that telephone
                                                     companies may only support up to 8 characters.
      House Number           22-25      4      AN    House number extension (e.g. ½). The field should be
      Suffix                                         space filled if no suffix applies.
      Prefix Directional     26-27      2      A     Leading street direction prefix. The field should be space
                                                     filled if no prefix applies. Valid entries:
                                                             N        S         E       W
                                                             NE       NW        SE      SW
      Street Name            28-87     60      AN    Valid service address of the Calling Number.
      Street Suffix          88-91     4        A    Valid street abbreviation, as defined by the U. S. Postal
                                                     Service Publication 28, Appendix C. (e.g. AVE)
      Post Directional       92-93      2      A     Trailing street direction suffix. The field should be space
                                                     filled if no suffix applies. Valid entries:
                                                             N        S         E       W
                                                             NE       NW        SE      SW
      Community Name        94-125     32      A     Valid service community of the street name/house number
                                                     as designated by the MSAG.
      State                 126-127    2        A    Alpha state abbreviation (e.g. TX)
      Location              128-187    60      AN    Additional address information (free formatted) describing
                                                     the exact location of the Calling Number (e.g. Apt 718).
      Customer Name         188-219    32      AN    Subscriber name associated with the Calling
                                                     Number. Preferred format for an individual customer
                                                     name (not a business) is: Last, First and, optionally, a
                                                     suffix which may be generation (Jr, III) and/or title (Phd,
                                                     Esq, MD). Honorifics (Mr., Mrs, Ms.) should not be
                                                     included as part of the name.
563

      Version 9, January 6, 2010                                                             Page 28 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010


564                                 VERSION 2.1 FORMAT FOR DATA EXCHANGE
565
       FIELD NAME        POSITION       BYTES   TYPE   DESCRIPTION
      Class of Service      220           1      AN    Value of:
                                                        1 = Residence              8   =    Mobile
                                                        2 = Business               9   =    Residence
                                                                                            OPX
                                                        3   = Residence PBX        0   =    Business OPX
                                                        4   = Business PBX         A   =    Customer
                                                                                            Owned Coin
                                                                                            Telephone
                                                                                            (COCT)
                                                        5   = Centrex              B   =    Not Available
                                                                                                     4
                                                                                            Footnote
                                                        6   = Coin 1 Way out       G   =    Wireless Phase
                                                                                            I
                                                        7   = Coin 2 Way           H   =    Wireless Phase
                                                                                            II
                                                        I = Wireless Phase
                                                            II with Phase I
                                                            information
                                                        V = VoIP Services          C   =    VoIP Residence
                                                            Default COS
                                                        D = VoIP Business          E   =    VoIP Coin/Pay
                                                                                            Phone
                                                         F = VoIP Wireless           J =    VoIP Nomadic
                                                            = VoIP Enterprise               For all VoIP
                                                         K     Services –                   COS see notes
                                                               Centrex & PBX                on page 13
                                                         T = Telematics
      Type of Service      221            1       N    Value of:
                                                         0   = Not FX nor Non-Published
                                                         1   = FX in 911 serving area
                                                         2   = FX outside 911 serving area
                                                         3   = Non-Published
                                                         4   = Non-Published FX in serving area
                                                         5   = Non-Published FX outside 911 serving area
                                                         6   = Local Ported Number (LNP)
                                                         7   = Interim Ported Number
      Exchange            222-225         4      AN    Local Exchange Carrier exchange identifier for the serving
                                                       telephone office of the customer.
      ESN                 226-230         5      AN    Emergency Service Number associated with the House
                                                       number and Street Name.
                                                       NOTE: ESN field may be space filled when the Data Base
                                                       Management System Provider is validating the address.
                                                       The Service Provider providing the E9-1-1 Selective
                                                       Routing will provide a list of ESNs available for
                                                       assignment.
566

      Version 9, January 6, 2010                                                             Page 29 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010


567                                 VERSION 2.1 FORMAT FOR DATA EXCHANGE
568
       FIELD NAME        POSITION       BYTES   TYPE   DESCRIPTION
      Main NPA            231-233         3      N     Three-digit area code of the Main Number associated with
                                                       the Calling Number.
      Main Number         234-240         7       N    Seven Digit telephone number of the Main Number
                                                       associated with the Calling Number.
      Order Number        241-250        10      AN    Service order number for the activity establishing this
                                                       record.
      Extract Date        251-256         6       N    Date on which the record was created in the format
                                                       MMDDYY
      County ID           257-260         4      AN    County Identification Code (usually the FIPS code)
                                                       NOTE: County Identification field is used to identify the
                                                       county of call origination. The Subcommittee recommends
                                                       use of the FIPS code assigned to each county by the U S
                                                       Census Bureau.
      Access              261-265         5      AN    NENA registered Company Identification code of the
      Infrastructure                                   Access Infrastructure Provider
      Provider
      (Company ID 1)
      Source ID            266            1      AN    Code that indicates whether data is part of the initial data
                                                       base creation process or part of the daily update process.
                                                            Daily = Space, Initial Load = C
      Zip Code            267-271        5       AN    Postal Zip Code
      Zip + 4             272-275        4       AN    Postal Zip Code Extension
      General Use         276-286        11      AN    This field will be mutually used by data exchange partners
                                                       to pass information not defined in previous fields.
      Customer Code       287-289        3       AN    Code used to uniquely identify a customer.
      Comments            290-319        30      AN    Optional notes, may be displayed at PSAP
      X Coordinate        320-328        9       AN    Longitude/ X coordinate
      Y Coordinate        329-337        9       AN    Latitude/ Y coordinate
      Z Coordinate        338-342        5       AN    Structure elevation
      Cell ID             343-348        6       AN    Identification number indicating a geographic region of
                                                       cellular coverage.
      Sector ID             349          1       AN    Sub set/section of a cell.
      TAR Code            350-355        6       AN    Taxing Area Rate Code
      Reserved            356-376        21      AN    This field is reserved for the Data Base Management
                                                       System Provider‟s use.
      ALT #               377-386        10       N    Customer Number being remote call forwarded in Interim
                                                       Number Portability service.
      Expanded Extract    387-394         8       N    Date on which the record was created in the format
      Date                                             YYYYMMDD
      NENA Reserved       395-475        81      AN    This field is reserved for NENA Data Technical Committee
                                                       Assignment
      Data Provider ID    476-480         5      AN    NENA registered Company Identification code of the Data
      (Company ID 2)                                   Provider (Note 1)
569


      Version 9, January 6, 2010                                                              Page 30 of 88
                                                                                             NENA Standard Data Formats for
                                                                                         9-1-1 Data Exchange & GIS Mapping
                                                                                                    NENA 02-010, Version 9,
                                                                                                             January 6, 2010


570                                   VERSION 2.1 FORMAT FOR DATA EXCHANGE
571
       FIELD NAME         POSITION           BYTES          TYPE       DESCRIPTION
      Reserved             481-511            31             AN        This field is reserved for the Data Base Management System
                                                                       Provider‟s use.
      End of Record            512              1            AN        Always an asterisk (*).
572
573
574           NOTE:     All fields are left justified, with trailing spaces.
575                     The Service Provider providing E9-1-1 Selective Routing must provide the
576                     governmental entity with a list of ESNs available for assignment by MSAG
577                     development personnel.
578           NOTE 1: The Data Provider ID (Company ID 2) field is used to carry the NENA Company ID of
579                   a PS/911 data provider. The NENA Reserved field has been reduced by 5 bytes to
580                   accommodate the Data Provider ID field. In addition the “Company ID” field that
581                   represents the Dialtone Provider NENA Company ID has been renamed to “Access
582                   Infrastructure Provider ID” (Company ID 1)and the definition clarified.

583
584
585




      Version 9, January 6, 2010                                                                            Page 31 of 88
                                                                                          NENA Standard Data Formats for
                                                                                      9-1-1 Data Exchange & GIS Mapping
                                                                                                 NENA 02-010, Version 9,
                                                                                                          January 6, 2010



586

587                                                  EXHIBIT 7
588                      VERSION 2.1 FORMAT FOR MSAG DATA EXCHANGE
589
590                             NAME             POSITION           BYTES              TYPE
                          Prefix Directional            1-2            2                 AN
591
                          Street name                  3-62            60                AN
592
593                       Street Suffix               63-66            4                 AN
594                       Post Directional            67-68            2                 AN
595                       Low Range                   69-78            10                AN
596                       High Range                  79-88            10                AN
597                       Community Name              89-120           32                 A
598                       State                      121-122           2                  A
599                       Odd/Even                     123             1              O, E or B
600                       ESN                        124-128           5                 AN
601                       Extract Date               129-134           6              MMDDYY
602                       PSAP ID                    135-138           4                 AN
603                       County ID                  139-142           4                 AN
604                       Exchange                   143-146           4                 AN
605                       General Use                147-166           20                AN
606                       TAR Code                   167-172           6                 AN
607                       Function of Change           173             1                  A
608
                          Reserved                   174-191           18                AN
609
610                       Expanded Extract           192-199           8                  N
611                       Date
612                       End of record                200              1             Always “*”
613
614                      NOTE: All fields are left justified, with trailing spaces.
615
616
617   Function of Change for MSAG options
618   Insert a single range:
619      FOC=I defines the current image to be inserted
620   Delete a single range:
621      FOC=D defines the current image to be deleted
622   Changes to an MSAG Range should appear in the Delta Files as a “D” record followed by an “I”
623   record.
624
625
626
627
      Version 9, January 6, 2010                                                                       Page 32 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010



628   Deprecated MSAG FOC options
629
630   Some DBMS providers currently provide delta MSAG files using FOC codes that were documented
631   for Version 3.1 in the previous versions of this document. These codes are not part of the NENA 02-
632   010 standard – but are shown below for documentation.
633   Insert a range:
634      FOC=I defines the current image to be inserted (no FOC=X used)
635   Change a single range:
636      FOC=X comes first to define the current (before) image
637      FOC=C comes second to define the after image
638   Delete a single range:
639      FOC=D defines the current image to be deleted (no FOC=X used)
640   Split one range:
641       FOC=X comes first to define the current (before) image
642       FOC=S or L comes next (two or more FOC=S records) to define two or more ranges after the
643   split (S&L are the same FOC and can not be used interchangeably)
644   Join two or more ranges:
645      FOC=X comes first to define two or more before images – must be in a sending sequence by
646   house number
647       FOC=J follows to define the single after image for the join (two or more X records must proceed
648   the J)
649




      Version 9, January 6, 2010                                                           Page 33 of 88
                                                                                             NENA Standard Data Formats for
                                                                                         9-1-1 Data Exchange & GIS Mapping
                                                                                                    NENA 02-010, Version 9,
                                                                                                             January 6, 2010



650                                                     EXHIBIT 8
651                     VERSION 2.1 HEADER FORMAT FOR DATA EXCHANGE
652
                                NAME                   POSITION           BYTES              TYPE
                       Header Indicator                      1-5              5              “UHL”
                       Extract Date                         6-11              6            MMDDYY
                       Company Name                        12-61             50                AN
                       Cycle Counter                       62-67              6                 N
                       County ID                           68-71              4                AN
                       State                               72-73              2                 A
                       General Use                         74-93             20                AN
                       Release Number                      94-96              3                 N
                       Format Version                        97               1                 N
                       Expanded Extract Date               98-105            8                  N
                       Reserved                           106-199            94                AN
                       End of Record                        200               1            Always “*”
653
654
655           NOTE: All fields are left-justified, with trailing spaces, except the Cycle Counter, this field will
656                 be right-justified with leading spaces.
657                    Header records will employ cycle counting to ensure a cycle of updates is not is
658                    missed.
659                    When used with an ALI data file, the „Reserved‟ field will be expanded to 406 bytes
660                    (when used with an ALI data file).
661
662




      Version 9, January 6, 2010                                                                             Page 34 of 88
                                                                                            NENA Standard Data Formats for
                                                                                        9-1-1 Data Exchange & GIS Mapping
                                                                                                   NENA 02-010, Version 9,
                                                                                                            January 6, 2010



663                                                     EXHIBIT 9
664                    VERSION 2.1 TRAILER FORMAT FOR DATA EXCHANGE
665
                                NAME                 POSITION            BYTES              TYPE
                       Trailer Indicator                   1-5               5               “UTL
                       Extract Date                       6-11               6            MMDDYY
                       Company Name                       12-61              50               AN
                       Record Count                       62-70              9                 N
                       Expanded Extract Date             71-78               8                 N
                       Reserved                          79-199             121               AN
                       End of Record                       200               1            Always “*”
666
667
668           NOTE: All fields are left justified, with trailing spaces, except for the Record Count; this field
669                 will be right-justified with leading spaces.
670                    Trailer records will employ record counting to ensure a record within an update file is
671                    not missed.
672                    When used with an ALI data file, the „Reserved‟ field will be expanded to 433 bytes.
673
674
675




      Version 9, January 6, 2010                                                                            Page 35 of 88
                                                                                  NENA Standard Data Formats for
                                                                              9-1-1 Data Exchange & GIS Mapping
                                                                                         NENA 02-010, Version 9,
                                                                                                  January 6, 2010




676                                             EXHIBIT 10
677                         VERSION 3.1 FORMAT FOR DATA EXCHANGE
678
             NAME         LABEL    MAX #   TYPE                             DESCRIPTION
                                   BYTES
       Record Type        DAT or     0      A     Indicates start of data record (label only, no data follows). Valid
                           RTN                    labels:
                                                  DAT = Data Record sent from the Service Provider to the Data
                                                  Base Management System Provider
                                                  RTN = Data record returned from the Data Base Management
                                                  System Provider to the Service Provider
       Status Indicator    STI       1     AN     Record status indicator.
                                                  Valid entries:
                                                    E = Error
                                                    C = Completed
                                                    P = Pending processing
                                                    U = Unprocessed Gateway received but not sent to
                                                             processing, (future date)


       Function of         FOC       1      A     Type of activity the record is being submitted for.
       Change                                     Valid “x” entries:
                                                   C = Change
                                                   D = Delete
                                                   I = Insert
                                                   U = Unlock
                                                   M = Migrate
                                                   E = Delete error record


       Calling Party       CPN      10      N     Number of the Calling Party.
       Number                                     Emergency Location Identification Number (ELIN) – A valid
                                                  North American Numbering Plan format telephone number
                                                  assigned to the Multi-Line Telephone Systems Operator by the
                                                  appropriate authority that is used to call to a PSAP and is used to
                                                  retrieve the ALI for the PSAP. The ELIN may be the same
                                                  number as the ANI. The North American Numbering Plan number
                                                  may in some cases not be a dialable number.
                                                   Footnote 3
679
680




      Version 9, January 6, 2010                                                                  Page 36 of 88
                                                                                      NENA Standard Data Formats for
                                                                                  9-1-1 Data Exchange & GIS Mapping
                                                                                             NENA 02-010, Version 9,
                                                                                                      January 6, 2010


681                                    VERSION 3.1 FORMAT FOR DATA EXCHANGE
682
                NAME           LABEL    MAX #   TYPE                            DESCRIPTION
                                        BYTES
          House Number         HNO        10    AN     House Number. Footnote 1,2,3
          House Number          HNS       4     AN     House number extension (e.g. ½). Footnote 1,2,3
          Suffix
          Prefix Directional    PRD       2      A     Leading street direction prefix. Footnote 1,2,3
                                                       Valid “x” Entries:
                                                              N       S          E       W
                                                              NE      NW         SE      SW
          Street Name           STN       60    AN     Valid service address of the Calling Party Number. Footnote 1,2,3
          Street Suffix         STS       4      A     Valid street abbreviation, as defined by the U S Postal Service
                                                       Publication 28, Appendix C. (e.g. AVE) Footnote 1,2,3
          Post Directional      POD       2      A     Trailing street direction suffix. Footnote 1,2,3
                                                       Valid “x” entries:
                                                              N        S          E       W
                                                              NE       NW         SE      SW
          MSAG Community       MCN        32     A     Valid service community name as identified by the MSAG.
          Name                                         Footnote 1,2,3
          Postal Community      PCN       32     A     Valid service community name as identified by the U S Postal
          Name                                         Service. Footnote 3
          State/Province        STA       2      A     Alpha US state, Canadian province abbreviation e.g., TX
                                                       (Texas), ON (Ontario) Footnote 1,2,3
          Location              LOC       60    AN     Additional location information (free formatted) describing the
                                                       exact location of the Calling Party Number (e.g., Apt 718, or cell
                                                       sector A)
                                                       Emergency Response Location (ERL) – A Location to which a 9-
                                                       1-1 emergency response team may be dispatched. The location
                                                       should be specific enough to provide a reasonable opportunity for
                                                       the emergency response team to quickly locate a caller anywhere
                                                       within it.
                                                       Footnote 2,3 This information may be displayed at the PSAP
          Landmark Address     LMK        60    AN     Landmark or Vanity address such as “One Rockefeller Plaza”
683




      1   Where an MSAG exists, must fit the MSAG entry.
      2   Primary address associated with the Calling Party Number
      3 Must include all TN USERS information on all Multi-Line Telephone Systems that will facilitate the
      implementation of enhanced 9-1-1 on all PBX, Key, Hybrid and Centrex Systems. Resellers must
      supply end user specific name and location information, not information pertaining to the name and
      location of the Reseller.
      Version 9, January 6, 2010                                                                         Page 37 of 88
                                                                                     NENA Standard Data Formats for
                                                                                 9-1-1 Data Exchange & GIS Mapping
                                                                                            NENA 02-010, Version 9,
                                                                                                     January 6, 2010


684                                  VERSION 3.1 FORMAT FOR DATA EXCHANGE
685
                NAME         LABEL    MAX #    TYPE                            DESCRIPTION
                                      BYTES
          Also Rings At      ARA        60      AN     Secondary address for the Calling Party Number that rings at 2
          Address                                      locations. Not validated against the MSAG. Footnote3 Not
                                                       applicable to dual service.
                                                       This information may be displayed at the PSAP
          Customer Name      NAM        32      AN     Subscriber name associated with the Calling Number. Preferred
                                                       format for an individual customer name (not a business) is: Last,
                                                       First and, optionally, a suffix which may be generation (Jr, III)
                                                       and/or title (Phd, Esq, MD). Honorifics (Mr., Mrs, Ms.) should
                                                       not be included as part of the name.
          Class of Service    CLS       1       AN     Valid entries:
                                                         1 = Residence                8 = Mobile
                                                         2 = Business                 9 = Residence OPX
                                                         3 = Residence PBX            0 = Business OPX
                                                         4 = Business PBX             A = Customer Owned Coin
                                                                                              Telephone (COCT)
                                                         5 = Centrex                  B = Not Available Footnote4
                                                         6 = Coin 1 Way out           G = Wireless Phase I
                                                         7 = Coin 2 Way               H = Wireless Phase II
                                                         I = Wireless Phase II
                                                                with Phase I
                                                                Information
                                                         V = VoIP Services            C = VoIP Residence
                                                                Default COS
                                                         D = VoIP Business            E = VoIP Coin/Pay Phone
                                                         F = VoIP Wireless            J = VoIP Nomadic
                                                         K = VoIP Enterprise                  For all VoIP COS see notes
                                                                Services –                    on page 13
                                                                Centrex & PBX
                                                         T = Telematics
          Type of Service     TYS       1       AN     Valid entries:
                                                         0    = Not FX nor Non-Published
                                                         1    = FX in 911 serving area
                                                         2    = FX outside 911 serving area
                                                         3    = Non-Published
                                                         4    = Non-Published FX in serving area
                                                         5    = Non-Published FX outside 911 serving area
                                                         8    = PSALI Published
                                                         9    = PSALI Non-Published

          Exchange            EXC       4       AN     A defined area, served by one or more telephone Central Offices,
                                                       within which a Local Exchange Carrier furnishes service. Footnote
                                                       5



      4    NA = not available – class of service for an ESCO failure
      Version 9, January 6, 2010                                                                     Page 38 of 88
                                                                                     NENA Standard Data Formats for
                                                                                 9-1-1 Data Exchange & GIS Mapping
                                                                                            NENA 02-010, Version 9,
                                                                                                     January 6, 2010


686                                   VERSION 3.1 FORMAT FOR DATA EXCHANGE
687
               NAME           LABEL    MAX #   TYPE                           DESCRIPTION
                                       BYTES
          Emergency Service    ESN       5     AN     Emergency Service Number associated with the House Number
          Number (ESN)                                and Street Name and Community Name.
                                                      Note: The Service Provider, providing the E9-1-1 Selective
                                                      Routing will assign ESNs.
          Main Telephone      MTN        10     N     Ten-digit telephone number of the Main Billing Number
          Number                                      associated with the Calling Party Number. Format:
                                                      NPANXXXXXX Footnote3
          Call Back Number    CBN        10    AN     Telephone Number that can be dialed to reach a specific calling
                                                      party. The call back number must be a dialable number and used as
                                                      a back up if the displayed number cannot be reached. Used for
                                                      both wireline and wireless calls. Footnote3
          P-ANI                PNI       10    AN     Pseudo ANI or locally specific code identifying the receiving
                                                      antenna for the wireless 9-1-1 call for routing purposes.
          Order Number        ORD        10    AN     Service order number for the activity associated with this record.
          Completion Date     CPD        10     N     Completion Date in format CCYY-MM-DD
          County ID           COI        5     AN     County Identification code (usually the FIPS code).
                                                      Note: County Identification field is used to identify the county of
                                                      call origination. The Committee recommends use of the FIPS code
                                                      assigned to each county by the U S Census Bureau.
          Access               CPF       5     AN     NENA registered Company Identification code for Service
          Infrastructure                              Provider providing the network access to the end user customer
          Provider (Company                           (wireline, wireless, IP, etc.).
          ID 1)
          Data Provider ID     CPS       5     AN     NENA registered Company Identification code for Service
          (Company ID 2)                              Provider/Reseller/Private Switch supplying ALI record source
                                                      information.
          Postal/Zip Code      ZIP       10    AN     Postal or Zip code. Format: NNNNN-NNNN or ANANAN
                                                      Footnote 3
          Customer Code       CUS        3     AN     Code used to uniquely identify a wireline customer
          Comments            CMT        30    AN     Optional notes, may be displayed at PSAP
                                                      TN USERS on MLTS can include any pertinent information that
                                                      will assist in reducing response time such as – contact security
                                                      department, contact front desk, etc. Footnote3
          TAR Code             TAR       6     AN     Taxing Area Rate Code
          Alternate            ALT       10     N     Remote Call Forwarding number used during Interim Number
          Telephone Number                            Portability-NPANXXXXXX
          Return Code         RCN        3      N     Code indicating specific processing error code or processing
          Number                                      completed successfully. (May be used as many times as
                                                      necessary.)
                                                      Valid "x" entries:
                                                      Not present (or 000 if used) = processing completed successfully
                                                      XXX = Valid NENA Standard Error Code
688
      5The Data Technical Committee strongly recommends that all processing edits be removed from this
      Label due to technological changes requiring improved data security measures.
      Version 9, January 6, 2010                                                                    Page 39 of 88
                                                                                    NENA Standard Data Formats for
                                                                                9-1-1 Data Exchange & GIS Mapping
                                                                                           NENA 02-010, Version 9,
                                                                                                    January 6, 2010


689                                 VERSION 3.1 FORMAT FOR DATA EXCHANGE
690
             NAME           LABEL    MAX #   TYPE                             DESCRIPTION
                                     BYTES
       Special Attention     SAI       1     AN     Calls that require special attention. Valid entries:
       Indicator                                    1 = TTY call
                                                    2 = ACN = Automatic crash/collision notification
       Common Language       CLI       11    AN     CLLI code of the local loop central office for the 911 calling party.
       Location Indicator
       (CLLI)
       General Use 1         GU1       60    AN     This field will be mutually used by data exchange partners to pass
                                                    information not defined in previous fields.
       General Use 2         GU2       60    AN     This field will be mutually used by data exchange partners to pass
                                                    information not defined in previous fields.
       General Use 3         GU3       60    AN     This field will be mutually used by data exchange partners to pass
                                                    information not defined in previous fields.
       General Use 4         GU4       60    AN     This field will be mutually used by data exchange partners to pass
                                                    information not defined in previous fields.
       General Use 5         GU5       60    AN     This field will be mutually used by data exchange partners to pass
                                                    information not defined in previous fields.
       General Use 6         GU6       60    AN     This field will be mutually used by data exchange partners to pass
                                                    information not defined in previous fields.
       General Use 7         GU7       60    AN     This field will be mutually used by data exchange partners to pass
                                                    information not defined in previous fields.
       General Use 8         GU8       60    AN     This field will be mutually used by data exchange partners to pass
                                                    information not defined in previous fields.
       Longitude            LON        11     N     Longitude/X coordinate. Right Justified; pad field with zeros or
                                                    spaces to left of decimal degrees. +long: east of Greenwich; -long:
                                                    west of Greenwich. When Phase II location cannot be provided,
                                                    Phase I information should be reported, i.e., the cell site or sector
                                                    where the call is received. (Can be used for wireline) Sample:
                                                    +000.000000 , -000.000000 Footnote3
       Latitude              LAT       10     N     Latitude/Y coordinate. Right Justified; pad field with zeros or
                                                    spaces to left of decimal degrees. +lat: north of equator; -lat: south
                                                    of equator. When Phase II location cannot be provided, Phase I
                                                    information should be reported, i.e., the cell site or sector where
                                                    the call is received. (Can be used for wireline) Sample:
                                                    +00.000000 , -00.000000 Footnote3
       Elevation             ELV       6      N     Elevation/Altitude indicated as height above mean sea level,
                                                    measured in meters. Right Justified; pad field with zeros or
                                                    spaces. (Can be used for wireline)
                                                    Sample: +00000 , -00000        Footnote3
       Cell Site ID          CEL       6     AN     Identification number indicating a geographic region of cellular
                                                    coverage. . When Phase II location cannot be provided, Phase I
                                                    information should be reported, i.e., the cell site or sector where
                                                    the call is received.
691



      Version 9, January 6, 2010                                                                     Page 40 of 88
                                                                                              NENA Standard Data Formats for
                                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                                     NENA 02-010, Version 9,
                                                                                                              January 6, 2010


692                                    VERSION 3.1 FORMAT FOR DATA EXCHANGE
693
             NAME            LABEL       MAX #      TYPE                                DESCRIPTION
                                         BYTES
       Sector ID               SEC         2          AN      Sub set/section of a cell. When Phase II location cannot be
                                                              provided, Phase I information, i.e., the cell site or sector where the
                                                              call is received should be reported.
694
695
696   The items below do not require a “Label” only the symbol shown
       Field Separator    |        1        AN       A “pipe” is to be utilized for the field separator
                                                     (ASCII HEX-7C)
       End of record NL  NL        1        AN       The NEW LINE character is a single character that identifies the
                                                     end of record in all cases for all records. (ASCII HEX-0A)
697
698
699

700   5.1.1 Data Record Format Example:
701   DAT|FOC|CPN..........|HNO..........|PRD..|STN....................|STS....|MCN....................|STA..|LOC..
702   ..........................|NAM...........................................|CLS.|TYS.|MTN..........|CPD........|CPF.....|NL
703   NOTE: If the field is not being used (I.E: “Street Suffix”, “Post Directional”, “Customer Code”) then the label is not
704         used. It is also not necessary for the labels to be in any particular order. Fields may be added to the record
705         without changing the file format.
706            The Service Provider, providing E9-1-1 Selective Routing must provide the governmental entity
707            with a list of ESNs available for assignment by MSAG development personnel.
708




      Version 9, January 6, 2010                                                                               Page 41 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010



709                                            EXHIBIT 11
710                            VERSION 3.1 FORMAT FOR MSAG DATA EXCHANGE
711
               NAME            LABEL   MAX #   TYPE                       DESCRIPTION
                                       BYTES
          Record Type            MSG     0            Indicates start of MSAG record (label only, no data
                                                      follows)
          Function of            FOC     1       A    Type of activity the record is being submitted for. Valid
          Change                                      entries6:
                                                       D = Delete
                                                        I = Insert

          Prefix Directional     PRD     2      AN    Leading street direction prefix Valid “x” Entries:
                                                                 N        S          E       W
                                                                 NE       NW         SE      SW
          Street Name            STN     60     AN    Valid service address of the Calling Party Number.
          Street Suffix          STS     4      AN    Valid street abbreviation, as defined by the U S Postal
                                                      Service Publication 28, Appendix C. (e.g. AVE)
          Post Directional       POD     2      AN    Trailing street direction suffix. -Valid “x” entries:
                                                                 N        S          E       W
                                                                 NE       NW         SE      SW
          Low Range              LOR     10     AN    The lowest house number that is included in this ESN
                                                      definition
          High Range             HIR     10     AN    The highest house number that is included in this ESN
                                                      definition
          MSAG Community         MCN     32      A    Valid service community name as defined by the MSAG
          Name
          Postal Community       PCN     32      A    Valid service community name as defined by the U S Postal
          Name                                        Service
          State/Province         STA     2       A    Alpha U.S. state, Canadian province abbreviation i.e., TX
                                                      (Texas), ON (Ontario)
          Odd/Even               OEN     1       A    Valid “x” entries:
                                                       O = Odd numbering only
                                                       E = Even numbering only
                                                       B = Both odd and even numbering

712
713




      6   See Version 2.1 MSAG FOC for more details: Function of Change for MSAG options


      Version 9, January 6, 2010                                                              Page 42 of 88
                                                                                               NENA Standard Data Formats for
                                                                                           9-1-1 Data Exchange & GIS Mapping
                                                                                                      NENA 02-010, Version 9,
                                                                                                               January 6, 2010


714                                VERSION 3.1 FORMAT FOR MSAG DATA EXCHANGE
715
            NAME              LABEL          MAX #         TYPE                           DESCRIPTION
                                             BYTES
       Emergency Service         ESN             5           AN       Emergency Service Number associated with the House
       Number (ESN)                                                   Number and Street Name and Community Name.
                                                                      Note: The Service Provider, providing the E9-1-1 Selective
                                                                      Routing will assign ESNs.
       Completion Date           CPD            10            N       Completion date in format CCYY-MM-DD
       PSAP ID                   PSI            4            AN       Code identifying the PSAP associated with the assigned
                                                                      ESN
       County ID                 COI             5           AN       County Identification code (usually the FIPS code).
                                                                      Note: County Identification field is used to identify the
                                                                      county of call origination. The Committee recommends use
                                                                      of the FIPS code assigned to each county by the U S Census
                                                                      Bureau.
       Exchange                  EXC             4           AN       A defined area, served by one or more Telephone Central
                                                                      Offices, within which a Local Exchange Carrier furnishes
                                                                      service.
       TAR Code                  TAR             6           AN       Taxing Area Rate Code associated with this House Number
                                                                      range, Street Name and Community Name
       E9-1-1 Control            SRT            11           AN       9-1-1 Control Office CLLI
       Office
       General Use 1             GU1            60           AN       This field will be mutually used by data exchange partners
                                                                      to pass information not defined in previous fields.
       General Use 2             GU2            60           AN       This field will be mutually used by data exchange partners
                                                                      to pass information not defined in previous fields.
716
717   The items below do not require a “Label” only the symbol shown
       Field Separator        |                           A “pipe” is to be utilized for the field separator (ASCII
                                                          HEX-7C)
       End of record        NL                            A NEW LINE character is a single character that identifies
                                                          the end of record in all cases for all records. (ASCII HEX-
                                                          0A)
718

719   6    MSAG Record Format Example:
720   MSG|FOC.|PRD..|STN.......................................|STS....|LOR..........|HIR..........|MCN.......................
721   ..........|PCN.................................|STA..|OEN.|ESN.....|CPD........|EXC....|SRT...........|GU1................
722   .....................................................................|NL
723   NOTE: If the field is not being used (I.E: General Use) then the label is not used. It is also not necessary for the labels
724   to be in any particular order. Fields may be added to the record without changing the file format.

725




      Version 9, January 6, 2010                                                                               Page 43 of 88
                                                                                   NENA Standard Data Formats for
                                                                               9-1-1 Data Exchange & GIS Mapping
                                                                                          NENA 02-010, Version 9,
                                                                                                   January 6, 2010



726                                             EXHIBIT 12
727                        VERSION 3.1 HEADER FORMAT FOR DATA EXCHANGE
728
            NAME            LABEL    MAX #       TYPE                     DATA DESCRIPTION
                                     BYTES
       Record Type            HDR        0          A     Indicates start of header record (label only, no data follows)
       Record Identifier      TST        3         AN     Test Records Only
       Extract Date           EXD       10          N     Year, Month, Day the data was processed, Format: CCYY-
                                                          MM-DD
       Company Name           CON       50         AN     Name of Company forwarding file
       Cycle Counter          CYC        9          N     Sequential number, 1-999,999,999
       Record Count           REC        9          N     Number of records by record type in file, does not include
                                                          Header and Trailer records
       General Use            GEN       20         AN     Field to be utilized by sender/receiver company‟s to provide
                                                          additional information
729
730   The items below do not require a “Label” only the symbol shown
       Field Separator         |         1         AN     A “pipe” is to be utilized for the field separator (ASCII
                                                          HEX-7C)
       End of record NL       NL         1         AN     The NEW LINE character is a single character that
                                                          identifies the end of record In all cases for all records.
                                                          (ASCII HEX-0A)
731

732   6.1.1 Header Record Format Example:
733   HDR|EXDCCYY-MM-
734   DD|CON…………………………..|CYC………|REC………|GEN……….|NL
735
736
737   NOTE: If the field is not being used (I.E: General Use) then the label is not used. It is also not
738         necessary for the labels to be in any particular order, except for the Record Type indicator,
739         which must be first. Fields may be added to the record without changing the file format.
740            Header records will employ cycle counting to ensure a cycle of updates is not missed.
741




      Version 9, January 6, 2010                                                                   Page 44 of 88
                                                                                             NENA Standard Data Formats for
                                                                                         9-1-1 Data Exchange & GIS Mapping
                                                                                                    NENA 02-010, Version 9,
                                                                                                             January 6, 2010



742                                                      EXHIBIT 13
743                       VERSION 3.1 TRAILER FORMAT FOR DATA EXCHANGE
744
            NAME              LABEL         MAX #          TYPE                      DATA DESCRIPTION
                                            BYTES
       Record Type              TLR             0             A       Indicates start of Trailer record (label only, no data
                                                                      follows)
       Record Count             REC             9             N       Number of records by record type in file, does not include
                                                                      Header and Trailer records
745
746   The items below do not require a “Label” only the symbol shown
       Field Separator            |            1           AN      A “pipe” is to be utilized for the field separator (ASCII
                                                                   HEX-7C)
       End of record            NL             1           AN      A NEW LINE character identifies the end of record value
                                                                   in all cases for all records. (ASCII HEX-0A)
747

748   6.1.2 Version 3.1 Trailer Record Format Example:
749   TLR|REC.........|NL
750
751   NOTE: Fields may be added to the record without changing the file format, because a record consists of the data found
752   between one new line and the next, labels need not follow in sequence though checking for duplicate labels within a
753   single record would be prudent.
754   Trailer records will employ record counting to ensure a record within an update file is not missed.

755




      Version 9, January 6, 2010                                                                            Page 45 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010



756                                              EXHIBIT 14
757                            VERSION 3.1 WIRELESS DATA EXCHANGE

758   6.1.3 Dynamic Updates of the ALI Database
759   The Version 1 through 4 Formats for Data Exchange applies to record and file exchanges between
760   Service Providers and Data Base Management System Providers. These exchanges are file oriented
761   and may be exchanged using bulk electronic file transmissions, CD-ROM, diskette, magnetic tape,
762   or similar medium. The need to provide dynamic ALI database updates during 9-1-1 calls was
763   introduced with Wireless Phase I solutions. The traditional record/file format for data exchange
764   does not apply to dynamic database updates, which are real-time transaction, oriented. Header and
765   Trailer records are not utilized in a transaction message, which is designed to be a real-time update
766   of one or more database records.
767   Wireless solutions require information to be provided to the PSAP at the time a 9-1-1 call is in
768   progress from a wireless device. This information is dynamic since it cannot be determined or
769   stored in the ALI database prior to the 9-1-1 calls. Information such as the wireless caller‟s Call
770   Back Number, Latitude, and Longitude information is only known at the time the 9-1-1 call is placed
771   and must be dynamically populated in the ALI database. Wireless Service Providers must generate a
772   real-time transaction to the ALI System that contains this dynamic information. The ALI database is
773   updated with this information prior to the PSAP equipment issuing an ALI request (bid) to the ALI
774   database. When the ALI system receives the request from the PSAP, the dynamically updated
775   database record is retrieved and used to build the ALI data that will be transmitted back to the PSAP,
776   with the Call Back Number, Latitude, Longitude, and other dynamically updated information.
777   This dynamic update capability requires real-time interfaces to be developed between the data
778   provider and the ALI Database Management System. Many of these interfaces are currently in place
779   as Wireless Phase I solutions were deployed. These real-time interfaces may utilize proprietary
780   software and data formats.
781   Wireless Phase II introduced the need to retrieve updated lat/long information during 911 call
782   processing. Data Base Management System Providers should refer to TIA/EIA/IS J-STD-036 and
783   the soon to be published NENA Standard for the Implementation of the Wireless Emergency Service
784   Protocol E2 Interface via TCP/IP. When implementing the E2 interface DBMS System Providers
785   must ensure compatibility between the data elements defined in the E2 interface and the data
786   elements defined in this NENA document. When inconsistencies exist between TIA/EIA/IS J-STD-
787   036 and the NENAE2 Interface Document, the NENA standards must take precedence. Position data
788   retrieved from the MPC may need to be translated to conform to the ALI database and ALI data
789   formats.
790   NENA recognizes that existing interfaces may utilize these proprietary interfaces, protocol, and data
791   formats. The Dynamic Update of the ALI Database shown in the XML format is for illustrative
792   purposes. Each interface provider should review the data elements for dynamic updates for
793   consideration in these proprietary interfaces. Adoption of XML data format for real-time interfaces
      Version 9, January 6, 2010                                                             Page 46 of 88
                                                                                 NENA Standard Data Formats for
                                                                             9-1-1 Data Exchange & GIS Mapping
                                                                                        NENA 02-010, Version 9,
                                                                                                 January 6, 2010


794   may provide the same benefits recognized for record/file exchange. New data elements may need to
795   be added to these real-time interfaces as new technology is introduced. New data elements can be
796   easily added when using XML format.
797   The following are data elements for Dynamic Updates to the ALI Database. These same data
798   elements should be defined in the ALI data format used to transmit the ALI back to the PSAP.
799                                   Dynamic Updates of the ALI Database
           NAME          LABEL        MAX #      TYPE                         DESCRIPTION
                                      BYTES
       Call-Back           CBN           10        AN     Telephone Number that can be dialed to reach a specific
       Number                                             calling party. The call back number must be a dialable
                                                          number and used as a back up if the displayed number
                                                          cannot be reached
       MOBILE ID           MIN           10        AN     Mobile Identification number of the cellular wireless
       (MIN)                                              device.
       Roamer Port         RPT           10        AN     Temporarily assigned "roamer" call back number.
       Channel             RCC           3         AN     Channel signal received on.
       Longitude           LON           11         N     Longitude/X coordinate. Right Justified; pad field with
                                                          zeros to left of decimal degrees. +long: east of Greenwich; -
                                                          long: west of Greenwich. When Phase II location cannot be
                                                          provided, Phase I information should be reported, i.e., the
                                                          cell site or sector where the call is received. (Can be used
                                                          for wireline) Sample: +000.######
800




      Version 9, January 6, 2010                                                                 Page 47 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010



801
802                         VERSION 3.1 FORMAT FOR WIRELESS DATA EXCHANGE
803
804   Dynamic Updates of the ALI Database
           NAME          LABEL       MAX #   TYPE                        DESCRIPTION
                                     BYTES
      Latitude             LAT          10    N     Latitude/Y coordinate. Right Justified; pad field with zeros to
                                                    left of decimal degrees. +lat: north of equator; -lat: south of
                                                    equator. When Phase II location cannot be provided, Phase I
                                                    information should be reported, i.e., the cell site or sector
                                                    where the call is received. (Can be used for wireline) Sample:
                                                    +00.######
      Elevation            ELV          5     N     Elevation/Altitude indicated as height above mean sea level,
                                                    measured in meters (Can be used for wireline) Sample:
                                                    #####
      P-ANI                 PNI         10    AN    Pseudo ANI or locally specific code identifying the receiving
                                                    antenna for the wireless 9-1-1 call for routing purposes.
      Location Valid       LVD          1     N     Valid data indicator (1=OK; 0=Invalid).
      Flag
      Datum                NAD          2     AN    Specifies the map projection and coordinate system for the
                                                    display of the Longitude and Latitude coordinates. Two
                                                    systems are commonly used for North America. The code 83
                                                    identifies North American Datum for 1983 (NAD83). Code
                                                    84 identifies the World Geodetic System for 1984 (WGS84).
                                                    Other codes may be added as additional datum become
                                                    available through authorized entities.
                                                    Where x =
                                                    83 = NAD83
                                                    84 = WGS84
      LDT Confidence       COF          7     N     Information that indicates the level of uncertainty inherent to
                                                    the associated latitude/longitude information expressed in
                                                    meters, ranging from one meter to 1800 Km expressed in
                                                    meters.
      LDT Confidence       COP          3     N     Information identifying the confidence by which it is known
      Percentage                                    that the calling party lies within the associated shape
                                                    description. It is expressed as a percentage ranging from 0 –
                                                    100.
      LDT Provider ID      LDT          8     AN    LDT Provider Identification Code. Codes to be developed
                                                    and held by NENA.
805
806




      Version 9, January 6, 2010                                                              Page 48 of 88
                                                                                         NENA Standard Data Formats for
                                                                                     9-1-1 Data Exchange & GIS Mapping
                                                                                                NENA 02-010, Version 9,
                                                                                                         January 6, 2010


807                          VERSION 3.1 FORMAT FOR WIRELESS DATA EXCHANGE
808
809   Dynamic Updates of the ALI Database
           NAME            LABEL       MAX #       TYPE                            DESCRIPTION
                                       BYTES
      LDT Technology         LTY           2         AN       Defines how particular position information was obtained to
                                                              help assess its credibility. Defined values include:
                                                              Single Character Value of x: Translation Value of yyy:

                                                                  0      = Unknown
                                                                  1      = Network Unspecified
                                                                  2      = Network AOA
                                                                  3      = Network TOA
                                                                  4      = Network TDOA
                                                                  5      = Network RF Fingerprinting
                                                                  6      = Network Cell Sector
                                                                  16     = Handset Unspecified
                                                                  17     = Handset GPS
                                                                  18     = Handset AGPS
                                                                  19     = Handset EOTD
                                                                  20     = Handset AFLT
      Time Stamp             TME           8         AN       Universal Time Coordinate (UTC) indicating milliseconds
                                                              into UTC day.
      Day Stamp              DAY           7          N       Year and Julian date. (UTC Date). Sample: 1996187
                                                              (CCYYDDD).
      Speed (in KPH)         SPD           3          N       Speed of travel in kilometers per hour.
      Heading                HDG           3          N       Direction of travel, decimal degrees from true north. Valid
      (in degrees)                                            entries 0-359.
      Cell Site ID           CEL           6         AN       Identification number indicating a geographic region of
                                                              cellular coverage. When Phase II location cannot be provided,
                                                              Phase I information should be reported, i.e., the cell site or
                                                              sector where the call is received.
      Sector ID              SEC           2         AN       Sub set/section of a cell. . When Phase II location cannot be
                                                              provided, Phase I information should be reported, i.e., the cell
                                                              site or sector where the call is received.
810
811                                         Wireless Data Format Example:
812   CBN..........|MIN..........|RPT...........|RCC...|XCD...........|YCD...........|ZCD......|PNI..........|LVD.|ND
813   A..|COF....|COP..|LDT........|LTY....|TME........|DAY.......|SPD...|HDG...|NL
814
815
816
817
818
819
820
      Version 9, January 6, 2010                                                                         Page 49 of 88
                                                                            NENA Standard Data Formats for
                                                                        9-1-1 Data Exchange & GIS Mapping
                                                                                   NENA 02-010, Version 9,
                                                                                            January 6, 2010


821   NOTE: Version 4 Data Exchange Format is an industry standard XML data format. NENA XML
822   (Extensible Markup Language) documents have been adapted from SGML (Standard Generalized
823   Markup Language) by the World Wide Web Consortium. Version 4 Data Exchange Format was
824   created to bring the NENA Data Exchange Format in line with industry standard implementation
825   methods, to introduce versioning control and promote reusability of previous work. All existing
826   NENA 4 information has been removed from this document and moved to an easily accessible area
827   on the NENA web site. http://www.nena.org/xml_schemas/nena.htm. Go to this url and select
828   NENA XML Schema Repository. Select Schema Archive. Select Version 0.0. All previous
829   XML format exhibits are shown including Element Tags, Data Dictionary, GIS Data Model, and
830   ALI Response V1.0.
831   XML ALI Exchange development should be done in accordance with the 04-005 NENA ALI Query
832   Service Standard. The most current versions of the ALI and AQS schemas should be used.
833
834
835




      Version 9, January 6, 2010                                                         Page 50 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010




836                                              EXHIBIT 15
837   VERSION 4 XML FORMAT FOR DATA EXCHANGE

838   6.1.4 The XML Schema
839   The XML Schema is a document that represents how the XML data must be organized. It defines the
840   data elements that are required and those that are optional. The schema also describes data types
841   (Strings vs. integer data, date elements, etc), the relationship between data elements (single or
842   multiple instance, parent and child elements)

843   6.1.5 Schema Version Control
844    All NENA data exchange formats, prior to NENA 3, by nature, could not be changed without
845   becoming a completely new data exchange format and were not backward compatible.
846   NENA 4 provides a vehicle to support necessary change without disturbing existing systems and
847   processes. NENA 4 can be said to be backward compatible within schema generations.
848   A Schema Generation change is used to make major modifications to the XML Schema, changes
849   that are so different that they will prevent the validation process. Schema from one Generation are
850   not backward compatible and cannot be used to validate data documents. For example, changing the
851   schema rules about how data elements are organized will often be the cause of backward
852   incompatibility since this type of change would modify the definition, structure or existing
853   relationships between data elements or groupings. Again, a new Generation will not be backward
854   compatible with previous generations.
855   A Schema Release change is used to introduce modifications to an XML Schema that maintain
856   backward compatibility with all other schema releases within the current generation.
857   Schema Generations will be kept in “Generation” named folders on the NENA Web site linked to
858   the NENA Home Page, following W3C conventions, and will be available to anyone who requires
859   the schema documents for validation or development. Under each Generation folder will be folder(s)
860   that contain the most current as well as previous schema releases. Each Release folder will contain
861   the actual schema files, all supporting documentation and Application Information Caption Map
862   data.

863   6.1.6 Schema Design
864   In a simple schema design, the data element type definitions may be included within the schema
865   itself. To promote reusability data type definitions have been separated into an ALI Type Library
866   schema document. The ALI Type Library can be used or referenced by other applications or schemas
867   to retrieve the data types defined for 911 ALI. When schema or data definition changes are required
868   the change will be made to a single reference file within a release instead of changing the individual
869   schemas. When the change is made to the ALI Type Library schema the change is then available to
870   all applications that reference it.

      Version 9, January 6, 2010                                                             Page 51 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010



871   6.1.7 Schema Extensions
872   XML Schema Extensions provide a method to include additional data elements that have not yet
873   been specifically defined in the ALI Library. Schema Extensions promote a data flexibility that was
874   not available in previous NENA exchange formats. Once it has been determined that the new data
875   element (s) provided through the extension mechanism are required they will be added to the ALI
876   Type Library or other schema documents, through the NENA Data Committee process. A new
877   schema release will then be created which includes the new data elements

878   6.1.8 Schema Validation
879   Proper Schema validation provides a level of confidence that the data being sent to and received by
880   an application meets the established definition and requirements for the defined XML data. Previous
881   NENA data exchange versions defined the arrangement of data elements in a fixed length record.
882   The XML Schema describes the layout of an XML document. Validation checks the element tag
883   names to ensure they are valid, ensures that required tags and data are present, the order of data
884   elements in the XML document and the data type of each element to ensure they fit the definition
885   and meet the requirements as specified in the Schema. Each XML data document includes
886   information that specifies the Schema Generation and Release used to validate the XML document
887   from which it was issued. This Schema Generation and Release information is included in the XML
888   documents Root Element at the beginning of the XML document.

889   6.1.9 Validation Point
890   The purpose of the XML schema is to provide a means to determine that an XML document is
891   complete and valid as to its format, structure and data element types. The most logical point in the
892   data exchange for validation to occur is at the sending application. Performing validation at the
893   sending end ensures that only valid XML documents are received reducing retransmissions and
894   effort on the receiving end to return the document to the sender. An alternative method is to validate
895   on both ends where there is either a lack of confidence in the sender validation process or where the
896   developer of the software wants to leverage the power of the schema.

897   6.1.10 Redefining of Data Elements
898   With a careful review of the original NENA 4 data elements it becomes apparent that the NENA 3
899   data elements were wrapped in an XML tag and called NENA 4 causing the real benefits available
900   with XML to be missed. For this reason the current NENA 3 and NENA 4 data elements have been
901   reexamined to determine areas where improvements could be made. Details regarding additions,
902   changes or modifications can be found in README files located within the Generation/Release
903   folders on the NENA web site.

904   6.1.11 Two examples of this redefining are described below.
905   General Use
906   The original NENA 4 data exchange document identifies eight (8) text elements labeled General Use
907   1 thru 8, each 60 characters in length. During the review of schema definition these 8 data elements

      Version 9, January 6, 2010                                                             Page 52 of 88
                                                                                  NENA Standard Data Formats for
                                                                              9-1-1 Data Exchange & GIS Mapping
                                                                                         NENA 02-010, Version 9,
                                                                                                  January 6, 2010


908   were removed and replaced with 1 element called General Use. The definition of this element says
909   that there can be 1 or many of this general use element. In this way the XML document can, without
910   changing Generation or Release include 1 General Use data element or 20. This is similar to adding
911   rows or columns to a table in a word processor or adding a column in spreadsheet program. A new
912   column or row can be added by creating an additional instance or occurrence of the data element. In
913   a similar manner Additional General Use fields can be added in the XML document without
914   changing the schema or the definitions.
915   Class and Type of Service
916   The original NENA 4 definitions for Class and Type of Service contain a 2 dimensional data element
917   for each Class and Type of Service The first part being the numeric representation such as 1, 2, 3,
918   etc. The second part is a text definition of the number such as, 1= Residence, 2=Business, etc. The
919   purpose was to make the standard text definition available for display at the PSAP. In the NENA 4
920   XML Schema document these definitions become part of the ALI Type Library schema and are,
921   therefore, available to those applications that require it by using the schema as a cross reference to
922   the definitions. This technique maintains the use of standard definitions, promotes reusability of data
923   across many applications and schemas. This can also reduce the size of the data stream by not
924   passing the definitions along with the data.

925   6.1.12 Transmission Protocol
926   The future direction of data exchange methods adopted by NENA must incorporate method and
927   design concepts that are independent of traditional connection protocols. Among the benefits of
928   XML data is the ability to be protocol independent. For example the current ALI data delivery
929   method utilizes a Start of Text (STX) / End of Text (ETX) protocol wrapped around the ALI data or
930   other message. While this protocol works well in the current environment there are benefits to be
931   gained from newer, faster data delivery methods and protocols such as TCP/IP, HTTP, HTTPS,
932   SOAP or others.
933   This becomes more apparent as the additional data available from Wireless, ACN and other sources
934   we have not yet identified are considered. Since XML is protocol independent it may be used within
935   the existing infrastructure without limiting the possibility of using other protocols to deliver the ALI
936   Data or other data messages.

937   6.1.13 XML Schema Location
938   NENA Version 4 Data Exchange Formats are available on the NENA web site at
939   http://www.nena.org/xml_schemas/nena.htm.
940   The most current Generation and Release XML schemas and supporting documentation are
941   available at this location.
942   Schema documents for all XML data sources will be coordinated and validated by the NENA Data
943   Technical Committee.
944   A Schema Generation identifies XML families of schemas that are backward compatible within that
945   family or generation.
      Version 9, January 6, 2010                                                      Page 53 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010


946   A Schema Release is a grouping of schema documents for each XML data source such as ACN,
947   Service Order, MSAG, etc.
948   There may be many releases within a Schema Generation. The differences between releases are such
949   that they do not cause incompatibility with previous releases within that Generation schema family.
950   Schema changes that cause backward incompatibility constitute a new Generation.
951   Some schema documents may not change between a Generation or Release; however, all files in
952   each release within each generation will have been verified to ensure compatibility with all other
953   schemas within that release. Once this has been accomplished the collection of schemas will be
954   organized into a Release, assigned a number designating the Generation family it belongs to and its
955   order within that Generation family and then place on the NENA web site for use. An example of the
956   Release naming convention would be Release 1.2 for Generation 1, Release 2 designating the second
957   release of XML schemas within Generation 1. The next release within Generation 1 would be
958   Release 1.3 and so on.
959
960




      Version 9, January 6, 2010                                                           Page 54 of 88
                                                                       NENA Standard Data Formats for
                                                                   9-1-1 Data Exchange & GIS Mapping
                                                                              NENA 02-010, Version 9,
                                                                                       January 6, 2010



961     6.1.14 Example of the relationship between schema Generations and subsequent Releases
962




963
964
965
966
967
968
969
970
971
972
973




      Version 9, January 6, 2010                                                    Page 55 of 88
                                                                                   NENA Standard Data Formats for
                                                                               9-1-1 Data Exchange & GIS Mapping
                                                                                          NENA 02-010, Version 9,
                                                                                                   January 6, 2010


 974
 975                                       Schema Version 4.2
 976                                               Change Log
 977
 978   These are the items that have been changed from Version 4.1 to 4.2 in the schemas.
 979   6.1.15 All schemas:
 980       1) Changed all instances of datatypes (and restrictions) xs:string to xs:token7.
 981       2) Set version in all schemas to 4.2.

 982   7   ALI Schemas
 983   7.1.1 ALI.xsd
 984       1) Removed LocationInfo root element.
 985       2) Removed MaxOccurs unbounded from LocationInfo occurring in AliBody.
 986       3) Added Best Practices documentation for CallInfoType.
 987       4) Modified CallInfoType so that all child elements are optional; specific change is that
 988          CallingPartyNum and ClassOfService are now optional.
 989       5) Added the following optional element to the ALI schema CallInfoType definition:
 990          CallInfo/SpecialMessage : SpecialMessageType.
 991       6) Added the following optional element to the ALI schema CallInfoType definition:
 992          CallInfo/AlsoRingsAtAddress : TextualCivicAddressType
 993       7) Removed use attribute in LocationInfoType.
 994       8) Added Best Practices documentation for AgenciesType.
 995       9) Replaced individual Law/Fire/EMS types with Agency Type definition.
 996       10) Added ability to specify multiple OtherAgencies.
 997       11) Modified ESN to be an optional element in Agencies.
 998       12) Modified SourceInfoType to make DataProvider, Access Provider, ALIRetrievalGMT
 999           optional elements.
1000       13) Modified NetworkInfo to make PSAPID and RouterID optional elements.

       7 An xs:token string is a string that does not contain the carriage return (#xD), line feed (#xA) nor tab
       (#x9) characters, that has no leading or trailing spaces (#x20) and that has no internal sequences of
       two or more spaces

       Version 9, January 6, 2010                                                               Page 56 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010


1001      14) Added PSAPName as element for NetworkInfo.

1002   7.1.2 ALITypeLib.xsd
1003       1) Modified AdditionalAgencyInfoType size to be 75 rather than 100 chars.
1004      2) Added AgencyType definition which contains AgencyName and AgencyTN.
1005      3) Removed AlsoRingsAtAddressType.
1006      4) Modified CellID and SectorID to be optional elements for CellSiteType; added Best
1007         Practices documentation.
1008      5) Add length specifier of 1 to ClassOfServiceCodeType.
1009      6) Added length specifier to CountryType
1010      7) Added Name as optional element in DataProviderIDType.
1011      8) Added length specifier of 2 to DatumType.
1012      9) Added Name as optional element in AccessProviderIDType.
1013      10) Removed EMSType, FireType, LawType (superceded by AgencyType).
1014      11) Added length specifier to LDTTechnologyCodeType.
1015      12) Removed LocationValidType.
1016      13) Added PSAPNameType.
1017      14) Removed RoamerPortType.
1018      15) Added length specifier to SourceOfServiceType (this is an optional field in Call Info).
1019      16) Added length specifier to SpecialAttentionIndicator.
1020      17) Added SpecialMessageType.
1021      18) Added Best Practices documentation for StreetAddressType.
1022      19) Made all elements in StreetAddressType optional.
1023      20) Added the following optional element to StreetAddressType definition: TextualAddress :
1024          TextualCivicAddressType. (Even though this may seem redundant with the
1025          LocationDescription element, the latter is defined to hold additional information about a
1026          location (for example “South Wing”) rather than the civic address of the location itself. The
1027          TextualAddress element is there to explicitly support cases where street address is available
1028          only in textual (un-structured) form – like the address of a VoIP caller in i2.)
1029      21) Added TextualCivicAddressType.
1030      22) Added length specifier to TypeOfServiceCodeType.



       Version 9, January 6, 2010                                                            Page 57 of 88
                                                                              NENA Standard Data Formats for
                                                                          9-1-1 Data Exchange & GIS Mapping
                                                                                     NENA 02-010, Version 9,
                                                                                              January 6, 2010



1031   7.1.3 ALI Query Service Directory and Schemas
1032   The “aliqs” directory contains schemas and WSDLs for ALI Query Service. These are all new.

1033   7.1.4 AQS and AQS.WS Removed
1034   Directories containing preliminary work on AQS have been removed.

1035   7.1.5 MSAGRecord.xsd
1036       1) Removed RangeNumberType.
1037       2) Modified LowRange and HIghRange to be HouseNumTypes.
1038       3) Modified Function Of Change to be consistent with decisions made for NENA 2.1 retrofit.
1039          The only FOC types supported are “D” and “I”.
1040       4) Moved TARCode from the street element to the range element.

1041   8   I2 Schemas
1042   8.1.1 Geopriv Directory and Schemas
1043   The geopriv directory contains the CivicAddress and geoshape schemas.

1044   8.1.2 GML-3.1.1 Directory and Schemas
1045   The GML directory contains GML schemas referenced from the v9 schemas.

1046   8.1.3 All I2 Schemas
1047
       Old                                         New
       V2-request                                  v2Request
       v2-response                                 v2Response
       v2-esct                                     v2Esct
       v2-esct-ack                                 v2EsctAck
       callserver-vpc-request                      callserverVpcRequest
       callserver-vpc-esct                         callserverVpcEsct
       esr-request                                 esrRequest
       call-id                                     callId
       call-origin                                 callOrigin
       esr-response                                esrResponse
       esct-ack                                    esctAck
       v3-request                                  v3Request
       v3-response                                 v3Response
       vpc-lis-request                             vpcLisRequest
       ipl-request                                 iplRequest
       message-id                                  messageId
       Version 9, January 6, 2010                                                          Page 58 of 88
                                                                                   NENA Standard Data Formats for
                                                                               9-1-1 Data Exchange & GIS Mapping
                                                                                          NENA 02-010, Version 9,
                                                                                                   January 6, 2010



       ipl-response                                  iplResponse
       pos-source                                    posSource
       v8-request                                    v8Request
       v8-response                                   v8Response
       vpc-erdb-request                              vpcErdbRequest
       erdb-request                                  erdbRequest
       erdb-response                                 erdbResponse
       v9-request                                    v9Request
       v9-response                                   v9Response
       vdb-identity-request                          vdbIdentityRequest
       erdb-identity-request                         erdbIdentityRequest
       identity-request                              identityRequest
       identity-response                             identityResponse
       location-key                                  locationKey
       nena-id                                       nenaID
       organization-name                             organizationName
       cert-uri                                      certUri
       location-key                                  locationKey
1048
1049   Added version attribute to the schema element.

1050   8.1.4 V2.xsd
1051       1) Modified result element to be String with numeric restriction.

1052   8.1.5 V7.xsd
1053       1) Removed pidf import
1054      2) Added return 500, 570, 580 to ReturnCodeType

1055   8.1.6 V8.xsd
1056       1) Removed pidf import
1057      2) Added return 210, 211, 212, 213, 214, 215, 562 to ReturnCodeType
1058      3) Modified geo-location to be consistent with V9.

1059   8.1.7 V9.xsd
1060   This schema has been completely re-written.
1061
1062



       Version 9, January 6, 2010                                                               Page 59 of 88
                                                                                 NENA Standard Data Formats for
                                                                             9-1-1 Data Exchange & GIS Mapping
                                                                                        NENA 02-010, Version 9,
                                                                                                 January 6, 2010



1063                                               EXHIBIT 22

1064                                   GIS DATA MODEL, VERSION 2.0

1065   1.0     Preface
1066   Version 2.0 of the NENA GIS Data Model identifies the minimal attributes required in a spatial
1067   dataset. It also defines the GML schema that can be used with this model. Using the GML schema,
1068   this data model can be used for GIS data exchange between neighboring public safety agencies and
1069   to meet the requirements of GIS data needed for the NENA i2 solution (NENA 08-001), and for the
1070   Location Validation Function and the Emergency Calling Routing Function in the NENA i3 solution
1071   (NENA 08-751).
1072   1.1     Metadata
1073   The Content Standard for Digital Geospatial Metadata (CSDGM), Vers. 2 (FGDC-STD-001-1998) is
1074   the US Federal Metadata standard. The Federal Geographic Data Committee originally adopted the
1075   CSDGM in 1994 and revised it in 1998. According to Executive Order 12096 all Federal agencies
1076   are ordered to use this standard to document geospatial data created as of January, 1995. The
1077   standard is often referred to as the FGDC Metadata Standard and has been implemented beyond the
1078   federal level with State and local governments adopting the metadata standard as well.
1079   The international community, through the International Organization of Standards (ISO), has
1080   developed and approved an international metadata standard, ISO 19115. As a member of ISO, the
1081   US is required to revise the CSDGM in accord with ISO 19115. Each nation can craft their own
1082   profile of ISO 19115 with the requirement that it include the 13 core elements. The FGDC is
1083   currently leading the development of a US Profile of the (ISO) international metadata standard, ISO
1084   19115.
1085   Metadata is information about the content, quality, condition, and other characteristics of data being
1086   sent. The basic elements to be included in the metadata file are taken from the 2003 ISO 19115 –
1087   International Standard for Geographic Information – Metadata.
1088   This International Standard defines an extensive set of metadata elements; typically only a subset of
1089   the full number of elements is used. However, it is essential that a basic minimum number of
1090   metadata elements be maintained for a dataset. Listed are the core metadata elements required to
1091   identify a dataset, typically for catalogue purposes. This list contains metadata elements answering
1092   the following questions: “Does a dataset on a specific topic exist („what‟)?”, “For a specific place
1093   („where‟)?”, “For a specific date or period („when‟)?” and “A point of contact to learn more about or
1094   order the dataset („who‟)?”. Using the recommended optional elements in addition to the mandatory
1095   elements will increase interoperability, allowing users to understand without ambiguity the
1096   geographic data and the related metadata provided by either the producer or the distributor. Dataset
1097   metadata profiles of this International Standard shall include this core.
1098   Listed below are the core metadata elements (mandatory and recommended optional) required for
1099   describing a dataset. An “M” indicates that the element is mandatory. An “O” indicates that the
1100   element is optional. A “C” indicates that the element is mandatory under certain conditions.
       Version 9, January 6, 2010                                                             Page 60 of 88
                                                                                          NENA Standard Data Formats for
                                                                                      9-1-1 Data Exchange & GIS Mapping
                                                                                                 NENA 02-010, Version 9,
                                                                                                          January 6, 2010


1101
       Dataset title (M)                                         Spatial representation type (O)
       (MD_Metadata > MD_DataIdentification.citation >           (MD_Metadata >
       CI_Citation.title)                                        MD_DataIdentification.spatialRepresentationType)
       Dataset reference date (M)                                Reference system (O)
       (MD_Metadata > MD_DataIdentification.citation >           (MD_Metadata > MD_ReferenceSystem)
       CI_Citation.date)
       Reference system (O)
       Dataset responsible party (O)                             Lineage (O)
       (MD_Metadata > MD_DataIdentification.pointOfContact >     (MD_Metadata > DQ_DataQuality.lineage > LI_Lineage)
       CI_ResponsibleParty)
       Geographic location of the dataset (by four               On-line resource (O)
       coordinates or by geographic identifier) (C)              (MD_Metadata > MD_Distribution >
       (MD_Metadata > MD_DataIdentification.extent >             MD_DigitalTransferOption.onLine >
       EX_Extent                                                 CI_OnlineResource)
       > EX_GeographicExtent > EX_GeographicBoundingBox or
       EX_GeographicDescription)
       Dataset language (M)                                      Metadata file identifier (O)
       (MD_Metadata > MD_DataIdentification.language)            (MD_Metadata.fileIdentifier)
       Dataset character set (C)                                 Metadata standard name (O)
       (MD_Metadata > MD_DataIdentification.characterSet)        (MD_Metadata.metadataStandardName)
       Dataset topic category (M)                                Metadata standard version (O)
       (MD_Metadata > MD_DataIdentification.topicCategory)       (MD_Metadata.metadataStandardVersion)
       Spatial resolution of the dataset (O)                     Metadata language (C)
       (MD_Metadata > MD_DataIdentification.spatialResolution    (MD_Metadata.language)
       >
       MD_Resolution.equivalentScale or
       MD_Resolution.distance)
       Abstract describing the dataset (M)                       Metadata character set (C)
       (MD_Metadata > MD_DataIdentification.abstract)            (MD_Metadata.characterSet)
       Distribution format (O)                                   Metadata point of contact (M)
       (MD_Metadata > MD_Distribution > MD_Format.name           (MD_Metadata.contact > CI_ResponsibleParty
       and
       MD_Format.version)
       Additional extent information for the dataset             Metadata date stamp (M)
       (vertical and temporal) (O)                               (MD_Metadata.dateStamp)
       (MD_Metadata > MD_DataIdentification.extent >
       EX_Extent
       > EX_TemporalExtent or EX_VerticalExtent)
1102

1103   1.2     9-1-1 SPATIAL ATTRIBUTES FOR LINE DATA
1104
1105   1.2.1A Centerline Layer (Required)
        ATTRIBUTE        USE       TYPE                             DATA DESCRIPTION
            NAME         R/O
       Low Address        R          N      Lowest address on left side of street in ascending order
       Left

       Version 9, January 6, 2010                                                                      Page 61 of 88
                                                                                NENA Standard Data Formats for
                                                                            9-1-1 Data Exchange & GIS Mapping
                                                                                       NENA 02-010, Version 9,
                                                                                                January 6, 2010


High Address       R         N    Highest address on left side of street in ascending order
Left
Low Address        R         N    Lowest address on right side of street in ascending order
Right
High Address       R         N    Highest address on right side of street in ascending order
Right
Prefix             R         A    Leading street direction prefix. Valid Entries: N S E W
Directional                       NE NW SE SW
Street Name Pre    O         A    The element of the complete street name preceding the street name
Type                              element that indicates the type of street. These are typically Street
                                  Suffixes according to Appendix C in USPS Publication 28. However,
                                  they are not abbreviated when used in this field.
Street Name        R         AN   Valid street name as assigned by local addressing authority
Street Suffix      R          A   Valid Street abbreviation, as defined by the US Postal Service
                                  Publication 28. (e.g. AVE)
Post Directional   R         A    Trailing street direction suffix. Valid Entries: N S E W
                                  NE NW SE SW
Road Class         R         N    http://www.fhwa.dot.gov/planning/fctoc.htm
                                  Highway Performance Monitoring System (HPMS) Functional
                                  Classifications:
                                  1= Interstate
                                  2= Other Freeways and Expressways
                                  3= Other Principal Arterial
                                  4= Minor Arterial
                                  5= Major Collector
                                  6= Minor Collector
                                  7= Local

                                  Not designated as a HPMS Functional Classification, but non the less an
                                  important road classification for 9-1-1:

                                  8= Trails (Recreational trails)

One-way            R         A    One way road classification.


                                  B or Blank – travel in both directions allowed
                                  FT – One-way from FROM node to TO node (in direction of arc)
                                  TF – One way from TO node to FROM Node (opposite direction of arc)
                                  (Discuss with Group)
Postal             R         A    Postal Community Name as identified on the left side of the street
Community
Name Left
Postal             R         A    Postal Community Name as identified on the right side of the street
Community
Name Right
Postal Code/Zip    R         AN   Postal or Zip code as identified on the Left side of the street. Format:
Code Left                         ANANAN or NNNNN 2
Postal Code/Zip    R         AN   Postal or Zip code as identified on the Right side of the street. Format:
Code Right                        ANANAN or NNNNN2

Version 9, January 6, 2010                                                                      Page 62 of 88
                                                                                               NENA Standard Data Formats for
                                                                                           9-1-1 Data Exchange & GIS Mapping
                                                                                                      NENA 02-010, Version 9,
                                                                                                               January 6, 2010


       MSAG                   R          A       Valid service community name as identified by the MSAG on the left
       Community                                 side of the street
       Name Left
       MSAG                   R          A       Valid service community name as identified by the MSAG on the right
       Community                                 side of the street
       Name Right
       ESN Left               O         AN       3-5 digit Emergency Service Number associated with street segment
       ESN Right              O         AN       3-5 digit Emergency Service Number associated with street segment
       Segment ID             R          N       Unique Road Segment ID number
       County Name            R         AN       County Name on the Left side of the street as given in FIPS 6-4 1
       Left

       County Name            R         AN       County Name on the Right side of the street as given in FIPS 6-4 1
       Right

       County Code            R          A       County Code on the Left side of the street as given in FIPS 6-4 1
       Left
       County Code            R          A       County Code on the Right side of the street as given in FIPS 6-4 1
       Right
       State/Province         R          A       Two character Alpha U.S. State or Canadian province abbreviation as
       Left                                      defined by Postal Authority or ISO 3166-2 i.e. TX (Texas), ON
                                                 (Ontario)
       State/Province         R          A       Two character Alpha U.S. State or Canadian province abbreviation as
       Right                                     defined by Postal Authority or ISO 3166-2 i.e. TX (Texas), ON
                                                 (Ontario)
       Source of Data         R          A       Agency that last updated the record
       Date Updated           R          N       Date of last update Format: CCYY-MM-DD
1106
       1
1107      http://www.census.gov/geo/www/fips/fips65/index.html The FIPS Codes Standard shall not apply to applications
1108   involving interchange of international data that require the use of the country codes of the International Organization for
1109   Standardization, i.e., ISO 3166. For the convenience of such users, the ISO 3166 country codes are published in FIPS
1110   PUB 104, Guideline for Implementation of ANSI Codes for the Representation of Names of Countries, Dependencies,
1111   and Areas of Special Sovereignty. FIPS PUB 104 provides both two- and three-character alphabetic codes for each entity
1112   listed. Federal agencies that do not require FIPS PUB 104 for international data interchange, and are not involved in
1113   national defense programs or with the mission of the U.S. Department of State, may adopt either set of codes.

       2
1114    The USPS considers zip codes to be delivery routes instead of areas. There may be differences between this depiction
1115   and actual zip code mailing address.

1116




       Version 9, January 6, 2010                                                                              Page 63 of 88
                                                                                             NENA Standard Data Formats for
                                                                                         9-1-1 Data Exchange & GIS Mapping
                                                                                                    NENA 02-010, Version 9,
                                                                                                             January 6, 2010


1117
1118   1.2.1B. Railroad Layer (Optional)
        ATTRIBUTE         USE      TYPE                                 DATA DESCRIPTION
            NAME          R/O
        Line               R          A        Railroad Line Owner (Code of Association of American Railroads)
        Line Sub-          R          A        Railroad Line Sub-Division Name
        Division Name
        Line Type            R         A       Main, Secondary or Siding
        Line Status          R         A       Active or Inactive
        Segment ID           R         N       Unique Railroad Segment ID
        Mile Post Low        R        AN       Beginning Linear Reference
        Mile Post High       R        AN       Ending Linear Reference
        Passenger Rail       R         A       Passenger Rail Indicator
        Indicator
        Source of Data       R        A        Agency that last updated the record
        Date Updated         R        N        Date of last update Format: CCYY-MM-DD
1119

1120   1.2.1C.Hydrology Layer (Optional)
        ATTRIBUTE        USE     TYPE                              DATA DESCRIPTION
           NAME          R/O
        Surface Water     R       A        Type of Surface Water (river, stream, etc.)
        Line
        Surface Water    R        A        Name of river, stream etc.
        Name
        Segment ID       R        N        Unique Hydrology Segment ID
        Source of Data   R        A        Agency that last updated the record
        Date Updated     R        N        Date of last update Format: CCYY-MM-DD
1121
1122




       Version 9, January 6, 2010                                                                         Page 64 of 88
                                                                                        NENA Standard Data Formats for
                                                                                    9-1-1 Data Exchange & GIS Mapping
                                                                                               NENA 02-010, Version 9,
                                                                                                        January 6, 2010




1123   1.3.    9-1-1 SPATIAL ATTRIBUTES FOR POINT DATA

1124   1.3. A Emergency Service Agency Location Layer (Required)
        ATTRIBUTE       USE   TYPE                 DATA DESCRIPTION
          NAME          R/O
        Agency Type      R      A    Law = L
                                     Fire = F
                                     Emergency Medical Service = E
        County Name     R      AN    County Name as given in FIPS 6-4 1


        County Code     R       A    FIPS County Code as given in FIPS 6-4 1
        Community       R       N    Unique Community ID Number i.e. FIPS,
        ID                           GEOCODES, etc.
        Agency ID       R       N    Emergency Service Agency ID defined with the
                                     first 5 digits as the County ID code and the last 4
                                     digits as the locally assigned agency code
        Agency Name     R       A    Name of Agency
        Agency          R       A    Agency Contact Person
        Contact
        House           R      AN    House Number Prefix to accommodate
        Number                       Alphanumeric characters or fire numbers in house
        Prefix                       number i.e. Wisconsin
        House           R       N    House Number
        Number
        House           R      AN    House Number Suffix
        Number
        Suffix
        Prefix          R      AN    Leading street direction prefix. Valid Entries: N S
        Directional                  EW
                                     NE NW SE SW
        Street Name     O       A    The element of the complete street name preceding
        Pre Type                     the street name element that indicates the type of
                                     street. These are typically Street Suffixes according
                                     to Appendix C in USPS Publication 28. However,
                                     they are not abbreviated when used in this field.
        Street Name     R      AN    Valid street name as assigned by local addressing
                                     authority
        Street Suffix   R      AN    Valid Street abbreviation, as defined by the US
                                     Postal Service Publication 28. (e.g. AVE)
        Post            R      AN    Trailing street direction suffix. Valid Entries: N S E
        Directional                  W
                                     NE NW SE SW
        Postal          R       A    Postal Community Name
        Community
        Name
        MSAG            R       A    Valid service community name as identified by the
        Community                    MSAG

       Version 9, January 6, 2010                                                                    Page 65 of 88
                                                                                           NENA Standard Data Formats for
                                                                                       9-1-1 Data Exchange & GIS Mapping
                                                                                                  NENA 02-010, Version 9,
                                                                                                           January 6, 2010


        Name
        Postal             O     AN    Postal or Zip code. Format: NNNNN or ANANAN2
        Code/Zip
        Code
        State/Province     R      A    Two character Alpha U.S. State or Canadian
                                       province abbreviation as defined by Postal
                                       Authority or ISO 3166-2 i.e. TX (Texas), ON
                                       (Ontario)
        Telephone          O     AN    Telephone Number of Agency Format: NPA-NXX-
        Number                         XXXX
        Source of          R      A    Agency that last updated the record
        Data
        Date Updated       R      N    Date of last update Format: CCYY-MM-DD
1125

1126   1.3 B. Cell Site Location Layer (Required)
        ATTRIBUTE         USE   TYPE                            DATA DESCRIPTION
          NAME            R/O
        NENA CO ID         R    AN     . NENA Company ID www.NENA.org

        Numeric Cell      R      N     Carrier Cell site ID
        ID
        Cell Site         R      A     Location Name assigned by the wireless carrier
        Common
        Name
        Cell Site         R     AN     Cell Site Identifier provided by the wireless service provider, it is unique
        Unique ID                      to the cell site
        Cell Site         R      A     The address of the cell tower as provided by the wireless service
        Address                        provider. Needs to be MSAG Valid
        Postal            R      A     Postal Community Name
        Community
        Name
        MSAG              R      A     Valid service community name as identified by the MSAG
        Community
        Name
        Cell Site State   R      A     State where the cell tower is located
        County Code       R     AN     FIPS County Code as given in FIPS 6-4 1

        Air Interface     R      A     A=Analog (900MHz), P=Digital (PCS), T=TDMA (Digital AMPs),
        Technology                     G=GSM – Type of RF Voice Technology
        Source of Data    R      A     Agency that last updated the record
        Date Updated      R      N     Date of last update Format: CCYY-MM-DD

1127
1128



       Version 9, January 6, 2010                                                                          Page 66 of 88
                                                                                         NENA Standard Data Formats for
                                                                                     9-1-1 Data Exchange & GIS Mapping
                                                                                                NENA 02-010, Version 9,
                                                                                                         January 6, 2010



1129   1.3 C. Mile Marker Location Layer (Optional)
        ATTRIBUTE        USE     TYPE                    DATA DESCRIPTION
           NAME          R/O
        Mile Post ID      R          N    Mile Post Identification Number
        Mile Marker       R          A    Type of mile marker :
        Type                              Railroad name
                                          Road name
                                          Trail
                                          Water Way
                                          Coastal
                                          Boardwalk
        Route System         R       AN   Name of route system (ex: Interstate 85)
        Name
        Segment ID           R       N    Unique Road or Railroad Segment ID number
        Source of Data       R       A    Agency that last updated the record
        Date Updated         R       N    Date of last update Format: CCYY-MM-DD
1130
1131   1.3 D. Railroad Grade Crossing Layer (Optional)
       ATTRIBUTE         USE     TYPE                    DATA DESCRIPTION
           NAME          R/O
       Grade Crossing    R       N        Unique USDOT ID for the Crossing
       ID

       Crossing          R       N        Position of Crossing
       Position                           At Grade
                                          RR Under
                                          RR Over

       Grade Crossing    O       A        Name given to Grade Crossing
       Name

       Source of Data    R       A        Agency that last updated the record

       Date Updated      R       N        Date of last update Format: CCYY-MM-DD


1132   1.3 E. Site/Structure Location Layer (Optional)
        ATTRIBUTE        USE     TYPE                    DATA DESCRIPTION
          NAME           R/O
        Community ID      R          N    Unique Community ID Number i.e. FIPS,
                                          GEOCODES, etc.
        Site ID              R        N   Unique Site ID Number
        House Number         R       AN   House Number Prefix to accommodate Alphanumeric
        Prefix                            characters or fire numbers in house number i.e.
                                          Wisconsin
        House Number         R        N   House Number
        House Number         R       AN   House Number Suffix
       Version 9, January 6, 2010                                                                     Page 67 of 88
                                                                                         NENA Standard Data Formats for
                                                                                     9-1-1 Data Exchange & GIS Mapping
                                                                                                NENA 02-010, Version 9,
                                                                                                         January 6, 2010


        Suffix
        Location         O     AN        Additional location information.
                                         Abbreviated as shown in USPS Publication 28,
                                         Appendix C, Item C2.
        Prefix           R     AN        Leading street direction prefix. Valid Entries: N S E
        Directional                      W
                                         NE NW SE SW
        Street Name      O      A        The element of the complete street name preceding the
        Pre Type                         street name element that indicates the type of street.
                                         These are typically Street Suffixes according to
                                         Appendix C in USPS Publication 28. However, they
                                         are not abbreviated when used in this field.
        Street Name      R     AN        Valid street name as assigned by local addressing
                                         authority
        Street Suffix    R     AN        Valid Street abbreviation, as defined by the US Postal
                                         Service Publication 28. (e.g. AVE)
        Post             R     AN        Trailing street direction suffix. Valid Entries: N S E W
        Directional                      NE NW SE SW
        ESN              R      N        Emergency Service Number associated with this House
                                         Number, Street Name and Community Name
        Postal           R      A        Postal Community Name
        Community
        Name
        MSAG             R      A        Valid service community name as identified by the
        Community                        MSAG
        Name
        Postal           O     AN        Postal or Zip code. Format: NNNNN or ANANAN2
        Code/Zip
        Code
        Landmark         R     AN        Landmark or Vanity address
        Site Type        R      A        Type of Structure – Classification Field
        L/R              R      A        Left/Right side of the road
        Source of Data   R      A        Agency that last updated the record
        Date Updated     R      N        Date of last update Format: CCYYMMDD
1133

1134   1.4.    9-1-1 SPATIAL ATTRIBUTES FOR POLYGON DATA

1135   1.4 A. County Boundary Layer (Required)
        ATTRIBUTE        USE    TYPE                      DATA DESCRIPTION
           NAME          R/O
        County Name       R         AN     County Name as given in FIPS 6-4 1


        County Code      R          N      FIPS County Code as given in FIPS 6-4 1


        Source of Data   R          A      Agency that last updated the record
        Date Updated     R          N      Date of last update Format: CCYY-MM-DD
       Version 9, January 6, 2010                                                                     Page 68 of 88
                                                                                             NENA Standard Data Formats for
                                                                                         9-1-1 Data Exchange & GIS Mapping
                                                                                                    NENA 02-010, Version 9,
                                                                                                             January 6, 2010



1136   1.4 B. Emergency Service Zone Boundary Layer (Required)
        ATTRIBUTE        USE     TYPE                              DATA DESCRIPTION
           NAME          R/O
        Community ID      R       N        Unique Community ID Number i.e. FIPS, GEOCODES, etc.
        County Name       R      AN        County Name as given in FIPS 6-4 1


        County Code      R        N        FIPS County Code as given in FIPS 6-4 1


        PSAP ID          R       AN        Code identifying the PSAP as listed in the FCC PSAP registry
                                           http://www.fcc.gov/pshs/services/911-
                                           services/enhanced911/psapregistry.html
                                           http://www.fcc.gov/pshs/services/911-
                                           services/enhanced911/psapregistry.html
        Agency ID        R        N        Emergency Service Agency ID
        ESN              R        N        Emergency Service Number associated with the ESZ
        Source of Data   R        A        Agency that last updated the record
        Date Updated     R        N        Date of last update Format: CCYY-MM-DD

1137   1.4 C. Municipal Boundary Layer (Required)
        ATTRIBUTE        USE     TYPE                            DATA DESCRIPTION
           NAME          R/O
        Community ID      R       N        Unique Community ID Number i.e. FIPS, GEOCODES, etc.
        MSAG              R       A        Valid service community name as identified by the MSAG
        Community
        Name
        Source of Data   R        A        Agency that last updated the record
        Date Updated     R        N        Date of last update Format: CCYY-MM-DD

1138   1.4 D. Emergency Service Agency Boundary Layer (Required)
        ATTRIBUTE         USE      TYPE                              DATA DESCRIPTION
           NAME           R/O
        PSAP ID            R          AN       Code identifying the PSAP as listed in the FCC PSAP registry
                                               http://www.fcc.gov/pshs/services/911-
                                               services/enhanced911/psapregistry.html
        County Name          R        AN       County Name as given in FIPS 6-4 1


        County Code          R        N        FIPS County Code as given in FIPS 6-4 1


        Agency ID            R        N        Emergency Service Agency ID
        Source of Data       R        A        Agency that last updated the record

        Date Updated         R        N        Date of last update Format: CCYY-MM-DD



       Version 9, January 6, 2010                                                                         Page 69 of 88
                                                                                       NENA Standard Data Formats for
                                                                                   9-1-1 Data Exchange & GIS Mapping
                                                                                              NENA 02-010, Version 9,
                                                                                                       January 6, 2010



1139   1.4 E. Cell Site Coverage Layer (Required)
        ATTRIBUTE        USE   TYPE                           DATA DESCRIPTION
            NAME         R/O
        LDT Provider      R    AN     LDT Provider Identification Code. Codes to be developed and held by
        ID                            NENA
        Numeric Cell     R      N     Carrier Cell site ID
        ID
        Cell Site        R     AN     Cell Site Identifier provided by the wireless service provider, it is
        Unique ID                     unique to the cell site
        Numeric          R      N     Carrier Sector ID usually indicates Omni or multi-sectored antenna
        Sector ID                     faces
        ESRD/ESRK        R      N     ESRD is a 10 digit # used for routing a wireless call & is assigned by
                                      cell sector. ESRK is a 10-digit # for routing & is assigned as a pool of
                                      numbers to a PSAP. The first # of range is entered here
        Sector           R      N     Orientation of the cell sector antenna face, with North being 0 degrees
        Orientation/Az                and South = 180 degrees.
        imuth
        Sector           R      A     Cell Sector Antenna orientation compass direction
        Compass
        Orientation
        Sector Beam      R      N     Width of the sector antenna beam in degrees, under normal operating
        Width                         conditions
        Average          R      N     Average true sector radius range (under average operating conditions.)
        Sector Radius                 Radius at which cell tower‟s polygon of influence ends and another
                                      begins.
        Coverage         R      A     C=Company Map, D=Digital data from Company, P=GIS Propagation
        source                        Study, L=Line of Site analysis, R=Range Def
        Source of Data   R      A     Agency that last updated the record
        Date updated     R      A     Date of last update Format: CCYY-MM-DD
1140




       Version 9, January 6, 2010                                                                      Page 70 of 88
                                                                                      NENA Standard Data Formats for
                                                                                  9-1-1 Data Exchange & GIS Mapping
                                                                                             NENA 02-010, Version 9,
                                                                                                      January 6, 2010




1141   1.4 F.    Hydrology Layer (Optional)
        ATTRIBUTE        USE   TYPE                          DATA DESCRIPTION
           NAME          R/O
        Surface Water     R     A     Type of Surface Water (pond, lake, large waterway, reservoir, etc.)
        Line
        Surface Water    R      A     Name of Pond, lake, waterway, reservoir, etc.
        Name
        Segment ID       R      N     Unique Hydrology Segment ID
        Source of Data   R      A     Agency that last updated the record
        Date Updated     R      N     Date of last update Format: CCYY-MM-DD
1142
1143   2.0      GML Schema
1144
1145   <?xml version="1.0" encoding="UTF-8"?>
1146   <!-- edited with XMLSpy v2006 U (http://www.altova.com) by Patricia Bluhm (HBF
1147   Group) -->
1148   <xs:schema xmlns:tns="urn:nena:gis" xmlns:xs="http://www.w3.org/2001/XMLSchema"
1149   xmlns:gml="http://www.opengis.net/gml"
1150   xmlns:gmlsf="http://www.opengis.net/gmlsf" xmlns:alins="http://www.nena9-1-
1151   1.org/schemas/2003/ali" targetNamespace="urn:nena:gis"
1152   elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
1153         <xs:annotation>
1154               <xs:appinfo
1155   source="http://schemas.opengis.net/gml/3.1.1/profiles/gmlsfProfile/1.0.0/gmlsfLe
1156   vels.xsd">
1157                     <gmlsf:ComplianceLevel>2</gmlsf:ComplianceLevel>
1158
1159         <gmlsf:GMLProfileSchema>http://schemas.opengis.net/gml/3.1.1/profiles/gmls
1160   fProfile/1.0.0/gmlsf.xsd</gmlsf:GMLProfileSchema>
1161               </xs:appinfo>
1162         </xs:annotation>
1163         <!-- ============================================================= -->
1164         <!-- includes and imports -->
1165         <!-- ============================================================= -->
1166         <xs:import namespace="http://www.opengis.net/gml"
1167   schemaLocation="http://schemas.opengis.net/gml/3.1.1/profiles/gmlsfProfile/1.0.0
1168   /gmlsf2.xsd"/>
1169         <xs:import namespace="http://www.opengis.net/gmlsf"
1170   schemaLocation="http://schemas.opengis.net/gml/3.1.1/profiles/gmlsfProfile/1.0.0
1171   /gmlsfLevels.xsd"/>
1172         <xs:import namespace="http://www.nena9-1-1.org/schemas/2003/ali"
1173   schemaLocation="../ALI/ALI/ALITypeLib.xsd"/>
1174         <!-- ================================================================ -->
1175         <xs:element name="NenaFeatures" type="tns:NenaFeaturesType"
1176   substitutionGroup="gml:_GML"/>
1177         <!-- ============================================================= -->
1178         <!-- Define a feature collection for a set of nena items           -->
1179         <!-- ============================================================= -->
1180         <xs:complexType name="NenaFeaturesType">
       Version 9, January 6, 2010                                                                     Page 71 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1181               <xs:complexContent>
1182                     <xs:extension base="gml:AbstractFeatureType">
1183                           <xs:sequence maxOccurs="unbounded">
1184                                  <xs:element name="nenaFeatureMembers"
1185   minOccurs="0">
1186                                        <xs:complexType>
1187                                              <xs:sequence>
1188                                                    <xs:element ref="gml:_Feature"
1189   maxOccurs="unbounded"/>
1190                                              </xs:sequence>
1191                                        </xs:complexType>
1192                                  </xs:element>
1193                           </xs:sequence>
1194                     </xs:extension>
1195               </xs:complexContent>
1196         </xs:complexType>
1197         <!-- ================================================================ -->
1198         <!-- Line Data Types -->
1199         <!-- ================================================================ -->
1200         <xs:complexType name="HydrologyType">
1201               <xs:complexContent>
1202                     <xs:extension base="gml:AbstractFeatureType">
1203                           <xs:sequence>
1204                                  <xs:element name="surfaceWaterType"
1205   type="xs:token" minOccurs="0">
1206                                        <xs:annotation>
1207                                              <xs:documentation>Type of Surface
1208   Water (river, stream, etc.); name should be specified in
1209   gml:name</xs:documentation>
1210                                        </xs:annotation>
1211                                  </xs:element>
1212                                  <xs:element ref="tns:dataSource" minOccurs="0"/>
1213                                  <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1214                                  <xs:element name="hydrologySegmentList"
1215   type="tns:HydrologySegmentType"/>
1216                           </xs:sequence>
1217                     </xs:extension>
1218               </xs:complexContent>
1219         </xs:complexType>
1220         <xs:complexType name="HydrologySegmentType">
1221               <xs:sequence>
1222                     <xs:element name="segmentID" type="tns:SegmentIDType"/>
1223                     <xs:element name="centerline" type="tns:lineType"/>
1224               </xs:sequence>
1225         </xs:complexType>
1226         <xs:element name="HydrologyCenterline" type="tns:HydrologyType"
1227   substitutionGroup="gml:_Feature">
1228               <xs:annotation>
1229                     <xs:documentation>Hydrology Centerline</xs:documentation>
1230               </xs:annotation>
1231         </xs:element>
1232         <!-- ================================================================ -->
       Version 9, January 6, 2010                                              Page 72 of 88
                                                                   NENA Standard Data Formats for
                                                               9-1-1 Data Exchange & GIS Mapping
                                                                          NENA 02-010, Version 9,
                                                                                   January 6, 2010


1233         <xs:complexType name="RailroadType">
1234               <xs:complexContent>
1235                     <xs:extension base="gml:AbstractFeatureType">
1236                           <xs:sequence>
1237                                 <xs:element name="lineOwner" type="xs:token"
1238   minOccurs="0">
1239                                       <xs:annotation>
1240                                              <xs:documentation>Railroad Line Owner
1241   (Code of Association of American Railroads); line subdivision name should be
1242   specified in gml:name</xs:documentation>
1243                                       </xs:annotation>
1244                                 </xs:element>
1245                                 <xs:element name="lineType"
1246   type="tns:RailroadLineType" minOccurs="0"/>
1247                                 <xs:element name="lineStatus"
1248   type="tns:RailroadLineStatusType" minOccurs="0"/>
1249                                 <xs:element name="passengerRailIndicator"
1250   minOccurs="0">
1251                                       <xs:simpleType>
1252                                              <xs:restriction base="xs:string">
1253                                                    <xs:enumeration value="T"/>
1254                                                    <xs:enumeration value="F"/>
1255                                              </xs:restriction>
1256                                       </xs:simpleType>
1257                                 </xs:element>
1258                                 <xs:element ref="tns:dataSource" minOccurs="0"/>
1259                                 <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1260                                 <xs:element name="railSegmentList"
1261   type="tns:RailSegmentType"/>
1262                           </xs:sequence>
1263                     </xs:extension>
1264               </xs:complexContent>
1265         </xs:complexType>
1266         <xs:complexType name="RailSegmentType">
1267               <xs:sequence>
1268                     <xs:element name="segmentID" type="tns:SegmentIDType"/>
1269                     <xs:element name="lowMilePost" type="xs:token"/>
1270                     <xs:element name="highMilePost" type="xs:token"/>
1271                     <xs:element name="centerline" type="tns:lineType"/>
1272               </xs:sequence>
1273         </xs:complexType>
1274         <xs:element name="Railroad" type="tns:RailroadType"
1275   substitutionGroup="gml:_Feature">
1276               <xs:annotation>
1277                     <xs:documentation>Railroad Centerline</xs:documentation>
1278               </xs:annotation>
1279         </xs:element>
1280         <!-- ================================================================ -->
1281         <xs:complexType name="StreetType">
1282               <xs:complexContent>
1283                     <xs:extension base="gml:AbstractFeatureType">
1284                           <xs:sequence>
       Version 9, January 6, 2010                                               Page 73 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1285                                 <xs:element name="prefixDirectional"
1286   type="alins:PrefixDirectionalType" minOccurs="0"/>
1287                                 <xs:element name="streetNamePreType"
1288   type="xs:token" minOccurs="0"/>
1289                                 <xs:element name="streetName"
1290   type="alins:StreetNameType" minOccurs="0"/>
1291                                 <xs:element name="streetSuffix"
1292   type="alins:StreetSuffixType" minOccurs="0"/>
1293                                 <xs:element name="postDirectional"
1294   type="alins:PostDirectionalType" minOccurs="0"/>
1295                                 <xs:element name="roadClass"
1296   type="tns:RoadClassType" minOccurs="0"/>
1297                                 <xs:element name="oneWay" type="tns:OneWayType"
1298   minOccurs="0"/>
1299                                 <xs:element ref="tns:dataSource" minOccurs="0"/>
1300                                 <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1301                                 <xs:element name="SegmentList"
1302   type="tns:SegmentType" maxOccurs="unbounded"/>
1303                           </xs:sequence>
1304                     </xs:extension>
1305               </xs:complexContent>
1306         </xs:complexType>
1307         <xs:complexType name="SegmentType">
1308               <xs:sequence>
1309                     <xs:element name="segmentID" type="tns:SegmentIDType"/>
1310                     <xs:element name="lowAddressLeft" type="tns:StreetNumType"
1311   minOccurs="0"/>
1312                     <xs:element name="lowAddressRight" type="tns:StreetNumType"
1313   minOccurs="0"/>
1314                     <xs:element name="highAddressLeft" type="tns:StreetNumType"
1315   minOccurs="0"/>
1316                     <xs:element name="highAddressRight" type="tns:StreetNumType"
1317   minOccurs="0"/>
1318                     <xs:element name="msagCommunityLeft"
1319   type="alins:MSAGCommunityNameType" minOccurs="0"/>
1320                     <xs:element name="msagCommunityRight"
1321   type="alins:MSAGCommunityNameType" minOccurs="0"/>
1322                     <xs:element name="postalCommunityLeft"
1323   type="alins:PostalCommunityNameType" minOccurs="0"/>
1324                     <xs:element name="postalCommunityRight"
1325   type="alins:PostalCommunityNameType" minOccurs="0"/>
1326                     <xs:element name="postalCodeLeft" type="alins:ZipType"
1327   minOccurs="0"/>
1328                     <xs:element name="postalCodeRight" type="alins:ZipType"
1329   minOccurs="0"/>
1330                     <xs:element name="esnLeft" type="alins:ESNType"
1331   minOccurs="0"/>
1332                     <xs:element name="esnRight" type="alins:ESNType"
1333   minOccurs="0"/>
1334                     <xs:element name="countyNameLeft" type="xs:token"
1335   minOccurs="0"/>

       Version 9, January 6, 2010                                              Page 74 of 88
                                                                     NENA Standard Data Formats for
                                                                 9-1-1 Data Exchange & GIS Mapping
                                                                            NENA 02-010, Version 9,
                                                                                     January 6, 2010


1336                        <xs:element name="countyNameRight" type="xs:token"
1337   minOccurs="0"/>
1338                        <xs:element name="countyIdLeft" type="alins:CountyIDType"
1339   minOccurs="0"/>
1340                        <xs:element name="countyIdRight" type="alins:CountyIDType"
1341   minOccurs="0"/>
1342                     <!--
1343                     <xs:element name="stateProvinceLeft"
1344   type="alins:StateProvinceType" minOccurs="0"/>
1345                     <xs:element name="stateProvinceRight"
1346   type="alins:StateProvinceType" minOccurs="0"/>
1347                     <xs:element name="countryLeft" type="xs:token" minOccurs="0"/>
1348                     <xs:element name="countryRight" type="xs:token"
1349   minOccurs="0"/>
1350   -->
1351                     <xs:element name="centerline" type="tns:lineType"/>
1352               </xs:sequence>
1353         </xs:complexType>
1354         <xs:element name="Street" type="tns:StreetType"
1355   substitutionGroup="gml:_Feature">
1356               <xs:annotation>
1357                     <xs:documentation>Street Centerline</xs:documentation>
1358               </xs:annotation>
1359         </xs:element>
1360         <!-- ================================================================ -->
1361         <!-- Point Data Types -->
1362         <!-- ================================================================ -->
1363         <xs:complexType name="AgencyType">
1364               <xs:annotation>
1365                     <xs:documentation>Emergency Service Agency definition;
1366   difference from Patty's 1st draft is derivation from
1367   gml:AbstractFeatureType</xs:documentation>
1368               </xs:annotation>
1369               <xs:complexContent>
1370                     <xs:extension base="gml:AbstractFeatureType">
1371                           <xs:sequence>
1372                                 <xs:element name="type" type="tns:AgencyTypeType"
1373   minOccurs="0">
1374                                       <xs:annotation>
1375                                              <xs:documentation>Agency Type (law,
1376   fire, ems); agency name should be specified in gml:name</xs:documentation>
1377                                       </xs:annotation>
1378                                 </xs:element>
1379                                 <xs:element name="communityId" type="xs:token"
1380   minOccurs="0"/>
1381                                 <xs:element name="agencyId"
1382   type="tns:AgencyIDType" minOccurs="0"/>
1383                                 <xs:element name="agencyContact" type="xs:token"
1384   minOccurs="0"/>
1385                                 <xs:element name="address"
1386   type="tns:StreetAddressType" minOccurs="0"/>

       Version 9, January 6, 2010                                                 Page 75 of 88
                                                                   NENA Standard Data Formats for
                                                               9-1-1 Data Exchange & GIS Mapping
                                                                          NENA 02-010, Version 9,
                                                                                   January 6, 2010


1387                                 <xs:element name="tn" type="alins:TNType"
1388   minOccurs="0"/>
1389                                  <xs:element ref="tns:dataSource" minOccurs="0"/>
1390                                  <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1391                                  <xs:element ref="gml:Point"/>
1392                           </xs:sequence>
1393                     </xs:extension>
1394               </xs:complexContent>
1395         </xs:complexType>
1396         <xs:element name="EmergencyServiceAgencyLoc" type="tns:AgencyType"
1397   substitutionGroup="gml:_Feature">
1398               <xs:annotation>
1399                     <xs:documentation>Emergency Service Agency
1400   Location</xs:documentation>
1401               </xs:annotation>
1402         </xs:element>
1403         <!-- ================================================================ -->
1404         <xs:complexType name="CellType">
1405               <xs:complexContent>
1406                     <xs:extension base="gml:AbstractFeatureType">
1407                           <xs:sequence>
1408                                  <xs:element name="nenaCompanyID"
1409   type="alins:AccessProviderIDType" minOccurs="0">
1410                                        <xs:annotation>
1411                                              <xs:documentation>NENA company id for
1412   the Location Determination Technology Provider</xs:documentation>
1413                                        </xs:annotation>
1414                                  </xs:element>
1415                                  <xs:element name="cellSiteNumericID"
1416   type="xs:token" minOccurs="0">
1417                                        <xs:annotation>
1418                                              <xs:documentation>Cell Site numeric
1419   id; cell site name should be specified in gml:name</xs:documentation>
1420                                        </xs:annotation>
1421                                  </xs:element>
1422                                  <xs:element name="cellSiteUniqueID"
1423   type="xs:token" minOccurs="0">
1424                                        <xs:annotation>
1425                                              <xs:documentation>Cell Site ID
1426   provided by the wireless service provider; it is unique to the cell
1427   site</xs:documentation>
1428                                        </xs:annotation>
1429                                  </xs:element>
1430                                  <xs:element name="cellSiteAddress"
1431   type="tns:StreetAddressType" minOccurs="0"/>
1432                                  <xs:element name="airInterfaceTechnology"
1433   type="tns:CellTypeType" minOccurs="0"/>
1434                                  <xs:element ref="tns:dataSource" minOccurs="0"/>
1435                                  <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1436                                  <xs:element ref="gml:Point"/>
1437                           </xs:sequence>
1438                     </xs:extension>
       Version 9, January 6, 2010                                               Page 76 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1439               </xs:complexContent>
1440         </xs:complexType>
1441         <xs:element name="Cell" type="tns:CellType"
1442   substitutionGroup="gml:_Feature">
1443               <xs:annotation>
1444                     <xs:documentation>Cell Site Location</xs:documentation>
1445               </xs:annotation>
1446         </xs:element>
1447         <!-- ================================================================ -->
1448         <xs:complexType name="MileMarkerType">
1449               <xs:complexContent>
1450                     <xs:extension base="gml:AbstractFeatureType">
1451                           <xs:sequence>
1452                                 <xs:element name="milePostId" type="xs:int"
1453   minOccurs="0"/>
1454                                 <xs:element name="mileMarkerType"
1455   type="tns:MMType" minOccurs="0"/>
1456                                 <xs:element name="routeSystemName" type="xs:token"
1457   minOccurs="0">
1458                                       <xs:annotation>
1459                                             <xs:documentation>Name of route system
1460   (example: Interstate 85)</xs:documentation>
1461                                       </xs:annotation>
1462                                 </xs:element>
1463                                 <xs:element ref="tns:segmentID" minOccurs="0"/>
1464                                 <xs:element ref="tns:dataSource" minOccurs="0"/>
1465                                 <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1466                                 <xs:element ref="gml:Point"/>
1467                           </xs:sequence>
1468                     </xs:extension>
1469               </xs:complexContent>
1470         </xs:complexType>
1471         <xs:element name="MileMarker" type="tns:MileMarkerType"
1472   substitutionGroup="gml:_Feature">
1473               <xs:annotation>
1474                     <xs:documentation>Mile Marker Location</xs:documentation>
1475               </xs:annotation>
1476         </xs:element>
1477         <!-- ================================================================ -->
1478         <xs:complexType name="RailroadGradeCrossingType">
1479               <xs:complexContent>
1480                     <xs:extension base="gml:AbstractFeatureType">
1481                           <xs:sequence>
1482                                 <xs:element name="gradeCrossingId" type="xs:token"
1483   minOccurs="0">
1484                                       <xs:annotation>
1485                                             <xs:documentation>Grade Crossing ID
1486   assigned to USDOT; crossing Name should be specified in
1487   gml:name</xs:documentation>
1488                                       </xs:annotation>
1489                                 </xs:element>
1490                                 <xs:element name="crossingPosition" minOccurs="0">
       Version 9, January 6, 2010                                              Page 77 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1491                                       <xs:simpleType>
1492                                             <xs:restriction base="xs:token">
1493                                                   <xs:enumeration value="At
1494   Grade"/>
1495                                                   <xs:enumeration value="RR
1496   Under"/>
1497                                                   <xs:enumeration value="RR
1498   Over"/>
1499                                             </xs:restriction>
1500                                       </xs:simpleType>
1501                                 </xs:element>
1502                                 <xs:element ref="tns:dataSource" minOccurs="0"/>
1503                                 <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1504                                 <xs:element ref="gml:Point"/>
1505                           </xs:sequence>
1506                     </xs:extension>
1507               </xs:complexContent>
1508         </xs:complexType>
1509         <xs:element name="RailroadGradeCrossing"
1510   type="tns:RailroadGradeCrossingType" substitutionGroup="gml:_Feature">
1511               <xs:annotation>
1512                     <xs:documentation>RailroadGradeCrossing
1513   Location</xs:documentation>
1514               </xs:annotation>
1515         </xs:element>
1516         <!-- ================================================================ -->
1517         <xs:complexType name="SiteType">
1518               <xs:complexContent>
1519                     <xs:extension base="gml:AbstractFeatureType">
1520                           <xs:sequence>
1521                                 <xs:element name="communityId" type="xs:token"
1522   minOccurs="0"/>
1523                                 <xs:element name="siteId" type="xs:token"
1524   minOccurs="0"/>
1525                                 <xs:element name="address"
1526   type="tns:StreetAddressType" minOccurs="0"/>
1527                                 <xs:element name="esn" type="alins:ESNType"
1528   minOccurs="0"/>
1529                                 <xs:element name="landmark"
1530   type="alins:LandmarkAddressType" minOccurs="0"/>
1531                                 <xs:element name="location"
1532   type="alins:LocationDescriptionType" minOccurs="0"/>
1533                                 <xs:element name="type" type="xs:token"
1534   minOccurs="0">
1535                                       <xs:annotation>
1536                                             <xs:documentation>Type of Structure
1537   – Classification Field</xs:documentation>
1538                                       </xs:annotation>
1539                                 </xs:element>
1540                                 <xs:element name="leftRight"
1541   type="tns:LeftRightType" minOccurs="0">
1542                                       <xs:annotation>
       Version 9, January 6, 2010                                              Page 78 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1543                                             <xs:documentation>Left/Right side of
1544   the road</xs:documentation>
1545                                       </xs:annotation>
1546                                 </xs:element>
1547                                 <xs:element ref="tns:dataSource" minOccurs="0"/>
1548                                 <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1549                                 <xs:element ref="gml:Point"/>
1550                           </xs:sequence>
1551                     </xs:extension>
1552               </xs:complexContent>
1553         </xs:complexType>
1554         <xs:element name="Structure" type="tns:SiteType"
1555   substitutionGroup="gml:_Feature">
1556               <xs:annotation>
1557                     <xs:documentation>Structure Location</xs:documentation>
1558               </xs:annotation>
1559         </xs:element>
1560         <!-- ================================================================ -->
1561         <!-- Polygon Data Types -->
1562         <!-- ================================================================ -->
1563         <xs:complexType name="CountyType">
1564               <xs:complexContent>
1565                     <xs:extension base="gml:AbstractFeatureType">
1566                           <xs:sequence>
1567                                 <xs:element name="countyId"
1568   type="alins:CountyIDType" minOccurs="0">
1569                                       <xs:annotation>
1570                                             <xs:documentation>FIPS county code;
1571   county name should be specified in gml:name</xs:documentation>
1572                                       </xs:annotation>
1573                                 </xs:element>
1574                                 <xs:element ref="tns:dataSource" minOccurs="0"/>
1575                                 <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1576                                 <xs:element ref="gml:Polygon"/>
1577                           </xs:sequence>
1578                     </xs:extension>
1579               </xs:complexContent>
1580         </xs:complexType>
1581         <xs:element name="County" type="tns:CountyType"
1582   substitutionGroup="gml:_Feature">
1583               <xs:annotation>
1584                     <xs:documentation>County Boundaries</xs:documentation>
1585               </xs:annotation>
1586         </xs:element>
1587         <!-- ================================================================ -->
1588         <xs:complexType name="ESZType">
1589               <xs:complexContent>
1590                     <xs:extension base="gml:AbstractFeatureType">
1591                           <xs:sequence>
1592                                 <xs:element name="communityId" type="xs:token"
1593   minOccurs="0"/>

       Version 9, January 6, 2010                                              Page 79 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1594                                 <xs:element name="countyName" type="xs:token"
1595   minOccurs="0"/>
1596                                 <xs:element name="countyId"
1597   type="alins:CountyIDType" minOccurs="0"/>
1598                                 <xs:element name="psapId" type="alins:PSAPIDType"
1599   minOccurs="0">
1600                                       <xs:annotation>
1601                                             <xs:documentation>Code identifying the
1602   PSAP as listed in the FCC PSAP registry http://www.fcc.gov/pshs/services/911-
1603   services/enhanced911/psapregistry.html
1604   http://www.fcc.gov/pshs/services/911-services/enhanced911/psapregistry.html
1605   </xs:documentation>
1606                                       </xs:annotation>
1607                                 </xs:element>
1608                                 <xs:element name="agencyID" type="xs:token"
1609   minOccurs="0"/>
1610                                 <xs:element name="esn" type="alins:ESNType"
1611   minOccurs="0"/>
1612                                 <xs:element ref="tns:dataSource" minOccurs="0"/>
1613                                 <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1614                                 <xs:element ref="gml:Polygon"/>
1615                           </xs:sequence>
1616                     </xs:extension>
1617               </xs:complexContent>
1618         </xs:complexType>
1619         <xs:element name="ESZ" type="tns:ESZType"
1620   substitutionGroup="gml:_Feature">
1621               <xs:annotation>
1622                     <xs:documentation>Emergency Service Zone
1623   Boundaries</xs:documentation>
1624               </xs:annotation>
1625         </xs:element>
1626         <!-- ================================================================ -->
1627         <xs:complexType name="MunicipleBoundariesType">
1628               <xs:complexContent>
1629                     <xs:extension base="gml:AbstractFeatureType">
1630                           <xs:sequence>
1631                                 <xs:element name="communityId" type="xs:token"
1632   minOccurs="0"/>
1633                                 <xs:element name="msagCommunityName"
1634   type="alins:MSAGCommunityNameType" minOccurs="0"/>
1635                                 <xs:element ref="tns:dataSource" minOccurs="0"/>
1636                                 <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1637                                 <xs:element ref="gml:Polygon"/>
1638                           </xs:sequence>
1639                     </xs:extension>
1640               </xs:complexContent>
1641         </xs:complexType>
1642         <xs:element name="Municiple" type="tns:MunicipleBoundariesType"
1643   substitutionGroup="gml:_Feature">
1644               <xs:annotation>
1645                     <xs:documentation>Municipality Boundaries</xs:documentation>
       Version 9, January 6, 2010                                              Page 80 of 88
                                                                   NENA Standard Data Formats for
                                                               9-1-1 Data Exchange & GIS Mapping
                                                                          NENA 02-010, Version 9,
                                                                                   January 6, 2010


1646               </xs:annotation>
1647         </xs:element>
1648         <!-- ================================================================ -->
1649         <xs:complexType name="EmergencyServiceAgencyBoundaryType">
1650               <xs:complexContent>
1651                     <xs:extension base="gml:AbstractFeatureType">
1652                           <xs:sequence>
1653                                  <xs:element name="psapId" type="alins:PSAPIDType"
1654   minOccurs="0"/>
1655                                  <xs:element name="countyName" type="xs:token"
1656   minOccurs="0"/>
1657                                  <xs:element name="countyId"
1658   type="alins:CountyIDType" minOccurs="0"/>
1659                                  <xs:element name="agencyId" type="xs:token"
1660   minOccurs="0"/>
1661                                  <xs:element ref="tns:dataSource" minOccurs="0"/>
1662                                  <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1663                                  <xs:element ref="gml:Polygon"/>
1664                           </xs:sequence>
1665                     </xs:extension>
1666               </xs:complexContent>
1667         </xs:complexType>
1668         <xs:element name="EmergencyServiceAgency"
1669   type="tns:EmergencyServiceAgencyBoundaryType" substitutionGroup="gml:_Feature">
1670               <xs:annotation>
1671                     <xs:documentation>Emergency Service Agency
1672   Boundaries</xs:documentation>
1673               </xs:annotation>
1674         </xs:element>
1675         <!-- ================================================================ -->
1676         <xs:complexType name="CellCoverageType">
1677               <xs:complexContent>
1678                     <xs:extension base="gml:AbstractFeatureType">
1679                           <xs:sequence>
1680                                  <xs:element name="ldtProviderID"
1681   type="alins:AccessProviderIDType" minOccurs="0"/>
1682                                  <xs:element name="cellSiteNumericID"
1683   type="xs:token" minOccurs="0">
1684                                        <xs:annotation>
1685                                              <xs:documentation>Cell Site numeric
1686   id; cell site name should be specified in gml:name</xs:documentation>
1687                                        </xs:annotation>
1688                                  </xs:element>
1689                                  <xs:element name="cellSiteUniqueID"
1690   type="xs:token" minOccurs="0"/>
1691                                  <xs:element name="cellSiteSectorId"
1692   type="alins:SectorIDType" minOccurs="0"/>
1693                                  <xs:element name="cellSiteNumericSectorId"
1694   type="xs:int" minOccurs="0"/>
1695                                  <xs:element name="esrd" type="alins:TNType"
1696   minOccurs="0"/>

       Version 9, January 6, 2010                                               Page 81 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1697                                  <xs:element name="sectorOrientationAzimuth"
1698   type="tns:SectorOrientationAzimuthType" minOccurs="0"/>
1699                                  <xs:element name="sectorCompassOrientation"
1700   type="xs:token" minOccurs="0"/>
1701                                  <xs:element name="sectorBeamWidth" type="xs:int"
1702   minOccurs="0"/>
1703                                  <xs:element name="sectorAverageRadius"
1704   type="xs:int" minOccurs="0"/>
1705                                  <xs:element name="coverageSource"
1706   type="tns:CoverageSourceType" minOccurs="0"/>
1707                                  <xs:element ref="tns:dataSource" minOccurs="0"/>
1708                                  <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1709                                  <xs:element ref="gml:Polygon"/>
1710                           </xs:sequence>
1711                     </xs:extension>
1712               </xs:complexContent>
1713         </xs:complexType>
1714         <xs:element name="CellCoverage" type="tns:CellCoverageType"
1715   substitutionGroup="gml:_Feature">
1716               <xs:annotation>
1717                     <xs:documentation>Cell Site Coverage
1718   Boundaries</xs:documentation>
1719               </xs:annotation>
1720         </xs:element>
1721         <!-- ================================================================ -->
1722         <xs:complexType name="HydrologyBoundaryType">
1723               <xs:complexContent>
1724                     <xs:extension base="gml:AbstractFeatureType">
1725                           <xs:sequence>
1726                                  <xs:element name="surfaceWaterLine"
1727   type="xs:token" minOccurs="0">
1728                                        <xs:annotation>
1729                                              <xs:documentation>Type of Surface
1730   Water (pond, lake, large waterway, reservoir, etc); name of the surface water
1731   should be specified in gml:name</xs:documentation>
1732                                        </xs:annotation>
1733                                  </xs:element>
1734                                  <xs:element ref="tns:segmentID" minOccurs="0"/>
1735                                  <xs:element ref="tns:dataSource" minOccurs="0"/>
1736                                  <xs:element ref="tns:lastUpdate" minOccurs="0"/>
1737                                  <xs:element ref="gml:Polygon"/>
1738                           </xs:sequence>
1739                     </xs:extension>
1740               </xs:complexContent>
1741         </xs:complexType>
1742         <xs:element name="HydrologyBoundary" type="tns:HydrologyBoundaryType"
1743   substitutionGroup="gml:_Feature">
1744               <xs:annotation>
1745                     <xs:documentation>Hydrology Boundaries</xs:documentation>
1746               </xs:annotation>
1747         </xs:element>
1748         <!-- ================================================================ -->
       Version 9, January 6, 2010                                              Page 82 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1749         <!-- General elements -->
1750         <!-- ================================================================ -->
1751         <xs:element name="lastUpdate" type="xs:date"/>
1752         <xs:element name="dataSource" type="xs:token"/>
1753         <xs:element name="segmentID" type="tns:SegmentIDType"/>
1754         <!-- ================================================================ -->
1755         <!-- Simple types -->
1756         <!-- ================================================================ -->
1757         <xs:simpleType name="AgencyIDType">
1758               <xs:annotation>
1759                     <xs:documentation>Emergency Service Agency ID defined with the
1760   first 5 digits of the County ID code and the last 4 digits as the locally
1761   assigned agency code</xs:documentation>
1762               </xs:annotation>
1763               <xs:restriction base="xs:token">
1764                     <xs:pattern value="[0-9]{9}"/>
1765               </xs:restriction>
1766         </xs:simpleType>
1767         <xs:simpleType name="AgencyTypeType">
1768               <xs:annotation>
1769                     <xs:documentation>Law, Fire, EMS</xs:documentation>
1770               </xs:annotation>
1771               <xs:restriction base="xs:token">
1772                     <xs:enumeration value="Law"/>
1773                     <xs:enumeration value="Fire"/>
1774                     <xs:enumeration value="EMS"/>
1775               </xs:restriction>
1776         </xs:simpleType>
1777         <xs:simpleType name="CellTypeType">
1778               <xs:annotation>
1779                     <xs:documentation>Analog (900MHz), Digital (PCS), TDMA
1780   (Digital AMPs), GSM - Type of RFVoice Technology</xs:documentation>
1781               </xs:annotation>
1782               <xs:restriction base="xs:token">
1783                     <xs:enumeration value="Analog"/>
1784                     <xs:enumeration value="GSM"/>
1785                     <xs:enumeration value="PCS"/>
1786                     <xs:enumeration value="TDMA"/>
1787               </xs:restriction>
1788         </xs:simpleType>
1789         <xs:simpleType name="CoverageSourceType">
1790               <xs:annotation>
1791                     <xs:documentation>Company Map; Digital data from Company; GIS
1792   Propagation study; Line of Site Analysis; Range Def</xs:documentation>
1793               </xs:annotation>
1794               <xs:restriction base="xs:token">
1795                     <xs:enumeration value="Company Map"/>
1796                     <xs:enumeration value="Digital Data"/>
1797                     <xs:enumeration value="GIS Propogation study"/>
1798                     <xs:enumeration value="Line of Site Analysis"/>
1799                     <xs:enumeration value="Range Def"/>
1800               </xs:restriction>
       Version 9, January 6, 2010                                              Page 83 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1801         </xs:simpleType>
1802         <xs:simpleType name="LeftRightType">
1803               <xs:restriction base="xs:token">
1804                     <xs:enumeration value="Left"/>
1805                     <xs:enumeration value="Right"/>
1806               </xs:restriction>
1807         </xs:simpleType>
1808         <xs:complexType name="lineType">
1809               <xs:annotation>
1810                     <xs:documentation>Single gml line string</xs:documentation>
1811               </xs:annotation>
1812               <xs:sequence>
1813                     <xs:element ref="gml:LineString"/>
1814               </xs:sequence>
1815         </xs:complexType>
1816         <xs:simpleType name="MMType">
1817               <xs:annotation>
1818                     <xs:documentation>Mile Marker type -- Railroad name; Road
1819   Name</xs:documentation>
1820               </xs:annotation>
1821               <xs:restriction base="xs:token">
1822                     <xs:enumeration value="Railroad"/>
1823                     <xs:enumeration value="Road"/>
1824                     <xs:enumeration value="Trail"/>
1825                     <xs:enumeration value="WaterWay"/>
1826                     <xs:enumeration value="Coastal"/>
1827                     <xs:enumeration value="Boardwalk"/>
1828               </xs:restriction>
1829         </xs:simpleType>
1830         <xs:simpleType name="OneWayType">
1831               <xs:annotation>
1832                     <xs:documentation>One way road classification.
1833   B or NULL – travel in both directions allowed
1834   FT – One-way from FROM node to TO node (in direction of arc)
1835   TF – One way from TO node to FROM Node (opposite direction of arc)
1836   </xs:documentation>
1837               </xs:annotation>
1838               <xs:restriction base="xs:token">
1839                     <xs:enumeration value="B"/>
1840                     <xs:enumeration value="FT"/>
1841                     <xs:enumeration value="TF"/>
1842               </xs:restriction>
1843         </xs:simpleType>
1844         <xs:simpleType name="RailroadLineType">
1845               <xs:restriction base="xs:token">
1846                     <xs:enumeration value="Main"/>
1847                     <xs:enumeration value="Secondary"/>
1848                     <xs:enumeration value="Siding"/>
1849               </xs:restriction>
1850         </xs:simpleType>
1851         <xs:simpleType name="RailroadLineStatusType">
1852               <xs:restriction base="xs:token">
       Version 9, January 6, 2010                                              Page 84 of 88
                                                                   NENA Standard Data Formats for
                                                               9-1-1 Data Exchange & GIS Mapping
                                                                          NENA 02-010, Version 9,
                                                                                   January 6, 2010


1853                      <xs:enumeration value="Active"/>
1854                      <xs:enumeration value="Inactive"/>
1855               </xs:restriction>
1856         </xs:simpleType>
1857         <xs:simpleType name="RoadClassType">
1858               <xs:annotation>
1859                      <xs:documentation>
1860   see http://www.fhwa.dot.gov/planning/fctoc.htm
1861   Highway Performance Monitoring System (HPMS) Functional Classifications:
1862   1= Interstate
1863   2= Other Freeways and Expressways
1864   3= Other Principal Arterial
1865   4= Minor Arterial
1866   5= Major Collector
1867   6= Minor Collector
1868   7= Local
1869   Not designated as a HPMS Functional Classification, but non the less an
1870   important road classification for 9-1-1:
1871   8= Trails (Recreational trails)
1872   </xs:documentation>
1873               </xs:annotation>
1874               <xs:restriction base="xs:token">
1875                      <xs:enumeration value="1"/>
1876                      <xs:enumeration value="2"/>
1877                      <xs:enumeration value="3"/>
1878                      <xs:enumeration value="4"/>
1879                      <xs:enumeration value="5"/>
1880                      <xs:enumeration value="6"/>
1881                      <xs:enumeration value="7"/>
1882                      <xs:enumeration value="8"/>
1883               </xs:restriction>
1884         </xs:simpleType>
1885         <xs:simpleType name="SectorOrientationAzimuthType">
1886               <xs:annotation>
1887                      <xs:documentation>Orientation of the cell sector antenna face
1888   with North being 0 degrees and South being 180 degrees</xs:documentation>
1889               </xs:annotation>
1890               <xs:restriction base="xs:integer">
1891                      <xs:totalDigits value="3"/>
1892                      <xs:minInclusive value="0"/>
1893                      <xs:maxInclusive value="360"/>
1894               </xs:restriction>
1895         </xs:simpleType>
1896         <xs:simpleType name="SegmentIDType">
1897               <xs:annotation>
1898                      <xs:documentation>Segment ID</xs:documentation>
1899               </xs:annotation>
1900               <xs:restriction base="xs:integer">
1901                      <xs:totalDigits value="8"/>
1902               </xs:restriction>
1903         </xs:simpleType>
1904         <xs:complexType name="StreetAddressType">
       Version 9, January 6, 2010                                               Page 85 of 88
                                                                  NENA Standard Data Formats for
                                                              9-1-1 Data Exchange & GIS Mapping
                                                                         NENA 02-010, Version 9,
                                                                                  January 6, 2010


1905               <xs:annotation>
1906                     <xs:documentation>Civic Address in NENA format using NENA
1907   field definitions. (replace with URISA) </xs:documentation>
1908               </xs:annotation>
1909               <xs:all>
1910                     <xs:element name="HouseNumPrefix" type="xs:token"
1911   minOccurs="0"/>
1912                     <xs:element name="HouseNum" type="tns:StreetNumType"
1913   minOccurs="0"/>
1914                     <xs:element name="HouseNumSuffix"
1915   type="alins:HouseNumSuffixType" minOccurs="0"/>
1916                     <xs:element name="PrefixDirectional"
1917   type="alins:PrefixDirectionalType" minOccurs="0"/>
1918                     <xs:element name="StreetNamePreType" type="xs:token"
1919   minOccurs="0"/>
1920                     <xs:element name="StreetName" type="alins:StreetNameType"
1921   minOccurs="0"/>
1922                     <xs:element name="StreetSuffix" type="alins:StreetSuffixType"
1923   minOccurs="0"/>
1924                     <xs:element name="PostDirectional"
1925   type="alins:PostDirectionalType" minOccurs="0"/>
1926                     <xs:element name="MSAGCommunity"
1927   type="alins:MSAGCommunityNameType" minOccurs="0"/>
1928                     <xs:element name="PostalCommunity"
1929   type="alins:PostalCommunityNameType" minOccurs="0"/>
1930                     <xs:element name="CountyName" type="xs:token" minOccurs="0"/>
1931                     <xs:element name="CountyID" type="alins:CountyIDType"
1932   minOccurs="0"/>
1933                     <xs:element name="StateProvince"
1934   type="alins:StateProvinceType" minOccurs="0"/>
1935                     <xs:element name="PostalCode" type="alins:ZipType"
1936   minOccurs="0"/>
1937                     <xs:element name="Country" type="xs:token" minOccurs="0"/>
1938               </xs:all>
1939         </xs:complexType>
1940         <xs:simpleType name="StreetNumType">
1941               <xs:annotation>
1942                     <xs:documentation>Street Number/Address
1943   Number</xs:documentation>
1944               </xs:annotation>
1945               <xs:restriction base="xs:integer">
1946                     <xs:totalDigits value="10"/>
1947               </xs:restriction>
1948         </xs:simpleType>
1949         <xs:simpleType name="UnitsType">
1950               <xs:annotation>
1951                     <xs:documentation>Feet; Meters</xs:documentation>
1952               </xs:annotation>
1953               <xs:restriction base="xs:token">
1954                     <xs:enumeration value="Feet"/>
1955                     <xs:enumeration value="Meters"/>
1956               </xs:restriction>
       Version 9, January 6, 2010                                              Page 86 of 88
                                                                               NENA Standard Data Formats for
                                                                           9-1-1 Data Exchange & GIS Mapping
                                                                                      NENA 02-010, Version 9,
                                                                                               January 6, 2010


1957         </xs:simpleType>
1958   </xs:schema>
1959
1960
1961   3.0      References
1962
1963          U.S. Department of Transportation - Federal Railroad Administration– Secretary‟s Action
1964            Plan for Highway-Rail Crossing Safety and Trespass Prevention Secretary of Transportation
1965          NENA 02-010, NENA Formats and Protocols for Data Exchange
1966          NENA 02-011, NENA Data Standards For Local Exchange Carriers, ALI Service Providers
1967            & 9-1-1 Jurisdictions
1968          NENA 02-014 NENA GIS Data Collection and Maintenance Standards
1969          NENA 57-001 Wireless Phase I & II Features and Functions Operational Information
1970            Document
1971




       Version 9, January 6, 2010                                                           Page 87 of 88
                                                                     NENA Standard Data Formats for
                                                                 9-1-1 Data Exchange & GIS Mapping
                                                                            NENA 02-010, Version 9,
                                                                                     January 6, 2010


1972

1973   99    Previous Acknowledgments
1974
       Data Exchange Formats Sub-Committee Members of as 11/01/2005
       Barry, Tim                               AT&T
       Bluhm, Patty – Chair                     HBF Group
       Bostrom, Carol                           AT&T
       Connel, David                            Denco Area 9-1-1 District
       Desjardins, Pierre                       Positron
       Hutchins, Gary                           Intrado
       Jacques, Maria                           State of Maine
       Lafferty, Sam                            AT&T
       Leigh, Kim                               Qwest
       Louden, Tom                              Verizon
       Marczak, Bill                            BellSouth
       Muehleisen, Scott                        OM2 Technology
       Muehleisen, Tom                          NuVox Communications
       Pyles, Ira                               Hillsborough County 9-1-1
       Sherry, Bob                              Intrado
       Vislocky, Mike                           Network Orange
1975
1976
1977
1978




       Version 9, January 6, 2010                                                 Page 88 of 88

				
DOCUMENT INFO
Categories:
Tags:
Stats:
views:97
posted:3/28/2011
language:English
pages:88
shenreng9qgrg132 shenreng9qgrg132 http://
About