48th Fighter Wing Micro-PAVER & GeoBase Integration at RAF Lakenheath Ed Falconer & Lynne Griffiths
Acknowledgements We gratefully acknowledge the assistance of the following people in the preparation of this presentation Chris Ashmore, Pavements Manger, RAF Lakenheath George Van Steenburg, AFCESA Jane Goldberg, USAFE GeoBase Program Manager
Outline Introduction RAF Lakenheath & its Geobase Program MicroPAVER Overview MicroPAVER & SDS Methods GeoBase and MicroPAVER integration Results To Date Initial & Longer-Term Procedures Data Conversion Guide for MicroPAVER users not conversant with GIS Work in Progress Future Data updates
Introduction RAF Lakenheath Location Near Cambridge East Anglia, UK Description Part of USAFE, 3 rd Air Force 48 th Fighter Wing F-15C & E Aircraft 763 Ha. in size (1,885 acres)
Introduction RAF Lakenheath GeoBase Integration with USAFE GeoBase initiative Similar implementation across USAFE bases Data stored in an Enterprise GeoDatabase using Oracle and ArcSDE Maps served via the on- Base intranet using ArcIMS 99.3% of buildings surveyed. Other data at about the same level
Introduction MicroPAVER Overview Pavement Maintenance Management System MS Access application Store inspection data Record pavement condition index (PCI) rating per Section 0: failed to 100: excellent Predict maintenance & repair (M&R) needs for multiple upcoming years Has a GIS display tool integrated into the application GIS data stored in Shapefiles, at an expected location C:\EMS Program Files\User Data http://www.cecer.army.mil/paver/features.htm
Introduction MicroPAVER Features Pavement Inventory Network, Branch, Section Pavement Inspection Collection and recording of field inspection information Reports Summary Charts Standard Reports: Branch Listing, Work History, Branch Condition, and Section Condition Reports. Re-Inspection Reports User-Defined Reports GIS Reports Condition Analysis View the condition of your entire pavement network Prediction Modeling Historical data on pavement condition used to build a model to predict PCI of similar pavements. Work Planning Tool for planning, scheduling, budgeting and analyzing alternative pavement maintenance and repair (M&R) activities http://www.cecer.army.mil/paver/features.htm
Introduction MicroPAVER & SDS Correlation between MicroPAVER & the Spatial Data Standard (SDS) datasets 1. Network: 1. All the paved area 2. Basically equivalent to Entity Type in SDS, or a feature class in ArcMAP 2. Branch: 1. Similar to subtypes in SDS and ESRI 2. Some interpretation required 3. Section: 1. Areas of similar pavement 4. Tables in MicroPAVER 1. Application generated primary key We ll look at each for RAF Lakenheath
Introduction MicroPAVER & SDS Correlation Network: All area paved, like a feature class 1. Airfield ( Airfield_surface_area ) 2. Roads ( Roads_site ) SDS MicroPAVER
Introduction MicroPAVER & SDS Correlation Branch: Similar to subtypes, some interpretation required 1. MicroPAVER = Apron, Taxiway, Runway, Overrun 2. SDS Subtypes = Apron, Taxiway, Runway, Overrun, Parking, etc. SDS MicroPAVER
Introduction MicroPAVER & SDS Correlation Section: Areas of similar pavement 1. No correlating data type in SDS 1. MicroPAVER and PCASE have requested additions to SDS 2. Air photos can be indicative of Sections
Introduction MicroPAVER Tables Tables in MicroPAVER 1. MicroPAVER application logic and associated tables contained in MS Access 2. UNIQUEID : application generated primary key, used throughout MicroPAVER 3. Network, Branch, & Section identified, feature by feature, in MicroPAVER, UNIQUEID assigned to each feature at that time.
Methods GeoBase & MicroPAVER Integration: Work Process Goal: Match data from MicroPAVER with GeoBase Initial Procedures Define steps to bring data already being used by MicroPAVER into general alignment with GeoBase data Try to retain tabular data integrity to preserve UNIQUEID Longer-Term Procedure Re-development of map data to more accurately reflect best knowledge of ground conditions Work with MicroPAVER developers to foster means for easier integration of GIS and PAVER datasets
Methods Initial Procedures Georeference the shapefiles used by MicroPAVER, keeps UNIQUEID Used Spatial Adjustment Tool in ArcMap GeoBase data as the reference datasets Write description of the process for the MicroPAVER community
Methods Notes About the GeoReferencing Process ArcGIS is required Uses the Spatial Adjustment Tool in ArcGIS Each Shapefile is edited, georeferenced, and then saved. The original file does not have to be replaced. The GeoReferencing operation was taking about 30 minutes per dataset. Dependent on the size of the dataset.
Methods Longer-Term Procedures Re-digitize the pavement sections Current SDS feature class and existing pavements data as a guide Detailed aerial photography to help delineate the section boundaries Assign attributes from the MicroPAVER data Spatial Join center point to polygon Attribute Transfer Mapping in Spatial Adjustment Toolbar Keeps Network, Branch, Section, PID, & UNIQUEID from original datasets
Results Results To Date Georeferenced MicroPAVER datasets Developed the GeoReferencing Shapefiles Guide Detailed description for non-gis people in the MicroPAVER community of the procedure to georeference the shapefiles currently used by MicroPAVER
Results Work in Progress: Data Update Generating a new pavements dataset for MicroPAVER Spatial Join along with Attribute Transfer Mapping to bring over the attributes
Future On-Going Efforts Continued interaction with MicroPAVER developers Facilitate the interlinking of GIS data with the detailed tabular data and modeling functions available in MicroPAVER and PCASE E.g. UNIQUEID Work with RAF Lakenheath Pavements Manager to keep recomposed MicroPAVER data up to date with developments in MicroPAVER and with GeoBase