Why GIS & Why Internet GIS?: - Accessibility - Timeliness - Linkages of Databases
Why GIS & Why Internet GIS?: - Accessibility - Timeliness - Linkages of Databases
Maclachlan, J. C, Jerrett, M., Abernathy, T. et al. 2007. Mapping health on the Internet:
A new tool for environmental justice and public health research. Health & Place 13: 72–
86.
1
PSU Glaciers Database (Mapserver)
http://glaciers.research.pdx.edu/
2
MetroMap
http://www.metro-region.org/index.cfm/go/by.web/id=1055
3
Internet Applications
Client – Server Architecture
Considerations:
• Web performance (Network connection speed)
• Data complexity (image - WMS vs. map features
- WFS)
• Extent of user/data interaction
Major Components:
• Client viewer
• Data/map server
4
ArcGIS Server Architecture
5
ArcGIS Server Web Services
Resources on the server that are available over the internet
• Data
– Feature (for Web editing)
– Geometry (for geometric calculations such as calculating areas and lengths)
– Globe (for 3D and globe rendering)
– Image (for serving raster data and providing control over imagery delivery)
– Keyhole Markup Language (KML)
– Map (for cached and optimized map services)
• Functionality
– Geocode (for finding and displaying addresses/locations on a map)
– Geoprocessing (for modeling and analysis of spatial data)
– Mobile (for running services on field devices)
– Network Analyst (for routing, closest facility location, or service area analysis)
– Search (for enterprise search of GIS assets)
• Internet services
– Web Coverage Service (WCS)
– Web Feature Service (WFS) and Transactional Web Feature Service (WFS-T)
– Web Map Service (WMS)
6
An Example of a Server Object
7
ESRI vs. Open Source Internet GIS
• Client Applications
– ArcGIS Desktop, internet browsers or applets.
• Server Applications
– ArcGIS Server / PostGIS
• DBMS
– ArcSDE + RDBMS / MySQL, PostgreSQL, …
• Data format
– Raster: Geodatabase / GDAL - Geospatial Data Abstraction
Library
– Vector: Geodatabase / OGL - OpenGIS Simple Features
Reference Implementation
– ArcGIS SDE supports PostgreSQL
• Development environments
– ArcGIS Desktop (Author, Designer), Java, Javascript, SilverLight,
Flex, php, ColdFusion, .NET,…
Take-home Messages
• Database design is an art. You need to consider:
– System efficiency
– Query/analysis efficiency
– Management efficiency
– Interoperability considerations
• Everything is in a steady state before the next driver acts…, that is,
don’t expect the existing DBMS/GIS features will be the same down
the road.
8
Guidelines for GIS Projects
• Creating 1st-hand data is expensive (use existing data when
possible)
• Conform project data (projected coordinate systems, attribute data
type, file structure, file naming convention)
• Check the output of each geoprocessing step
• Keep a backup copy of your data
• Check hardware’s capacity (disk space, R/W access privilege,
network bandwidth,…)
• Know the software limitations/features (no space for in your file path
and file name, 2GB size limit for personal GDB, info goes with
coverage, layer files vs feature classes, file lock, …)
• Know that software can never be bug-free (so what?)
• Be resourceful in solving problems (online help, user forum, your
peers…)
• Know when to ask for help
• Learn new things on your own
• …
What’s next?