1 / 23

Geospatial Systems Architecture

Geospatial Systems Architecture. Todd Bacastow. GIS Evolution. http://wiki.gis.com/wiki/images/8/81/FallSDS11Fig2-1_Evolution.jpg. GIS Users. Number of Users. Internet Viewer Component Hand-held Desktop Professional. Functionality. Market Forces.

jgeary
Download Presentation

Geospatial Systems Architecture

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. Geospatial Systems Architecture Todd Bacastow

  2. GIS Evolution http://wiki.gis.com/wiki/images/8/81/FallSDS11Fig2-1_Evolution.jpg

  3. GIS Users Number of Users Internet Viewer Component Hand-held Desktop Professional Functionality

  4. Market Forces • Integrating spatial data analysis and map visualization into key business applications • Moving and consolidating spatial data • Moving client/server mapping applications to the web and looking to web services

  5. What is an architecture? • There is no universally agreed definition • A system architecture defines the structure and/or behavior of a system • Best be thought of as a representation • It is also a process because a sequence of steps • It can also be a discipline

  6. Analogies • Consider a community that maintains an infrastructure for a public service to homes and businesses. This infrastructure might include: • Electricity producers • Drinking water purification and distribution • Sewage treatment • Other waste disposal • Natural gas distribution • Public transport • Cable television and telephones • Roads and toll ways

  7. Evolution (Information + computation + hardware + communications)

  8. GIS Configuration Alternative:Stand alone Information + computation + hardware + communications

  9. GIS Configuration Alternative:Connected Desktop Information + computation + hardware + communications

  10. GIS Configuration Alternative:Centralized Configuration Alternative Information + computation + hardware + communications

  11. GIS Configuration Alternative:Centralized Configuration Alternative Information + computation + hardware + communications

  12. GIS Configuration Alternative:Federated Information + computation + hardware + communications

  13. GIS Configuration Alternative:Mobile Information + computation + hardware + communications

  14. Internet/Web Applications Browsers Web Web Server Broker Databases Information + computation + hardware + communications

  15. GIS Portal GIS Portal GIS Portal Cloud Architecture Building Blocks • Network architecture (Distributed) • Loosely Coupled • Internet Standards • Many GeoServices • Many Clients • Metadata Servers • Open / Interoperable • Full GIS capabilities GIS Users Connect and UseCheckout and Use Search Catalog and Find World Wide Web • Publish GIS Data & Services • Document in Catalog Metadata Server Author, Manage, Serve Catalogs Author, Manage, Serve Geographic Information Collections Information + computation + hardware + communications

  16. How? • Consume and expose Web services for: • Mapping • Metadata • Data sharing and distribution • Geoprocessing • Provide standard services and components for web developer (.Net, “generic XML/SOAP”, or Java API’s)

  17. GIS Services Enterprise Applications Browsers Web Broker Web Server Services Databases Information + computation + hardware + communications

  18. Integration Information + computation + hardware + communications

  19. Another view of architecture • Enterprise • Information • Computational • Engineering • Technology

  20. System Architecture • ISO Reference Model of Open Distributed Processing (RM-ODP) • Enterprise Viewpoint: • It is directed to the needs of the users of an information system. • Information Viewpoint: • It focuses on the information content of the enterprise. • Computational Viewpoint: • It deals with the logical partitioning of the distributed applications independent of any specific distributed environment on which they run. • Engineering Viewpoint: • It addresses the issues of system support (platform) for distributed applications. • Technology Viewpoint: • The technology model identifies possible technical artifacts for the engineering mechanisms, computational structures, information structures, and enterprise structures.

  21. . Architecture Development

  22. Steps • Defining Architecture Requirements. • to enable the system to meet the community’s goals and objectives. • Defining a Candidate Architectures. • to evolve an architecture gradually. • Defining Enterprise Architecture. • integrate it into an enterprise architecture model. • Defining Reference Architecture. • a working example designed and proven for use in by the participants • Validating a Reference Architecture.

  23. Timing is everything

More Related