Compliance with LBRS Standards Compliance with LBRS Standards An In-House Effort An In-House Effort Shoreh Elhami, GISP GIS Director Delaware County Auditor’s Office 2008 Ohio GIS Conference September 10-12, 2008 Crowne Plaza North Hotel Columbus, Ohio
27
Embed
Compliance with LBRS Standards An In-House Effort Shoreh Elhami, GISP GIS Director Delaware County Auditor’s Office 2008 Ohio GIS Conference September.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Compliance with LBRS StandardsCompliance with LBRS StandardsAn In-House EffortAn In-House Effort
Shoreh Elhami, GISP
GIS Director
Delaware County Auditor’s Office
2008 Ohio GIS Conference
September 10-12, 2008
Crowne Plaza North Hotel
Columbus, Ohio
Compliance with LBRS Standards
An In-House Effort• Introduction & Objective• Procedure
• Pilot Project• Datasets• Methodology
• Approval Process• Update Mechanism
• Summary
Introduction – Delaware County
• Located in central Ohio, fastest growing county in the State of Ohio since 1980
• 21st fastest growing county in the nation
• A mature GIS system – circa 1990 • A comprehensive GIS dataset – over
100 data layers• To learn more, visit our website at:
www.dalisproject.org
Objective• To comply with the State’s LBRS
standards and guidelines to help build seamless statewide GIS datasets; an absolute necessity for numerous applications including disaster response and transportation
• To demonstrate what’s involved in an In-House effort and encourage similar GIS shops (the hesitant ones!) to do the same
Procedure• Contacted OGRIP/ODOT; multiple meetings• Conducted a Pilot Project
• Compared OGRIP and County’s datasets• Populated the pilot area with new information and
submitted all datasets
• Met with OGRIP again; this time other decision makers attended
• In the process of signing the MOA• OGRIP will sign next; funding will be allocated• Countywide work will start• Annual Update Mechanism (all processes will be
documented and available to all interested parties)
Pilot Project: Compare LBRS’ Datasets with County’s
• Address Points – Existing• Street Centerline – Existing • Alternate Street Names Table –
New • Centerline Points – New• Landmark Table – New
County’s Address Points
• Originally outsourced in 1999; the county was driven and address points were GPS’ed (plus front façade photos) – countywide update interval is 5 years
• Annual in-house update – driving • Includes all structures within the
county (+/- 80,000 structures)• Rich attribute data – 35 attributes
County’s Address Points
County’s Street Centerline
• Created from 6 inch pixel resolution Orthophotos stereoscopically; limited attributes – 1997
• Several additional attributes since then – up to 28 attributes
ROAD_LAYER):1. Geo-coded the address file using the
Street Centerline with a 5 foot side offset and 3 feet end offset
2. Created a 7 foot buffer from the Street Centerline (List – Dissolve by SEG_ID)
3. Conducted a Spatial Join between layers from step 1 and 2 (to get the SEG_ID from the buffer layer to the geo-coded layer)
4. Regular join between the layer in step 3 and the Address Point layer by LSN or full address as join item
SEG_ID: ROAD_LAYER
Address Points (contin...)
• NLF_ID (ODOT ID Number)• Joined Address Points to road centerline by
using full street name as join item• MP_VAL (Address Point’s 3D Distance)
• Created a route, used “Locate features along a route” function of 3D Analyst to transpose address points on the route (5000’ distance)
• Created an event point layer using the table from the previous step; deleted all records that their NLF_ID was not equal to RID (Route ID) to weed out erroneous records
• Joined the clean layer to Address Point; used LSN as join item (excluded zero addresses); Calculate MP_VAL = MEAS
MP_VAL – Creating the Route
MP_VAL
Address Points (contin...)
• Z_COORD• Calculated from the Terrain using
Functional Surface > “Interpolate Shape” using 3D analyst extension of ArcGIS
• Created a Terrain from 6-foot Contour (from 2’ contour) and converted to raster to create a DEM (3D Analyst – Conversion – From Terrain – Terrain to Raster)
• Use the Functional Surface > “Surface Length” function (3D Analyst Extension of ArcGIS) to calculate 3D Length
• BEG_LOG & END_LOG• Manually created for pilot area; though it
will be calculated by ODOT for the county
Length3D
Length3D
Alternate Street Names Table
• Alias name information already existed in our street centerline layer