1. Open Source Geospatial software for the the Army Corps of Engineers Wetlands Regulatory program FOSS4G2007 Victoria, B.C. Canada Michael Smith Engineer Research & Development Center Remote Sensing/GIS Center US Army Corps of Engineers, Hanover, NH michael.smith@erdc.usace.army.mil

2. Task: Revise Regulatory Software  Geospatial Input  Geospatial Intelligence  Complex forms  Many Business Rules  National Upward Reporting / Geospatial Reports

3. Business Requirements  Account/password management for thousands of users  Strictly Defined Roles and Access  Remote Data Centers (run by people we’ve never met on machines we’ve never seen)  24x7 Systems with Fail-Over/Disaster Recovery  Oracle standby servers and load-balanced apache  24x7x365 DBAs at data centers

4. ORM1  VB with Oracle data storage (3 stored procedures)  Mapping done via ArcIMS called from VB  3 years development for point spatial storage  $5 M budget  2 Updates in 2 years  District by district deployment

5. ORM1

7. ORM1 GIS Implementation USACE Corporate SDE/Oracle geodatabase OMBIL / ORM CorpsMap District eGIS COMOBJECTEXCHANGECOMOBJECTEXCHANGE AnalysisAnalysis RFMIS EngLink ORM Data V&V Process SDESDE Lat/Long PLSS Congressional County Water body Soil type HUC ORM Input Panels Write to OMBIL IMSIMS REMIS

8. ArcGIS Server Architecture

9. Few Moving Parts Apache MapServer CGI Oracle Web Services

10. Not that exciting an architecture ( but do you really want it exciting? )  Oracle Database backend - all data stored there  Apache frontend  Pl/Sql Stored Procedures - for Business Logic  Oracle Application Express (Web metadata-driven front end)  MapServer provides GIS visualization for web  MapServer provides OGC interoperability (cascading WMS/WFS and integration with ArcGIS)

11. One of Many (Clients) Approach Our web interface and MapServer CGI just one method to get at the data  Google Earth (kml from Oracle, wms from MS)  ArcGIS (via SDE, wms, VB.net)  Bentley MicroStation (via ProjectWise)  Others…..

12. Metadata Driven Development Environment

13. Apex - more

14. Application Reports

15. Activity / Session State Management

16. ORM2  1 year development (actually around 7 months, 5 months of group meetings on peoples gripes)  $750K budget  Point / Line / Poly spatial storage  Web front end with Oracle backend (everything in oracle with mapserver cgi)  1 division (5 districts) initial deployment  All remaining districts (except 1) deployed following month

17. Hardware Platform  Hardware  Sun Fire 12K / 32 cpu / 32 gb RAM - for Database  1 of 40 Oracle Databases (1 gb ram allocated)  2 Sun Fire T2000 with Load Balancer / Shared with 3 others  Requirements are minimal though  Serve 50 (10 concurrent) users with Oracle XE (free) on a laptop (macbook pro) (in a vm)

18. Benefits  Very stable  same architecture for 6 years  Scalable  supporting ~ 1350 users, around 500 distinct users per day, 30-35K page views, 9K map views  Oracle XE is free / Apex is included  If not XE, your org probably has Oracle already  If not, Postgres / PostGIS

19. Page Views

20. ORM2 Dashbaord

21. Full History

22. On-screen Digitizing

23. Consume WMS

24. WMS Services

25. Spatial Details from Query

26. Spatial Analyses

27. Spatial Searches

28. Spatial Searches - By Address

29. Google Earth - Export

30. Google Earth - Import

31. Presentation from 2004  Build enterprise class applications with unlimited scalability …  Oracle runs all the Mission Critical Systems of the Corps  Sun or Linux Servers at Agency Data Centers  Independent development, testing and production environments  Oracle is our primary RDBMS  Oracle is our primary application & web development environment  Oracle Spatial geometry for application specific and dynamic geospatial data  We use shape files or Oracle for rendering read only/basemap data  PL/SQL for domain logic  University of Minnesota Map Server for Map Generation  Adopt OGC Standards (WMS/WFS) and SOAP/XML RPC Access to Geospatial Data  DMS OWTchart for graphing  Refractions OGC->IMS script for ESRI compatibility

32. Questions?

33. Versions over the Years YearESRIOur Choice 2001MapObjectsForNet / MapServer 3 2002ArcView IMSMapserver 3.5 2003ArcIMS 3Mapserver 3.6 2004ArcIMS 3Mapserver 4.2 2005ArcIMS 4Mapserver 4.6 2006ArcMap ServerMapserver 4.8 2007ArcGIS ServerMapserver 4.10 (soon 5)