address point dataset 10/02 – present do you know where your addresses are??? keith shaw steve...
TRANSCRIPT
Address Point Dataset 10/02 – Present
Do You Know Where Your Addresses Are???
Keith Shaw
Steve Yoder
Johnson County AIMS
Address Point Dataset 10/02 – Present
Abstract
Johnson County AIMS, with the cooperation of the cities of Overland Park, Olathe, Lenexa, Leawood and Shawnee, and the Johnson County Clerk’s Office, has developed a process to collect and quality control all of the addresses within the county. These cities funnel their address points to a central server on a nightly basis and processes developed by AIMS combine these files with those controlled by AIMS and the Clerk's Office to produce a single county-wide dataset. This dataset is then exhaustively quality controlled through use of SQL statements and other software and made available to users in the county in several formats. AIMS has developed several websites allowing address assigners in the county access to view addresses that have failed QC as well as those that have been added, updated, or deleted during the previous day.
Address Point Dataset 10/02 – Present
Ancient History
Johnson County Street Centerline Dataset
Johnson County Addressing Standards
Johnson County Situs Address DB
(Address Repository)
Address Point Dataset 10/02 – Present
Starting Point, October 2002
• Why are we bothering with addresses?– I/CAD Implementation Project Initiated by the
Sheriff’s Department
• Result: JoCo Address Repository Ver 1– ArcView/Avenue app for consolidating
address points from various sources executing nightly
– But dataset not “in use”
Address Point Dataset 10/02 – Present
Starting Point, October 2002
• Address Repository Ver 1 Input Sources– Johnson County Clerk: Real Estate Tax Roll
– Johnson County PW: Unincorporated Addresses
– City of Overland Park
– City of Lenexa
– City of Olathe
– AIMS: Apartments (Non-OP, Olathe, Lenexa)
• Input appended together– Overlapping geography of input sources
– True repository/depository/dump
Address Point Dataset 10/02 – Present
In the Beginning there were None
Address Point Dataset 10/02 – Present
Addition of City Data
Address Point Dataset 10/02 – Present
Addition of Clerk Data
Address Point Dataset 10/02 – Present
The Rest Filled Out
Address Point Dataset 10/02 – Present
Shortcomings of Version 1
• Currency … “the data is not as timely as it could be” • Quality … “the data is not good enough for use by other applications”
• Maintenance … “we lack the means to update the data”
• Database Schema … “more complex than it needs to be”
Address Point Dataset 10/02 – Present
Currency“the data is not as timely as it could be”
• Only one of the input sources had a regularly scheduled and fully automated process for updating its contribution to the address repository.– Solution: Work with suppliers to fully automate their
upload to us and to execute that upload nightly.
• Points are not being added in a timely fashion.– Solution: Work with Planning Departments; Address
Coordinator Position to ensure address points are entered during the platting process
Address Point Dataset 10/02 – Present
LEAWOODaddpt1 shapefile
Maintained by Police Dept (MikePelger) using AddVantage
SHAWNEEaddpt1 shapefileMaintained by Planning Dept (April
Bowman, Mark Zielsdorf) usingAddVantage
OVERLAND PARKop_add shapefile
& units dbfMaintained by Planning/GIS (BradMunford, Tim Fitzgibbons, DougHemsath) using Tidemark/Oracle
OLATHEOlatheAddr
Feature ClassMaintained by Planning (Matt Steging)using in-house developed app (ArcMap
based)
LENEXAmasadd ArcInfo
CoverageMaintained by Public Works/GIS (BruceYounger) using in-house developed app
(ArcInfo/AML)
addpt 1 shapefile@
Leawood Share on AIMSData Server
(fromLEAWOODtoAIMS\Address)
addpt 1 shapefile@
Shawnee share on AIMSData Server
(fromShawneetoAIMS\Address)
op_add shapefile &units dbf
@OP share on AIMS Data
Server(fromOPtoAIMS\Address)
addpt1 & addptatt2
shapefiles@
dev\addrep\OverlandParkon AIMS Data Server
addpt1 & addptatt2
shapefiles@
dev\addrep\Shawnee onAIMS Data Server
Copy @ 4:25 PM Mon - Fri
Copy @ 6:55 PM Mon - Fri
Copy @ 6:45 PM Mon - Fri
oladdr shapefile@
Olathe share on AIMSData Server
(fromOLATHEtoAIMS\Address)
Sde2shp & Copy @ 6:16 PM Mon - Fri
add shapefile@
Lenexa share on AIMSData Server
(fromLENEXAtoAIMS\Address)
Cov2shp & Copy when publish new ver
addpt1 & addptatt2
shapefiles@
dev\addrep\Leawood onAIMS Data Server
addpt1 & addptatt2
shapefiles@
dev\addrep\Olathe onAIMS Data Server
addpt1 & addptatt2
shapefiles@
dev\addrep\Lenexa onAIMS Data Server
SHERIFF DISPaddpt1 shapefileMaintained by AIMS, Clerk, & ECC
using AddVantage
& addptatt2 shapefile@ dev\addrep\ShrfDispAIMS
MISSION HILLSaddpt1 shapefileMaintained by AIMS & ECC using
AddVantage
& addptatt2 shapefile@ dev\addrep\MissionHills
addpt2 shapefile@
dev\addrep\JohnsonCountyon AIMS Data Server
addptout 2 shapefile@
dev\addrep\JohnsonCountyon AIMS Data Server
Address_pt3
Feature Class
in JOCOGeog DB onadmsaimsde01
addpt3 shapefile
@ Pub Share onAIMS Data Server(addrep\shpfiles)
Addpt2
SQL Server Table
in Addrep DB on admsaimsde01
AddptFailQCSQL Server Table
in Addrep DB on admsaimsde01
Copy
Copy
Convert to addptshapefile format
Convert to addptshapefile format
Convert to addptshapefile format(assign APID)
BA
B
B
B
B
B
B
Append
INT
ER
NA
L to
Joh
nson
Cou
nty’
s N
etw
ork
EX
TE
RN
AL
to J
ohns
on C
ount
y’s
Net
wor
k
AddptChangeAddptVer11
AddptVer21
SQL Server Tablesin Addrep DB on admsaimsde01
dtsLoadAddpt
Copy(subset of fields)
Nightly Process for Rebuilding the Johnson County Address Point Dataset27 April 2004
“IN”ProvidedBy = MaintResp
andStatus = ‘Active’
dtsDetectAddptChanges
DataConverter.exe
Calculate Derived Columns(ProvidedBy, MaintResp, GeoPropID,TaxPropID, TxPIDConf)
Incorporate units.dbf into op_add.shp
B
A
Output
Input
“OUT”ProvidedBy <> MaintResp
andStatus = ‘Active’
Fie ldName Schema 1 Schema 2 Schema 3APIDNumPreDirStrNameStrTypeSecUnitDesSecUnitCityStateZipXYAliasAddTypeStatusTypeVerifyDtLastVrfdSourceUDFie ld1UDFie ld2UDFie ld3NotesCentXCentYCentScoreSymbCatgLabelLine1LabelLine2LabelLine3QCExceptFie ldCheckProvidedByM aintRespGeoPropIDTaxPropIDTxPIDConf
Copy
PRAIRIE VILLAGEaddpt1 shapefile
Maintained by Public Works Dept(Suzanne Lownes) using AddVantage
addpt 1 shapefile@
Prairie Village folder onJoCo FTP Server
(pvks\fromPRAIRIEVILLAGEtoAIMS\Address)
Copy @ 8:00 PM Mon - Fri
addpt1 & addptatt2
shapefiles@
dev\addrep\PrairieVillageon AIMS Data Server
Copy
B
Address Point Dataset 10/02 – Present
Quality
“the data is not good enough for use by other applications”
• Multiple Spellings of Street Names Multiple Abbreviations for Street Types Inconsistency with Centerline– Solution: Strict QC, Regular QC, Notification
to Supplier of Points that Fail QC– Solution: Domains from Centerline
• Duplicate Addresses– Solution: Address Point Maintenance
Responsibility regions
Address Maintenance Regions
Address Point Dataset 10/02 – Present
Quality
“the data is not good enough for use by other applications”
• Solution – Provide website showing errors that is updated nightly.
• http://ims.jocogov.org/addrep/viewerrors.asp
Address Point Dataset 10/02 – Present
Quality
“the data is not good enough for use by other applications”
• Solution - Provide definition of errors for easy cleanup.
Address Point Dataset 10/02 – Present
Maintenance“we lack an efficient means to update the data”
• Edits only made by data suppliers– Solution: Start with Address Repository Ver 1
and clean things up from there
• No Address Point Editing Application– Solution: AddVantage– Solution: Work with Leawood and Shawnee to
use AddVantage to establish & maintain address points
Address Point Dataset 10/02 – Present
Address Point Dataset 10/02 – Present
Address Point Dataset 10/02 – Present
Address Point Dataset 10/02 – Present
Database Schema“more complex than it needs to be”
• “Costs” of the 4 table implementation Address Repository Ver 1 used were greater than “Benefits”– Solution: One table
• Ever Changing Key Value– Solution: APID
• A unique ID across all suppliers• Assigned by suppliers at time an address point
added
Address Point Dataset 10/02 – Present
4 Tables 1 Table
Address Point Dataset 10/02 – Present
APID = Address Point IDentifier
• 18 Digit APID– 200310140615001234– yyyy (year)– mm (month)– dd (day)– hh (hour)– mm (minute)– ss (second)– rrrr (random number)
Address Point Dataset 10/02 – Present
The Final OutcomeThe Johnson County Address Dataset - 225738 Address Points
Address Point Dataset 10/02 – Present
Contacts
Keith Shaw
Johnson County AIMS
111 S Cherry St
Olathe, KS 66061
v. (913) 715-1568
f. (913) 715-2222
Steve Yoder
Johnson County AIMS
111 S Cherry St
Olathe, KS 66061
v. (913) 715-1544
f. (913) 715-2222