Compliance with LBRS Standards - PowerPoint PPT Presentation

1 / 27
About This Presentation
Title:

Compliance with LBRS Standards

Description:

... with LBRS Standards. An In-House Effort. Shoreh Elhami, GISP. GIS ... what's involved in an In-House effort and encourage similar GIS shops ... house update ... – PowerPoint PPT presentation

Number of Views:72
Avg rating:3.0/5.0
Slides: 28
Provided by: shoreh
Category:

less

Transcript and Presenter's Notes

Title: Compliance with LBRS Standards


1
Compliance with LBRS Standards An In-House Effort
Shoreh Elhami, GISP GIS Director Delaware County
Auditors Office
2
Compliance with LBRS StandardsAn In-House Effort
  • Introduction Objective
  • Procedure
  • Pilot Project
  • Datasets
  • Methodology
  • Approval Process
  • Update Mechanism
  • Summary

3
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

4
Objective
  • To comply with the States LBRS standards and
    guidelines to help build seamless statewide GIS
    datasets an absolute necessity for numerous
    applications including disaster response and
    transportation
  • To demonstrate whats involved in an In-House
    effort and encourage similar GIS shops (the
    hesitant ones!) to do the same

5
Procedure
  • Contacted OGRIP/ODOT multiple meetings
  • Conducted a Pilot Project
  • Compared OGRIP and Countys 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)

6
Pilot Project Compare LBRS Datasets with
Countys
  • Address Points Existing
  • Street Centerline Existing
  • Alternate Street Names Table New
  • Centerline Points New
  • Landmark Table New

7
Countys Address Points
  • Originally outsourced in 1999 the county was
    driven and address points were GPSed (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

8
Countys Address Points
9
Countys Street Centerline
  • Created from 6 inch pixel resolution Orthophotos
    stereoscopically limited attributes 1997
  • Several additional attributes since then up to
    28 attributes
  • Road mileage /- 1,700

10
Countys Street Centerline
11
Address Points - Comparison
  • Add 11 attributes
  • SEG_ID, NLF_ID, MP_VAL, BUILDING, FLOOR,
    STRUC_TYPE, FIPS_CODE, SOURCE, COLL_DATE,
    Z_COORD, OCC_STAT
  • Map 9 attributes (different name, same content)
  • PARCEL_NO, STREET_NUMB, PREDIR, PRETYPE, NAME,
    TYPE, SUFDIR, UNIT_NUMBER, ZIP_CODE

12
Address Points
  • SEG_ID (same as countys ROAD_LAYER)
  • Geo-coded the address file using the Street
    Centerline with a 5 foot side offset and 3 feet
    end offset
  • Created a 7 foot buffer from the Street
    Centerline (List Dissolve by SEG_ID)
  • 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)
  • Regular join between the layer in step 3 and the
    Address Point layer by LSN or full address as
    join item

13
SEG_ID ROAD_LAYER
14
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 Points 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

15
MP_VAL Creating the Route
16
MP_VAL
17
Address Points (contin...)
  • Z_COORD
  • Calculated from the Terrain using Functional
    Surface Interpolate Shape using 3D analyst
    extension of ArcGIS

18
Street Centerline
  • Add 21 attributes
  • L_TWP, R_TWP, L_CITY, R_CITY, L_COUNTY, R_COUNTY,
    L_STATE, R_STATE, L_FIPS, R_FIPS, JURISDIC,
    CARDINAL, BEG_LOG, END_LOG, LENGTH3D, STYPE,
    DIR_TRAV, LANES, REV_DIR, DIV, SPEED
  • Map 14 attributes
  • ROAD_LAYER, PREDIR, PRETYPE, NAME, TYPE, SUFDIR,
    F_LEFT, T_LEFT, F_RIGHT, T_RIGHT, ZIP_LEFT,
    ZIP_RIGHT, E_CODE, NLF_ID

19
Street Centerline
  • Length3D
  • 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

20
Length3D
21
Length3D
22
Alternate Street Names Table
  • Alias name information already existed in our
    street centerline layer
  • Add 12 attributes
  • STR_PRE_12, PRE_TYPE_12, STR_NAME_12,
    STR_TYPE_12, STR_DIR_12, LSN_12
  • Map 7 attributes
  • ROAD_LAYER, PREDIR, PRETYPE, NAME, TYPE, SUFDIR,
    ADDRESS

23
Centerline Points
  • The existing centerline point layer is designed
    for road intersection search the content and
    function to create this layer is different from
    the new layer
  • The new layer includes a vertex at every road
    intersection as well as where the road is
    intersected by zip code and municipal boundary
  • Includes 4 attributes
  • STR_ID, X_COORD, Y_COORD, Z_COORD

24
Landmark table
  • Countys landmarks all exist in the Address Point
    layer with their alias names
  • Extracted all of those records
  • Deleted unnecessary attributes
  • Added 1 new attribute (LM_ID)
  • Mapped 4 attributes
  • PARCEL_NO, ALIAS, ADDRESS, NLF_ID

25
Summary
  • Pilot Project started in early 2008
  • Three Submittals of datasets
  • Received multiple feedbacks
  • The last version was submitted in August 2008
  • Spent /-100 hours on the pilot project which
    became the basis for final estimates

26
Summary
  • Time estimate to complete countywide datasets
    /- 1,294 hours
  • After funding is allocated, the countywide work
    will begin
  • Delivery date /-3 months
  • Will develop a routine to publish all five (5)
    datasets annually (will maintain two versions of
    Address Points and Street Centerline layers)
  • Complete documentation will be available to
    everyone from our website

27
Questions?
  • Delaware County Auditors GIS Office
  • Todd A. Hanks, County Auditor
  • www.dalisproject.org
  • Shoreh Elhami, GISP
  • GIS Director
  • selhami_at_co.delaware.oh.us
Write a Comment
User Comments (0)
About PowerShow.com