Title: Understanding the Requirements and Using the MSAGtoGIS Comparison Reports to Improve Both Presented
1Understanding the Requirements and Using the
MSAG-to-GIS Comparison Reports to Improve
BothPresented by James Stewart,Spatial Data
Research, Inc.October 27th, 2009
2Synchronizing yourMSAG and GIS Data
- There is and will continue to be a lot of focus
on improving databases related to 9-1-1 service
and call mapping. - This particular session will focus on
synchronizing MSAG and GIS data, something that
is required in Next Generation 9-1-1 solutions
but that will also have immediate benefits as
well.
3Synchronizing yourMSAG and GIS Data
- A minimum percentage of matching records between
MSAG and road GIS data. - Quarterly reports with those percentages and with
enough detail to help you correct the mismatches.
4Synchronizing yourMSAG and GIS Data
- When the GIS and the MSAG do not match, it
indicates the potential for 9-1-1 calls to not
map correctly. Imagine the following MSAG
record, the only one for this road and community
Imagine these are the GIS features for the road
5Synchronizing yourMSAG and GIS Data
- In this example, any address between 5150 and
5157 will not map automatically since the GIS
data ends at potential address 5149.
6Synchronizing yourMSAG and GIS Data
- Also, the GIS data currently used to map 9-1-1
calls will serve as the MSAG in the Next
Generation 9-1-1 environment. - So, before the MSAG as we know it goes away, its
important to get everything you need from it into
the GIS data (but you dont need to add
ESN-related data since that will come from
polygon GIS features. Heres a brief analogy
7Synchronizing yourMSAG and GIS Data
- Think of 2 lanes on a highway that are merging
into 1 a few miles ahead. - Youd probably start by putting a few signs up
telling people about the upcoming merge.
8Synchronizing yourMSAG and GIS Data
- After a few more reminder signs, thered be the
moment of truth. (This will be the cutover to
Next Generation 9-1-1.) Imagine Lane A as the
MSAG lane and Lane B as the GIS lane.
9Synchronizing yourMSAG and GIS Data
Sure, you can cut off that old jalopy (the MSAG)
in the left lane and back up traffic for miles
behind you.
10Synchronizing yourMSAG and GIS Data
Or even worse
11Synchronizing yourMSAG and GIS Data
- What will actually happen if the MSAG and GIS are
not synchronized prior to full G9-1-1 cutover? - There will be several landline telephone
customers with physical/service/9-1-1 addresses
that no longer match the MSAG (which is now
incorporated in the GIS data). - This will cause either delay in or problems after
implementing Next Generation 9-1-1.
12Synchronizing yourMSAG and GIS Data
- Should you start comparing your MSAG and GIS data
manually? - I wouldnt want to!
- SDR has created a special comparison tool to
produce reports and these reports will be sent to
PSAPs and Data Sources across the state very soon.
13Synchronizing yourMSAG and GIS Data
- In order to produce meaningful results, SDR must
have your most recent MSAG and road centerline
GIS data. - Expect more follow up and focus on Data Sources
that have not been submitting road GIS data to
the NM 9-1-1 GIS Database (or at least notifying
SDR of a lack of updates routinely).
14Synchronizing yourMSAG and GIS Data
- All PSAPs are also required to forward copies of
their quarterly MSAG extracts to Glenn Condon at
DFA. - If you have not heard from Glenn Condon, if you
do not receive quarterly MSAG extracts from
Intrado or if you simply need assistance of any
kind with this routine quarterly process, please
contact him during or directly after this session.
15Synchronizing yourMSAG and GIS Data
- On a quarterly basis, SDR will produce new
comparison results reports for areas that have
submitted new road centerline GIS datasets or
MSAG databases (or both) and distribute those to
both the GIS agencies and PSAPs that are
responsible for their maintenance. - SDR will also produce rollups of the
synchronization percentages for DFA to use in
following up.
16Synchronizing yourMSAG and GIS Data
- Before I can explain the comparison on any level
of detail, a brief look at where the road data
comes from that is used for this comparison - Data Sources submit road data to the NM 9-1-1 GIS
Database. - SDR edge matches it with other neighboring
datasets and adds community values where missing,
compiling it all effectively into a single
dataset statewide.
17Synchronizing yourMSAG and GIS Data
- SDR must create a road centerline GIS layer
containing all roads and only roads within the
relevant PSAPs response area. - SDR compares every road centerline GIS feature
for a match in the MSAG and then compares every
MSAG feature for a match in the GIS data,
resulting in essentially two reports and sets of
match percentages.
18Synchronizing yourMSAG and GIS Data
- MSAG data must also be converted to a spreadsheet
(.xls) format since many of these arrive in text
(.txt) format. - In some cases, there is more than one MSAG per
PSAP as well and those must be combined for this
comparison. (For instance, the Valencia County
RECC PSAP covers the areas in the Valencia and
Los Lunas MSAGs.)
19Synchronizing yourMSAG and GIS Data
- Each comparison (GIS-to-MSAG and MSAG-to-GIS)
works as follows - Does the record have a perfect road name match in
the other database? - If yes, the automation continues (see 2).
- If no, the automation flags the record as having
no name match in the other dataset. - Example E MAIN ST matches E MAIN ST but NM
HIGHWAY 151 does not match NM HWY 151.
20Synchronizing yourMSAG and GIS Data
- Does the record have a perfect community name
match in the other database? (Must be in a
record with the same road name.) - If yes, the automation continues with the address
range check (see 3A). - If no, the automation still attempts to find a
record with a matching range since, at this
point, most Data Sources are not even submitting
community values and the values entered by SDR
may not match the MSAG communities (see 3B).
21Synchronizing yourMSAG and GIS Data
- 3A. Does the record have an address range that
fits entirely within the address range of one
or more records in the other database? (Must be
in a record with the same road name and community
value.) - If yes, the automation marks the record as a
perfect match. - If no, the automation marks the record as having
a range mismatch only.
22Synchronizing yourMSAG and GIS Data
- 3B. Does the record have an address range that
fits entirely within the address range of one
or more records in the other database? (Must be
in a record with the same road name, but does not
require a community value.) - If yes, the automation marks the record as a
name and range match only. - If no, the automation marks the record as having
a name match only.
23Synchronizing yourMSAG and GIS Data
MSAG extract
Road GIS extract
Each MSAG and GIS record has a complete match in
the other dataset.
24Synchronizing yourMSAG and GIS Data
- Example 2 (name and range match only)
MSAG extract
Road GIS extract
The MSAG record has no complete match in the road
GIS data. The 1st GIS record also has no
complete MSAG match however, the 2nd record does
match the MSAG.
25Synchronizing yourMSAG and GIS Data
- Example 3 (name and community match only)
MSAG extract
Road GIS extract
The MSAG record has no complete match in the road
GIS data because the GIS address range goes only
to 412 on MUSTANG CIR. However, the GIS feature
does match the MSAG completely.
26Synchronizing yourMSAG and GIS Data
- Example 4 (name match only)
MSAG extract
Road GIS extract
The road names match between the MSAG and road
GIS. Also, ignoring the community mismatch, both
road GIS records fit the MSAG range but the same
is not true in reverse.
27Synchronizing yourMSAG and GIS Data
- Example 5 (no name match)
MSAG extract
Road GIS extract
The complete road name does not match between the
MSAG and road GIS data, making all other
automated comparisons meaningless.
28Synchronizing yourMSAG and GIS Data
- When you receive the comparison report, it will
contain a copy of your MSAG as well as a table
containing the attribution for each road
centerline GIS feature used in the comparison. - Each record in each table will contain coding
denoting one of the 5 situations listed
previously.
29Synchronizing yourMSAG and GIS Data
- Here are some examples of MSAG records coded for
matching to the road centerline GIS data
30Synchronizing yourMSAG and GIS Data
- From these, SDR will also create simple s
indicating the proportion of each result as a
whole.
31Synchronizing yourMSAG and GIS Data
- The automation is essentially producing two sets
of results and uses the four other spreadsheet
tabs to do so. Look at the bottom left portion
of your Excel screen. The STATS tab is what we
saw on the previous slide
32Synchronizing yourMSAG and GIS Data
- The RCL tab contains all of the road centerline
GIS features used in the comparison. - It is not in the format that you submitted it, in
all likelihood. Instead, its in the format that
is used at the PSAP. - Look at the DSID tab to see the Data Source that
submitted each record. This list should tend to
be slightly over-inclusive.
33Synchronizing yourMSAG and GIS Data
- At the far right side of the RCL tab are the
results for each record. These results are
obtained by comparing each record to the records
in the MSAG_Compressed tab. - NAME_OK
- YES if the automation finds one record in the
MSAG_Compressed tab with the same exact name.
34Synchronizing yourMSAG and GIS Data
- COMM_OK
- YES if the automation found a name and
community match in at least one record on the
MSAG_Compressed tab - NO if there was only a name match but no record
with a name and community match - - if the NAME_OK check resulted in no match.
(It doesnt check community without a name match.)
35Synchronizing yourMSAG and GIS Data
- RANGE_OK
- YES if the automation found a record in the
MSAG_Compressed tab with the same name and
community and which contains the examined road
records address range. - NO see YES except the RCL range didnt fit
within the MSAG_Compressed range - - if the name and community dont match, it
does not check the range.
36Synchronizing yourMSAG and GIS Data
- RANGE2_OK
- YES if the automation found a record in the
MSAG_Compressed tab with the same name and
which contains the examined road records
address range, regardless of community. - NO see YES except the RCL range didnt fit
within the MSAG_Compressed range - - if the name doesnt match, it does not check
the range.
37Synchronizing yourMSAG and GIS Data
- The same basic principles and coding apply to the
reverse comparison, where each MSAG record is
compared to a compressed version of the road
centerline GIS data. - The MSAG tab is where youll find the
individual results.
38Synchronizing yourMSAG and GIS Data
- NOTE There are a handful of records in each
database that wont match the other database for
good reason
MSAG extract
Road GIS extract
Once we identify all versions of this type of
record, we will delete them before compiling
results.
39Synchronizing yourMSAG and GIS Data
- OK, so now you have your report. What should you
do to improve synchronization between the
databases?
- Recommendations
- Have a meeting (or series of meetings) between
your GIS agencies and your MSAG Coordinator and
go through the report determining how each
flagged record will be fixed.
40Synchronizing yourMSAG and GIS Data
- Start by standardizing road names in the two
datasets (using USPS standards in Publication 28
to avoid future changes). You may need to change
both databases to do this. - Next, fill in your community values in the road
GIS data and make sure they match the values in
the MSAG.
41Synchronizing yourMSAG and GIS Data
- Correct address range disparities last and remove
all catch all records (Session 2A). In order
to do this, you will need to ensure that the same
basic convention is used in each database,
especially on city blocks that often dont go up
to 99 on each block. If you smooth over gaps
in the addressing in one database and not the
other, its best to remove those gaps entirely
from both. Some options
42Synchronizing yourMSAG and GIS Data
CITY BLOCK RANGE FIX 1 You can create one MSAG
and GIS record per block and stop at the last
real potential address number instead of
including several blocks in one MSAG record.
This is the ideal solution as addresses outside
of the real range cannot make it into the
telephone company customer records.
MSAG record prior to edits
MSAG records after edits
43Synchronizing yourMSAG and GIS Data
CITY BLOCK RANGE FIX 2 The opposite.
Generalize ranges in the MSAG and GIS to include
everything from 00 to 99 on each block. This
is somewhat less time consuming but will allow
illegitimate addresses into the system if a
resident gives it to the telephone company. It
will also make call mapping less accurate.
MSAG records prior to edits
MSAG record after edits
44Synchronizing yourMSAG and GIS Data
CONCLUSION No one is expecting everything to
change over night. If you work consistently on
it, you should see better matching percentages
each time you receive an updated report and see
better call mapping results as well. (Of course,
you must be submitting your new MSAG extracts and
updated road centerline GIS data for the
comparisons to be up-to-date!)