1 / 13

NR 621: GIS on The Web

NR 621: GIS on The Web. Jim Graham Spring 2009. Dynamic Web Pages (server). Client. Server. Internet. Database. Browser. Web Server. Web Script. HTML File. HTML File. Image File. Image File. GIS Web Servers. Client. Server. Internet. Database. Browser. Web Server. Web Script.

cicely
Download Presentation

NR 621: GIS on The Web

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. NR 621: GIS on The Web Jim Graham Spring 2009

  2. Dynamic Web Pages (server) Client Server Internet Database Browser Web Server Web Script HTML File HTML File Image File Image File

  3. GIS Web Servers Client Server Internet Database Browser Web Server Web Script HTML File HTML File Image File Image File GIS Server GIS Files

  4. GIS On the Web Closed Servers Client Software Open Servers Internet Map Quest Map Quest Google Maps Google Maps GODM Client i3 GODM Server GoogleEarth Keyhole KML Files ArcExplorer ArcMap World Wind JPL

  5. Key Issues • Parameters: • Schedule • Resources ($, people, equipment) • Features • Performance • Data: Large amounts can kill performance • 3 Decisions: • Client features • Web Server (GIS Server, Scripting, Database) • Data configuration

  6. Solutions • Small amounts of data, static: • Files (Shapefiles and TIFFs) to download • KML files on a web site for GoogleEarth • Shapefiles with a GIS web server • Medium amounts of data, query/search, periodic updates: • GIS web server with spatial database • Large amounts of data, flexible, immediate updates: • Custom solution with spatial database

  7. Web-based clients: GoogleMaps MapQuest GODM Client GoogleEarth Plug-in ArcIMS (HTML, Java) Internet-based clients: ArcExplorer ArcMap GoogleEarth World Wind VirtualEarth Client OSes: Windows Macintosh Linux UNIX Browsers: IE FireFox Safari Chrome? Client Support

  8. Key Client-Side Questions • Required features: • Web pages with 2d content? • Querying (search)? • 3d visualization? • Web-based (GoogleEarth plug-in)? • Application based (GoogleEarth)? • Recommendation: • 2D web site w/search • GoogleEarth support with KML files

  9. OS: Windows Linux UNIX Web Server Apache Internet Information Server Framework/Language: ASP: VBScript ASP: Jscript VB.NET C#.NET PHP Java Python Cold Fusion Server Alternatives

  10. Server Criteria • We don’t have IT to support anything but windows • IIS is easier to support than Apache and this can be changed later if desired • Scripting Alternatives: • PHP: Fast, easy, OpenSource • ASP/VBScript: Fast, easy • Question: Is OpenSource and issue for sponsors? (Don’t think they care)

  11. GIS Web Serving • All can use Shapefiles and external raster files. The issue is the Map Server and the Database • ArcIMS w/SQL Server • ArcIMS w/ArcSDE and SQL Server • Oracle Spatial • Map Server w/PostreSQL and PostGIS • GODM Server w/SQL Server • ERMapper (rasters only)

  12. GIS Server Alternatives • Shapefiles -> Spatial Database • Rasters -> JPEG and/or PNG tile files • Alternatives: • Map Server w/PostgreSQL & PostGIS • GODM w/SQL Server(?) • ArcIMS w/ArcSDE & SQL Server • Issues: • High-resolution polylines • Large extent • Querying (Symbology?) • Updates

  13. GODM Solution • Client Environments: • Custom client with various backgrounds and projections: GoogleMaps, MapQuest, NASA, i3 • GoogleEarth w/KML files • Server: • GODM Server w/Custom spatial data format (topological) inside SQL Server

More Related