1 / 18

NPS Perspectives

NPS Perspectives. Web Mapping. Nate Irwin - Developer, CSU/NPS RIMD. Web Mapping. Web mapping and EGIS. Our initial approach. Current and planned web map apps. Challenges that we face. Rethinking our approach. NPS use cases. Outsourcing base mapping. NPS Perspectives: What it does.

clarissa-verne
Download Presentation

NPS Perspectives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NPS Perspectives Web Mapping Nate Irwin - Developer, CSU/NPS RIMD

  2. Web Mapping • Web mapping and EGIS. • Our initial approach. • Current and planned web map apps. • Challenges that we face. • Rethinking our approach. • NPS use cases. • Outsourcing base mapping. • NPS Perspectives: • What it does. • Technology behind it. • Demo.

  3. Web Mapping Where does web mapping fit into EGIS? • Just a small piece of the puzzle. • If data and services don’t exist, web mapping is irrelevant. • The presentation tier is a good place for integration of disparate services.

  4. Web Mapping Our Initial Approach • Full-steam ahead with ArcGIS Server. • Build our own tile cache. • Use ArcSDE as our spatial engine. • Problems: • Enterprise-class ArcGIS Server installs can be difficult to setup. • Generating tile cache for large areas at many different scales is unsustainable. • The Web ADF is way too “heavy” for us.

  5. Web Mapping RIMD Web Map Applications • Current applications: • Facilities Management Mapping Application • NPS System Viewer • Radio Program Mapping Application • Civil War 150 • Several more applications planned for this FY.

  6. Web Mapping Challenges that We Face • Sustainability is the biggest challenge. • Lack of support and development resources. • Limited infrastructure (bandwidth/servers).

  7. Web Mapping The “Aha!” Moment • EGIS should focus on creating and maintaining high quality spatial data. • EGIS is in a great position to integrate services at the national level. • The NPS does not have the resources to maintain and serve service wide base imagery. • All of our mapping applications are the same!

  8. Web Mapping NPS Use Cases • Only ~20% of NPS web map applications need advanced capabilities. • Most important features/considerations: • Speed is everything! • It’s the data, stupid! • Access to high-resolution imagery. • Ability to overlay and interact with NPS-specific datasets. • Usability trumps all.

  9. Web Mapping Why Outsource Base Mapping? • Resources Saved = Lots of Money Saved • Development time saved. • Hardware freed up for other uses. • Bandwidth conserved. • BetterData • Tremendous Performance Gains

  10. Web Mapping Factors Considered • Type, Breadth, and Quality of API(s). • Licensing and Development Costs. • Quality of Base Data. • Built-in Features and Data Support. • Ability to Integrate with a GIS. • Go to http://www.nateirwin.net and search for “Web Mapping”.

  11. Web Mapping The Choices • ESRI ArcWeb Services • Google Maps • Yahoo! Maps • Microsoft Virtual Earth • Solid, well-supported JavaScript API. • Competitive pricing and integration with existing ELA. • Huge investment in data development. • Geocoding, routing, KML/GeoRSS support.

  12. Web Mapping What We Get/Don’t Get with Virtual Earth • We Do Get: • Aerial, hybrid, and street data. • Geocode and routing services. • 3D capabilities in the browser. • Access to API and developer tools. • Integration with Microsoft architecture. • What We Don’t Get: • Internal access to oblique imagery.

  13. NPS Perspectives Concepts Behind NPS Perspectives • An “object oriented” approach. • Build a solid foundation for all web map apps. • Allow for customization through “modules”. • Connect to data service. • Add routing capability. • Export data to KML. • Highly portable – code can be run anywhere. • Database-driven generation of code.

  14. NPS Perspectives Advantages (Developers and Managers) • For developers: • Re-use of code. • Targeted development. • Easily extended. • For project/program managers: • Ability to focus on data. • Wide exposure for data.

  15. NPS Perspectives Advantages (Sys Admins and Users) • For system/database administrators: • Focus on creating a single, highly-available system. • Can avoid chasing down requirements for project after project. • For users: • A rich/intuitive interface. • Access to all NPS services in a single place. • Only have to learn one application.

  16. NPS Perspectives Technology Behind It • SQL Server 2005/2008. • ArcGIS Server 9.3. • ArcSDE 9.2. • ASP.NET Web Services w/a number of open source projects. • Database-driven. • Ext JavaScript library. • Microsoft Virtual Earth API. • Microsoft MapPoint Web Services.

  17. NPS Perspectives Demo • Civil War 150. • Facilities Management Demo. • NPS Perspectives.

  18. NPS Perspectives Questions?

More Related