Leveraging spatial data and
imagery for campus safety
Seth Peery, Enterprise GIS
Malcolm Beckett, IT for Administration
Objectives
• Illustrate successful collaborations between VPIT
and VPAS on the management of foundational
geospatial datasets
• Demonstrate access modes and delegated
administration for Pictometry imagery
• Discuss Interior Space CADGIS workflow
• Discuss organizational and technical considerations
associated with space.facilities.vt.edu CAS
migration
• Demonstrate logging and reporting features added
by IT for Admin Svcs for space website
Collaboration
• Nearly all geospatial
problems in the
operational space have
technical, data, and
business process
components.
– VPIT == Technical
expertise and
infrastructure
– VPAS == Domain
expertise and
authoritative data
• Our data is our foundation;
systems facilitate access
• Enterprise GIS and
FS::Eng. Operations work
shoulder to shoulder
•
•
•
•
•
•
•
•
•
•
•
CAD GIS ETL
AimCAD
Pictometry
Data request workflow
Standards
Development
Database schemas and
version structure
Campus Map
Information Modeling
Basemap services
Common core
infrastructure services
Web app development
...
Pictometry Analytics
•
•
•
•
N, S, E, W and nadir perspectives for all of main campus
2013, 2011 and 2009 data available
Horizontal and vertical measurement
Overlay spatial data via ArcGIS extension AND Web UI
Pictometry Access Modes
(1) Web Application (PASE)
(2) Cached ArcGIS Server
MapService
(used in Campus Map)
(3) NAS share (for ArcGIS and EFS)
\\birdseye.gis.vt.edu\Pictometry
Managing Pictometry Access
• Multiple
web application instances
(“organizations”) can be
configured to meet
specific needs.
• Primary organization is
“VPAS”
• User accounts local to
system
• Shared Administration
model
– VPIT: Enterprise GIS
manages server
infrastructure
– VPAS: Engineering
Operations manages
users and content
Contact jashelto@vt.edu for access
to Pictometry apps and data
Interior Space CAD GIS ETL
•
Objective: create
GIS representation
of interior space
that is automatically
kept up to date
•
Integrate with
HokieServ (AiM) for
attribute data
•
ETL CAD data to
polygons (AimCAD,
gizinta)
•
Visualization
(Invision FM)
Invision FM implementation has been identified as a high priority
for both CTSSR and Facilities Services::Engineering Operations for the current year.
Space Website and CAS
• Old space website (cdcd.vt.edu) used IP restriction,
no login; was taken down
• Several business processes depended on a webbased space data access vehicle
• Enterprise GIS and Facilities Services::Engineering
Operations worked together to identify requirements
for re-launch
– Content: Identify non-sensitive graphical
and attribute standard
– Access Policy: CAS authN,
ED affiliations for authZ
– Logging and Reporting considerations
Space Data Systems, Workflows and Users at Virginia Tech, as of March 13, 2013
Space Data Producers
VPAS Systems
Central IT Systems
HokieServ Space Module
ArcSDE (Enterprise GIS)
Room Attribute
Data (Oracle DB)
6
5
1
Banner
space.facilities.vt.edu
Building and Room
Attribute Data
(Oracle DB)
VPAS T:\ Drive
[Oracle attributes
accessed from AIM
directly]
Drawings in Web Viewer
8
Space/Fixed
Assets Tables
DWGs
Edits to
Floor plans
(FS::EO)
DWGs
3
PDFs
7
4
2
PDFs
Building GIS
Polygons
LaserFiche
DWGs
Room GIS
Polygons
PDFs
LEGEND
ATLAS (CNS)
Building and
Room Attributes
Space Data Consumers
911 Center
Data product,
Native Format
Data product,
Derived Copy
Internal VPAS Users
Anyone with CAS
(Faculty, Staff,
Students, Alumni,
guest PIDs, etc.)
Academic Units
GIS Users
NI&S
FIS Space/GIS
Administrative Units
Data product,
to be removed
Contractors
Established Workflow,
working OK
Workflow to be created
or improved
Workflow to be
terminated
Data use relationship
OUP
Detailed Data Creation and Interoperability Workflows
1) Engineering Ops updates local DWG master file. Saves DWG to T:\
drive, saves PDF to T:\ drive, uses AimCAD to “publish” to AIM as part
of the update workflow. Per (2) below, EO will also manually push
DWG and PDF updates to LaserFiche going forward.
2) We plan to establish an SOP for manual data replication between T:\
Drive and LaserFiche. Meetings were held 2/26, 3/5 on this topic. The
Laserfiche software limits opportunities for automated replication.
3) Need to improve the process by which CAD updates get propagated
to GIS. How is GIS notified?
4) An automated script copies PDF files from T:\drive to
space.facilities.vt.edu. Also copies DWG files, but they’re not used.
5) space.facilities.vt.edu website accesses attribute data directly from HokieServ.
6) DB links are used to replicate attribute data to Enterprise GIS. (Currently this link
is still pointing to Archibus)
7) Enterprise GIS subsequently replicates data to NI&S ATLAS DB.
8) Right now there is no replication to Banner from the DB of record for space data
(currently HokieServ)
** Note: With the removal of DWGs from space.facilities.vt.edu, Laserfiche
becomes the most likely point for their distribution. During the course of planning
for this increased volume of users, it may be an opportune time to revisit Laserfice
access policies and SOPs.
CAS Implementation
and Security Considerations
MALCOLM BECKETT
Contact Information
Seth Peery
Senior GIS Architect
Enterprise GIS (0214)
1700 Pratt Dr
Blacksburg, VA 24061
(540) 231-2178
sspeery@vt.edu
Malcolm Beckett
Director
IT for Administrative Services (0291)
280 Sterrett Drive
Blacksburg, VA 24061
(540) 231-2319
malcolm@vt.edu