NENA Information Document for Synchronizing Geographic Information System databases with MSAG ALI NENA 71501 Version 11 September 8 2009 Prepared by National Emergency Number AssociGeneration ID: 825428
Download Pdf The PPT/PDF document "NENA Information Document for Synchroniz..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
NENA Information Document for Synchroniz
NENA Information Document for Synchronizing Geographic Information System Databases with MSAG & ALI NENA Information Document for Synchronizing Geographic Information System databases with MSAG & ALI, NENA 71-501, Version 1.1, September 8, 2009 Prepared by: National Emergency Number AssociGeneration Integration Committees, Next Generation Data Development Working Group NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 Page 2 of 37NENA INFORMATION DOCUMENT This NENA Information Document is published by the National Emergency Number Association (NENA) as an information source for the volinterested parties and is provided as an example onl a complete directive. ason including, but not limited to, conformity with state or local regulations may restrict or require modif
ication of the recommendations contained
ication of the recommendations contained in this document. Therefore, this document should not be the only source of information used. NENA members are advicompatibility with local requirements. By using this document, the user agrees that NENA will have no liability for any consequential, incidental, special, or punitive damages arising from use of the document. NENAs Joint Data Technical/PSAP Operations & Next Generation Integration Committees have developed this document. Recommendations for changes to this document may be submitted via email to CommLeadership@nena.orgor via mail to: National Emergency Number Association Arlington, VA 22203-1695 NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 OF CONTENTS EXECUTIVE OVERVIEW.....................................
........................................
.........................................................................................5INTRODUCTION..............................................................................................................................................52.1URPOSE AND COPE OF OCUMENT....................................................................................................................52.2EASON TO MPLEMENT.........52.3OCUMENT ERMINOLOGY...62.4EASON FOR EISSUE............62.5ECOMMENDATION FOR TANDARDS EVELOPMENT ...............................................................................62.6ACTORS......................62.7EFINITIONS..........................................................................................................6SYNCHRONIZATION OF GIS, MSAG, AND ALI DATA...........................................
...............................73.1REPAR
...............................73.1REPARATION..............83.1.1MSAG Standardization Control..............................................................................................83.1.2GIS Data Standardization Control.......................................................................................133.2YNCHRONIZATION ROCESS VERVIEW...........................................................................................................183.2.1Synchronization of GIS Street to the MSAG...................................................................223.2.2ALI database to GIS Street Centerline Data............................................................................................313.2.3Site / Structure Location and ALI records Comparison....................................................................
.......3.2.4Discrepancy Con.............
.......3.2.4Discrepancy Con...........................................................................................................................35CONCLUSIONS..............................................................................................................................................36REFERENCES.................................................................................................................................................36NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 The terms "shall", "must" and "required" are usedparameters and to differentiate from those parameters that are recommendations. Recommendations NENA reserves the right to modify this document.the table below. Version Approval Date Reason For Changes Original 05/2
6/2009 Initial Document 1.1 08/19/2009
6/2009 Initial Document 1.1 08/19/2009 Document number changed to 71-501 Recommendation for Standards Development Work time. Some of the cost factors to be considered, when undertaking the synchronization process, may include: Overtime Stress Management Classes Data availability Accuracy and completeness of existing data Acronyms/Abbreviations/Definitions Some acronyms/abbreviations used in this document have not yet been included in the master of this document, they will be included. See NENA 00-001 - NENA Master Glossary of 9-1-1 Terminology located on the NENA web site for a complete listing of terms used in NENA documents. The following Acronyms/Abbreviations are used in this document: Acronym ** N)ew (U)pdateAutomatic Location Identification NENA Information Document foInformation System databases with MSA
G & ALIVersion 1.1, September 8, 2009
G & ALIVersion 1.1, September 8, 2009 Page 7 of 37The following Acronyms/Abbreviations are used in this document: Automatic Number Identification Synchronization of GIS, MSAG, and ALI data Conflicting information between the MSAG, ALI and GIS databases becomes more prevalent without a constant effort to keep the systems synchronized. However, GIS data of any size will contain errors, and eliminating themexpectation. The goal of this document is to develop a process that will consistently identify errors or discrepancies in the data and quickly correct those which are found. The longer GIS data goes without an update, the less accurate the information will become and the integrity of the data diminishes. The 9-1-1 Authority will always be from: Local GIS department(s) (i.e. government, law enforcement, fire departme
nt, utilities) Local City or County GIS
nt, utilities) Local City or County GIS departments GIS data provided from third parties The amount of time to correct the data and eliminate errors cannot be estimated until an analysis of the discrepancies is performed. Maintaining data integrity within the GIS, MSAGMSAG, ALI, and GIS datapersonnel, GIS personnel, Database Management Systems (DBMS), Postal Authority, Incumbent Local Exchange Carriers (ILECs) and Competitive Local Exchange Carriers (CLECs). This process requires specific procedures and a clear process to keep the information synchronized. It is important that the users of map data retain confidence in the datas accuracy. All GIS, MSAG, and ALI data must be ation and the updates made available to telecommunicators in a timely manner. ocess involves many important steps that this document. Traditionall
y these two databases have been maintain
y these two databases have been maintained separately; therefore undersondition and maintenance important first step towards synchronization. From this understanding, an agency specific workflow can be implemented to consolidate . Once the MSAG and GIS databases are standardized, they need to be compared for accuracy and completeness. The synchronization of the GIS and the MSAG data could ultimately lead to a consolidated workflow and data maintenance process which would eliminate the need to maintain separate GIS and MSAG Data Preparation NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 Discrepancies between the GIS, the MSAG, and the ALI data can cause call problems. Inaccuracies in the databases could lead to a delayed or improper response. By comparing GIS data to
the MSAG, identifying the problems, crea
the MSAG, identifying the problems, creating discrepancy reports, and working to correct the discrepancies, these problems can be minimized. echnical standard where uniform methods and criteria are used. This should be one of the first steps when comparing GIS and MSAG N, S, E, W, NE, NW, SE, or SW are the only Remove special characters (dash, underscorecharacters that could cause problems inUse only whole numbers in the house number fiHouse Number Suffix field). Use complete spelling of the legal street name assigned by the addressing authority (e.g. Spell out the complete MSAG and Postal Community name. iated when not part of the actual street name (North Dr en they are not the actual street name. (Lone Pine Dr South Loop West Dr would notLoop W Dr). http://www.usps.com/ncsc/lookups/abbreviations.htmlThe Canadian Address
ing Guide may be downloaded from the Can
ing Guide may be downloaded from the Canada Post / Postes Canada English: /address_management/can/addressing_guide- French: iness/offerings/address_management/can/addressing_guide-. Example of Street Suffix Standardization NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 An example of using the Zip Code Lookup service to obtain the USPS street name Pressing Submit returns the following: The street naming conventions sGIS street centerline, the MSAG and S road naming conventions must be consistent. d take place in both the MSAG anumber of changes to the databases may be quite high, all involved parties must agree to the number of changes that can be processed in a timely manner and reviewing the contractual obligations of the on the following
steps are recommended: Request the MSAG
steps are recommended: Request the MSAG from your Data Base Management System provider. Load the MSAG into a worksheet or database format, with each field being in a separate column. Save the MSAG file (e.g. Initial MSAG). Save another copy of the MSAG under a different name (e.g. Copy of MSAG). Open the copy of the MSAG (e.g. Copy of MSAG). NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 It is strongly recommended that the information in the Copy of MSAG be sent to the addressing entities for their review. The entities may have streets not shown on the MSAG or may have either renamed or extended a street and failed to forward proper notification or documentation. Any changes that need to be made will have to be sent to the proper agencies to be corrected. Make note o
f any MSAG errors, but do not change any
f any MSAG errors, but do not change anything in this MSAG copy (Copy of MSAG). Make a copy of the Copy of MSAG and name it MSAG Changes. Open the MSAG Changes and add columns for New Prefix Direction, New Street Name, New Street Suffix, and New Street Suffix Direction, or other fields needing correction, similar to the example below. These fields will store the information that needs to be changed in the MSAG. Review each MSAG record for Prefix Directional, Street Name, Street Type, Post-Directional, and Community Name standardization. Review to make sure the proper information is in the correct field. Again, in the First Pass we are only changing street names and ESNs. A very similar process will be used when we compare the MSAG and GIS data for MSAG Community, Postal Community, and Low and High address ranges later
. Note: Corrections to the MSAG data in
. Note: Corrections to the MSAG data in your DBMS may differ from this process. Example of Changes to MSAG table (not all fields are shown) PDSTREET_NAMEST_SUFSDLOWHIGHCOMMUNITYESNN_PDN_STREET_NAMEN_ST_SUFN_SDN_ESNPPLEFORD11001199TAYLORPPLEFORDDRBARONRIDGEDR10001099TAYLORBARON RIDGEWAYCHADBURY800899TAYLORCHADBURYRDCORAL WAYDR13001322TAYLORCORAL WAYDRCORAL WAYCT15001511TAYLORCRAGMOREDR10001199TAYLORCRAIGMORECROWNWOODDR41004299TAYLORNCROWNWOODLNDARTMOUTHDR100199SEABROOKDELANEY900999TAYLORDELAINEYLN corrected and standardized information back to the respective agency for updating. The MSAG Changes document will be used to track and send changes to the screpancies for this process. Submission of changes must be completed using agreed upon formats or interfaces. GIS Data Standardization and Quality Control Most of the inf
ormation in this section for GIS centerl
ormation in this section for GIS centerline data is covered in-014, Issue 1, July 17, 2007. This document should be referred to for recommended audits, quality control, quality assurance, and related information. Parts of that document have been expaNENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 Community Name Right R A Postal Community Name as identified on the right side of the streetPostal Code/Zip Code Left R AN Postal or Zip code as identified on the Left side of the street. Format: ANANAN or NNNNN Postal Code/Zip Code Right R AN Postal or Zip code as identified on the Right side of the street. Format: ANANAN or NNNNN MSAG Community Name Left R A Valid service community name as identified by the MSAG on the left side of the street MSAG Community Name Rig
ht R A Valid service community name as
ht R A Valid service community name as identified by the MSAG on the right side of the street ESN Left O A 3-5 digit Emergency Service Number associated with street segment ESN Right O A 3-5 digit Emergency Service Number associated with street segment Segment ID R N Unique Road Segment ID number County Name County Name on the Left side of the street as given in FIPS 6-4 County Name RightCounty Name on the Right side of the street as given in FIPS 6-4 County Code R A County Code on the Left side of the street as given in FIPS 6-4 County Code Right R A County Code on the Right side of the street as given in FIPS 6-4 Source of Data R A Agency that last updated the record Date Updated R N Date of last update Format: CCYY-MM-DD Each street centerline segment should contain the e segment. In areas where thersegment, a
potential or probable range must be ass
potential or probable range must be assigned. 199 for one segment then 200-299 for the next with recommended that the NENA GIS Data Model fields address ranges of each street segment (e.g. 137 168 for one segment then 206 259 for the next segment) and another set of address fields be added to the GIS centerline data to accommodate any Some of the Mapped ALI and / or Computer Aided Dispatch (CAD) systems will only load street in the attribute fields. The use of actual address dependent on how other applications or entities will be using the street centerline data. Other systems may allow only continuousdifferent systems to understand their limitations. NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 . Geocoded addresses (shown as stars) along street segment havi
ng potential address ranges It is strong
ng potential address ranges It is strongly recommended that in the GIS street centerline. Using actual address ranges for the GIS street centerlines will improve the location accuracy of the geocoding on of the geocoded point would be a closer approximation of the addressing authority and the Postal Service will minimize the errors in the GIS street centerline data. The nuances of the local addressing system and available resources must be taken into consideration. This document takes the approach that the GIS street centerline data should meet the following Is spatially accurate Attributes are accurate and complete and standardized (address ranges, ESNs, Communities, Meets or exceeds all related NENA Standards Contains the necessary attributes to be used by multiple applications and users Maintained on a continual basis C
ontains all the valid addressing informa
ontains all the valid addressing information present in the MSAG after corrections to both datasets and MSAG records are made Matches the corrected MSAG to a Some recommended quality checks for attributes in the GIS street centerline data set include: All street names are present in the street centerline attributes Street names conform to the legal names as assigned by the addressing authority. (Some actices for street naming, and the legal street name may conflict with standardized naming conventions, but the 9-1-1 databases must be hronization and conformance in the NG 9-1-1 environment, e.g. zed to NE J L Higg Pkwy and all punctuations Incorrect, incomplete, missing, or inconsistent road names are corrected. From 100 To 199 101 Actual structure locationsNENA Information Document foInformation System databases with M
SAG & ALIVersion 1.1, September 8, 2009
SAG & ALIVersion 1.1, September 8, 2009 this section. In Phase One analysis, the MSAG data is the control dataset, and the GIS data is joined with the MSAG, to determine what records in the MSAG match the GIS street centerline data. The join s in the MSAG are not in the GIS street centerline data. The join process requires a composite Unique Key indevelopment process for the composite Unique Key are discussed in section 2.2.1. An assumption cannot be made as to which discrepalid. This process simply local personnel will be required to determine if . Example of GIS street centerline data reaLow Address RightLow Address LeftHigh Address RightHigh Address LeftPrefix DirectionalStreet NameStreet SuffixPost DirectionalESN RightESN LeftCommunity RightMSAG Community LeftUnique_Key12512125131258612587BAY AREABLVD069070LA PORTPASA
DENABAY AREA BLVD 0691262212623126701267
DENABAY AREA BLVD 06912622126231267012671BAY AREABLVD069070LA PORTPASADENABAY AREA BLVD 06913522135231353613537BAY AREABLVD069070LA PORTPASADENABAY AREA BLVD 0691802180318721873CALYPSO COVECT079079PASADENAPASADENACALYPSO COVE CT 07961261365665710THSTS080080SEABROOKSEABROOK10TH ST S 08040840951451512THST080080SEABROOKSEABROOK12TH ST 0804308430925862587ALBATROSSDR080080SEABROOKSEABROOKALBATROSS DR 0801768176918201821BIMINIWAY080080SEABROOKSEABROOKBIMINI WAY 0802422242322782279BLUE CANOECT080080SEABROOKSEABROOKBLUE CANOE CT 080500501514515BLUE DOLPHINDR080080SEABROOKSEABROOKBLUE DOLPHIN DR 0801776177719661967CAPRIDR080080SEABROOKSEABROOKCAPRI LN 0801740174118461847DOLPHINDR080080SEABROOKSEABROOKDOLPHIN DR 080606607652653NFLAMINGO080080SEABROOKSEABROOKN FLAMINGO 0804520452146284629SFLAMINGO080080SEABROOKSEABROOKS FLAMINGO 080101
2101312361237WFLAMINGO080080SEABROOKSEAB
2101312361237WFLAMINGO080080SEABROOKSEABROOKW FLAMINGO 0801008100910861087NHERONDR080080SEABROOKSEABROOKN HERON DR 0801151115212661267NHERONDR080080SEABROOKSEABROOKN HERON DR 0801332133314601461SHERONDR080080SEABROOKSEABROOKS HERON DR 0804900490149984999SSURF OAKS080080SEABROOKSEABROOKS SURF OAKS 0801502150315181519CORAL WAYCT093093SEABROOKSEABROOKCORAL WAY CT 0931306130713221323CORAL WAYDR093093SEABROOKSEABROOKCORAL WAY DR 093 NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 Phase Two MSAG compared to GIS street centerline In the Phase Two analysis the GIS street centerline data is the control and the MSAG is joined with the GIS data to determine what records in the GIS data match the MSAG. The join process will also show records that exist in the GIS data that a
re not in the MSAG. The join process in
re not in the MSAG. The join process in Phase Two also requires a composite Uniquermine if the GIS data, MSAG, or both require correction. For example, ifranges in the map that is not in eed to determine if the GIS stre it is determined that the street actually exists, te the street name and address ranges. Comparing the GIS data to the MSAG data will show the discrepancies between the MSAG and the GIS street centerline data, such as the street names or ESNs in the MSAG that do not match those in the GIS street centerline data. . Example of MSAG table joined to the GIS data Street NameStreet SuffixPost DirectionalRightLeftUnique_KeyPSST_NAMETYPESDLOWHIGHO/EESNBAY AREABLVD069070BAY AREA BLVD 069BAY AREABLVD1250013598LA PORTEE069CALYPSO COVECT079079CALYPSO COVE CT 079CALYPSO COVECT18001899PASADENAB07910THSTS08008010TH ST
S 08012THST08008012TH ST 080ALBATROSSDR0
S 08012THST08008012TH ST 080ALBATROSSDR080080ALBATROSS DR 080BIMINIWAY080080BIMINI WAY 080BIMINIWAY17001899SEABROOKB080BLUE CANOECT080080BLUE CANOE CT 080BLUE CANOECT24002499SEABROOKB080BLUE DOLPHINDR080080BLUE DOLPHIN DR 080BLUE DOLPHINDR500500SEABROOKE080CAPRILN080080CAPRI LN 080DOLPHINDR080080DOLPHIN DR 080DOLPHINDR17001899SEABROOKB080FLAMINGO080080N FLAMINGO 080NFLAMINGO600699SEABROOKB080FLAMINGO080080S FLAMINGO 080SFLAMINGO45004699SEABROOKB080FLAMINGO080080W FLAMINGO 080WFLAMINGO10001299SEABROOKB080HERONDR080080N HERON DR 080NHERONDR10001299SEABROOKB080HERONDR080080N HERON DR 080NHERONDR10001299SEABROOKB080HERONDR080080S HERON DR 080SHERONDR13001499SEABROOKB080SURF OAKS080080S SURF OAKS 080SSURF OAKS49004999SEABROOKB080CORAL WAYCT093093CORAL WAY CT 093CORAL WAYCT15001511TAYLORB093CORAL WAYDR093093CORAL WAY DR 093CORAL W
AYDR13001322TAYLORB093When the MSAG dat
AYDR13001322TAYLORB093When the MSAG data is joined to the GIS street centerline data the streets in the MSAG data that that are not an exact match, can beNENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 GIS Street Centerline DataESN_L Unique Key Kelly Ct S 111 Kelly Ct S 111 S Main 220 S Main 220 S Main 221 S Main 221 W Adams Ave 111 W Adams Ave 111 Notes on Joining the MSAG and GIS street centerline data: left and right ESN values differ as these may be streets that form the border of the ESNs, Postal Communities and / or MSAG Communities. These streets can be identified in the MSAG davalue in the E/O column of the MSAG. If the streets are completely within an ESN in the MSAG data then this column should contain a B for Both, assuming the MSAG data
is MSAG records that contain an Even (E)
is MSAG records that contain an Even (E) or consideration as they may form the boundary between two or more ESNs. These types of records should be carefully checked against the Left and Right ESN values in the GIS street centerline data. The GIS street centerline data and the MSAG data may store the ESN values differently. However, they must be the same length for the the street name of SMITH ST with an ESN name of SMITH ST with an ESN value of 021 in 00021 is not the same as SMITH ST 021. Many typical computer software applications for spreadsheets or databases allow the unique composite key in the MSAG to be created using the concatenate command, or similar for example Smith St may not match SMITH All extra spaces need to be removed from the unique key, e.g. replacing two spaces with one space and removing leading a
nd trailing spaces. In Figure 16 below t
nd trailing spaces. In Figure 16 below there is an extra space before Kelly in the first Unique Key record and in the second Unique Key is an extra space between Main and 220. These must be removed prior to joining the two data sets for the NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 Prefix DirectionalStreet NameStreet SuffixPost DirectionalESN RightESN LeftMSAG Community RightMSAG Community LeftUnique_KeyBAY AREABLVD069070LA PORTPASADENABAY AREA BLVD 069BAY AREABLVD069070LA PORTPASADENABAY AREA BLVD 069BAY AREABLVD069070LA PORTPASADENABAY AREA BLVD 069CALYPSO COVECT079079PASADENAPASADENACALYPSO COVE CT 07910THSTS080080SEABROOKSEABROOK10TH ST S 08012THST080080SEABROOKSEABROOK12TH ST 080NFLAMINGO080080SEABROOKSEABROOKN FLAMINGO 080SFLAMINGO080080SEABROOKSEABR
OOKS FLAMINGO 080WFLAMINGO080080SEABROOK
OOKS FLAMINGO 080WFLAMINGO080080SEABROOKSEABROOKW FLAMINGO 080NHERONDR080080SEABROOKSEABROOKN HERON DR 080SSURF OAKS080080SEABROOKSEABROOKS SURF OAKS 080CORAL WAYCT093093SEABROOKSEABROOKCORAL WAY CT 093CORAL WAYDR093093SEABROOKSEABROOKCORAL WAY DR 093. GIS Street Centerline Joined to MSAG dataMSAG.Unique_KeyPrefix DirectionalStreet NameStreet SuffixPost DirectionalESN RightESN LeftCenterline Unique_KeyBAY AREA BLVD 069BAY AREABLVD069070BAY AREA BLVD 069BAY AREA BLVD 070CALYPSO COVE CT 079CALYPSO COVECT079079CALYPSO COVE CT 079BIMINI WAY 080BIMINIWAY080080BIMINI WAY 080BLUE CANOE CT 080BLUE CANOECT080080BLUE CANOE CT 080BLUE DOLPHIN DR 080BLUE DOLPHINDR080080BLUE DOLPHIN DR 080CAPRI DR 080DOLPHIN DR 080DOLPHINDR080080DOLPHIN DR 080N FLAMINGO 080NFLAMINGO080080N FLAMINGO 080S FLAMINGO 080SFLAMINGO080080S FLAMINGO 080W FLAMIN
GO 080WFLAMINGO080080W FLAMINGO 080N HER
GO 080WFLAMINGO080080W FLAMINGO 080N HERON DR 080NHERONDR080080N HERON DR 080S HERON DR 080SHERONDR080080S HERON DR 080S SURF OAKS 080SSURF OAKS080080S SURF OAKS 080CORAL WAY CT 093CORAL WAYCT093093CORAL WAY CT 093CORAL WAY DR 093CORAL WAYDR093093CORAL WAY DR 093 NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 Joining the GIS centerline data to the MSAG data, and then joining the MSAG data to the GIS centerline data will allow a determination to be made as to where the discrepancies exist. In the First Pass the ESN and street naming discare not limited to the following: ProblemParent DataJoined DataStreet Type missingJONES RDJONESESNs differ0002323Street misspelledJONES RDJONEES RDPost Directional transposedJONES RD NJONES RD NSuffix Directional transposed JONES
RD NJONES RD NCommunity Names DifferBUR
RD NJONES RD NCommunity Names DifferBURLINGTONBURLOne Word vs. Two Word namesBLUEBONNET DRBLUE BONNET DRIncorrect StandardizationN LAKE DRNORTH LAKE DRStreet Names, Street TypeCommunity Names with inconsistent speviations in MSAG There will be streets segments in the GIS data that may not be in the MSAG such as unaddressed private roads, ramps, unaddresseImproper ESN assignment for FX records, Test records, and VoIP and Wireless Shell records. and GIS must also apply to MSAG and GIS data. As an example, the MSAG loity street may be 100- actual data ranges may be broken out by block for the corresponding street segments, thNENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 . Example of Street MAIN ST 100 333 GIS Street Centerline Ranges MAIN ST 100 121 MAIN ST
200 232 MAIN ST 300 333 Block Level S
200 232 MAIN ST 300 333 Block Level Synchronization Block level synchronization has individual MSAG enranges in the GIS street centerline data. This leentries. . Example of Block Level Synchronization MSAG Entry MAIN ST 100 121 MAIN ST 200 232 MAIN ST 300 333 GIS Street Centerline Data Ranges MAIN ST 100 121 MAIN ST 200 232 MAIN ST 300 333 Block level synchronization means the MSAG data and the GIS street centerline data are in complete agreement. However block level synchronization may not be achieved based on available Although Street Level Synchronization is acceptable there may still be discrepancies in the GIS it is recommended that the ALI dataComparing the MSAG address ranges to the GIS Street Centerline can be accomplished by manual methods as described in this document, third party software, custo
m coding using tools available in the GI
m coding using tools available in the GIS software, Structure Query Language (SQL) statements, or generatisummary of the minimum and maximum address range of each unique street segment in each ESN which can be accomplished with most GIS software. NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 . Example of GIS Street Centerline Data with MSAG Communities Prefix DirectionalStreet NameStreet SuffixPost DirectionalESN RightESN LeftMSAG Community RightMSAG Community LeftUnique_KeyBAY AREABLVD069070LA PORTPASADENABAY AREA BLVD LA PORTEBAY AREABLVD069070LA PORTPASADENABAY AREA BLVD LA PORTEBAY AREABLVD069070LA PORTPASADENABAY AREA BLVD LA PORTECALYPSO COVECT079079PASADENAPASADENACALYPSO COVE CT PASADENA10THSTS080080SEABROOKSEABROOK10TH ST S SEABROOK12THST080080SEABROOKSEABR
OOK12TH ST SEABROOKNFLAMINGO080080SEABRO
OOK12TH ST SEABROOKNFLAMINGO080080SEABROOKSEABROOKN FLAMINGO SEABROOKSFLAMINGO080080SEABROOKSEABROOKS FLAMINGO SEABROOKWFLAMINGO080080SEABROOKSEABROOKW FLAMINGO SEABROOKNHERONDR080080SEABROOKSEABROOKN HERON DR SEABROOKSSURF OAKS080080SEABROOKSEABROOKS SURF OAKS SEABROOKCORAL WAYCT093093SEABROOKSEABROOKCORAL WAY CT SEABROOKCORAL WAYDR093093SEABROOKSEABROOKCORAL WAY DR SEABROOKPSST_NAMETYPESDLOWHIGHMSAG_COMMUO/EESNUnique_KeyBAY AREABLVD1250013598LA PORTEE069BAY AREA BLVD LA PORTEBAY AREABLVD1250113599LA PORTEO070BAY AREA BLVD LA PORTECALYPSO COVECT18001899PASADENAB079CALYPSO COVE CT PASADENABIMINIWAY17001899SEABROOKB080BIMINI WAY SEABROOKBLUE CANOECT24002499SEABROOKB080BLUE CANOE CT SEABROOKBLUE DOLPHINDR500500SEABROOKE080BLUE DOLPHIN DR SEABROOKCAPRIDR17001999SEABROOKB080CAPRI DR SEABROOKDOLPHINDR17001899SEABROOKB080DOLPHIN
DR SEABROOKNFLAMINGO600699SEABROOKB080N
DR SEABROOKNFLAMINGO600699SEABROOKB080N FLAMINGO SEABROOKSFLAMINGO45004699SEABROOKB080S FLAMINGO SEABROOKWFLAMINGO10001299SEABROOKB080W FLAMINGO SEABROOKNHERONDR10001299SEABROOKB080N HERON DR SEABROOKThe ALI database can be geocoded against the GIS nce measure. This can be used as a confirmation that all ALI information will be properly located in the GIS street centerline data. The ALI will not contain all centerline data. Comparing the ALI database to GIS street centerline data will find any remaining discrepancies between the ALI and GIS street centerline data. Comparing the ALI database to GIS street centerline data is accomplished by geocoding the ALI database to the GIS street centerline data. Geocoding is the comparing tabular address information to geographic reference information. NENA Information Document foI
nformation System databases with MSAG &
nformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 Street Name Street Suffix Post Directional MSAG Community Name Postal Community Name ESN Zip Code Location excluded include VoIP and Wireless shell records, FX records, and Test Records. A table of the required ALI data can be built w. Example of the ALI Table with the Unique Key 123APPLELNWDERRY45612345BLDGA123APPLEDERRYBLDG12345144APPLELNDERRY45612345STE208144APPLEDERRYSTE456333EMARKETSTJACKSONCITY44454321RM333MARKETJACKSONCITY44454321300NVALLEYVIEWBLVDJACKSONCITY44454321300VALLEYVIEWBLVDJACKSONCITY4445432141MAINSTJACKSONCITY44354321UNIT741MAINJACKSONCITYUNIT44354321437MAPLELNBRADFORD12833333437MAPLEBRADFORD1283333328SLOOPRDBRADFORD1283333328LOOPBRADFORD33333228CHESTNUTSTTAYLOR34021212228CHESTNUTTAYLOR21212221CHESTNUTSTTAYLOR34021212221CH
ESTNUTTAYLOR2121284MAINSTTAYLOR340212128
ESTNUTTAYLOR2121284MAINSTTAYLOR3402121284MAINTAYLOR21212The table of the GIS Site / Structure Locations will look similar to the one shown in Figure 31. . Example of a GIS Site / Structure 144APPLELNDERRY45612345STE208144APPLEDERRYSTE20845612345333MARKETSTJACKSONCITY44454321ROOM222333MARKETJACKSONCITYROOM22244454321300NVALLEYVIEWBLVDJACKSONCITY44454321300VALLEYVIEWBLVDJACKSONCITY4445432141MAINSTJACKSONCITY4435432141MAINJACKSONCITY44354321437MAPLELNBRADFORD12833333437MAPLEBRADFORD1283333328SLOOPRDBRADFORD1283333328BRADFORD12833333221CHESTNUTSTTAYLOR34021222221CHESTNUTTAYLOR3402122284MAINSTTAYLOR4302121284MAINTAYLOR43021212NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 . Example of a custom report of discrepancies Discrepancy Correction Service Provider must corre
ct the ALI data, and / or the 9-1-1 DBMS
ct the ALI data, and / or the 9-1-1 DBMS provider must make the the DBMS provider for a timeline for the changes. tion into NENA i3 you must makeNote: This is a time consuming, labor intensive project that will require a significant commitment. It is not something that can be quickly completed. Avendor to have them process the discrepancies. NENA Information Document foInformation System databases with MSAG & ALIVersion 1.1, September 8, 2009 NENA Wireless (Pre-XML) Static and Dynamic ALI Data Content Technical Information Document --- DEF Format V 2.1, NENA 02-501, Issue 1, October 16, 2006 tions Operational Information Document, NENA Wireless Phase I/II Planning and ImplemA Public Safety Answering Point Managers Guide to Geographic Information Technology, a National Emergency Number Association White Paper, October 200