Geologic Web Services: Planning and Design

1. Geologic Web Services: Planning and Design Sheena K. Beaverson

2. Introduction • Existing ISGS Map Services • Project Planning • Navigation Strategies • Technical Nuts and Bolts • Current Needs and Future Projects

3. Introduction • AXL Design • Christopher McGarry • MXD Design • Antigone Dixon-Warren • Steven Gustison • Christopher Korose • Database Design • Alison Lecouris (Oracle) • Danial Nelson (ArcSDE) • Beta Testing – many project participants, management

4. Geologic Web Services Existing Map Services

5. Introduction • Illinois Digital Orthophoto quarter Quadrangles • File viewing and download • Released on-line June, 2001 • ArcIMS 3.0 • .axl file calling multiple image catalogs • Geography Network Challenge 3rd Place Winner • Access to over 4,100 data files • Data files contained within .zip file bundles

9. Existing Map Services • Illinois Historic Aerial Photographs • File viewing and download • Released on-line September, 2003 • ArcIMS 4.0, migrated to ArcIMS 4.0.1 • .axl file calling one image catalog (base imagery) • Access to over 8,100 data files (25 counties) • Additional 20 counties to be added • Imagery in MrSID format

14. Existing Map Services • Illinois Oil and Gas Resources • Released on-line February, 2004 • ArcIMS 4.0.1 and ArcMapServer 4.0.1 • .mxd file calling shapefiles, Arc/Info coverages, ArcSDE data layers • Access to over 180,000 wells in Illinois • Oracle data points • Over 83,000 well records reviewed and updated

18. Existing Map Services • Illinois Natural Gamma Ray Logs • To be released on-line June, 2004 • ArcIMS 4.0.1 and ArcMapServer 4.0.1 • .mxd file calling shapefiles • Access to about 350 individual logs

21. Existing Map Services • Illinois Water Wells • To be released on-line June, 2004 • ArcIMS 4.0.1 and ArcMapServer 4.0.1 • .mxd file calling ArcSDE data layers • Access to over 277,600 wells in Illinois • Oracle data points • No review of well records included

24. Existing Map Services • ISGS-IDOT Extranet • Not released publicly • ArcIMS 4.0.1 and ArcMapServer 4.0.1 on PC • Custom applications drive reporting of Preliminary Envronmental Site Assessments (PESAs) • MIDCARB – Midcontinent Interactive Digital Carbon Atlas and Relational dataBase • Multi-state map service served from Kansas

26. Geologic Web Services Project Planning

27. Project Planning • Data collection and assessment • Assemble data layers and assess data format • Modify data layers accordingly (migrate into SDE?) • Construct data sub-sets via query, identify table joins, add attributes for hyperlink field • Gather information on cartographic display • Existing paper maps, symbol sets, attribute information • Identify criteria to address confidential data points • Identify criteria to address homeland security concerns

28. Project Planning • Educate mapping team about differences between paper maps and cartographic maps • Scale dependant rendering • Limited viewing area • Screen real estate • Identify target audience • General public, K-12 students, college students • Field workers, drillers, exploration geologists • Internal staff or inter-agency team • (confidential data), screen proportions, fast internet connections • Internet, Intranet, Extranet

29. Project Planning • Identify modifications to template map service • Are software upgrades needed? • Have data storage routines changed significantly? • Are new base data layers now available? • Have instabilities emerged in original map service that can be readily addressed? • Initiation of a new project brings the temptation to upgrade existing map services. • Try not to be tempted by the dark side!

30. Project Planning • Meet with project staff to determine: • Must-have data layers • Possible additional data layers • Data display order – ‘the data stack’ • This is an iterative process • Avoid ‘what if I want…’ temptations • Can add additional data layers in the double digits range • Goal: guide web visitors to data quickly and logically

31. Project Planning • .mxd or .axl development Phase I • Add new base data, re-design display parameters • Add project-specific data layers • Review data stack with respect to emerging cartographic issues and complexities in symbology • Also an iterative process • Modifications to original plan by Technical staff • Preliminary feedback from mapping team

32. Project Planning • .mxd or .axl development Phase II • Program project-specific customizations • ArcIMSparam.js file arrays • Data field attribute display set and field aliasing • Enable hyperlink layers • Customized data layer labeling and added symbols • Customize html frames for web page display • Resist the temptation to initiate Phase II programming until after the data stack is finalized • Gives the impression of being ‘done’ far too soon

33. Project Planning • Phase I Beta testing, content assessment • Solicit comments from your mapping team on any feature of the map service and web display. • Font selection, size, display • Display and interaction of data layers • Data attribute labeling and order • Appropriateness of scale dependant data layer display • Completeness and usability of overall interface • This is the time to get nit-picky! • Have ‘everything and kitchen sink’ impulses won out? • Will our audience comprehend the story being presented?

34. Project Planning • Complete revisions from Phase I Beta testing • Phase II Beta testing, debugging • Solicit comments from your mapping team • Have editorial points been addressed? • Have we created new problems as a result? • Did we miss anything big in Phase I? • Solicit input from map service developers you know • If the buttons and navigation don’t make sense to them, how will a wider audience be able to use the map?

35. Project Planning • Development of support resources • Metadata for data layers and map service itself • Web pages to supply project information • Web page guide to interactive map components • Review of all web resources by editorial staff • Promote On-line release • Navigation How-To presentations to target audiences

36. Geologic Web Services Navigation Strategies

37. Navigation Strategies • Keep it simple • Web customers are familiar with browser tools • Web customers are unfamiliar with GIS tools • Using ESRI tool GIFs helps all interactive map developers educate new users • Complex data stacks can get confusing • ArcIMS to ArcMapServer to ArcSDE is a new setup • Limit web navigation to map service through one point

42. Geologic Web Services Technical Nuts and Bolts

43. Technical Nuts and Bolts • Production Server and Developmental Server • ArcIMS 4.0.1 UNIX machine, SunOS 5.8 • ArcMapServer 4.0.1 on PC • IDOT Extranet, other Developmental Servers • ArcIMS 4.0.1 on PC also with ArcMapServer 4.0.1

44. Technical Nuts and Bolts • Natural Gamma-Ray Logs Map Service • First map service designed on PC and ported to UNIX • Naming convention discrepancies • ArcIMSparam.js vs. arcimsparam.js • File content discrepancies • selFieldList: #ID# and #SHAPE# vs. #Id# and #Shape#

46. Technical Nuts and Bolts • Fix for ArcMapServer image naming issue after successful creation of map service with .mxd in administrator and website creation • navigate to the "javascript" directory • edit the javascript textfile "aimsXML.js: • a) find "function getURL" and "function getLegendURL". • b) directly above the line "return theURL;" add the code: • //* ISGS ArcMap Server fix added here • theURL = theURL.toLowerCase(); • //* end fix

47. The complete getURL functions should look like: • // get URL • function getURL(theReply) { • var theURL = ""; • var startpos = 0; • var endpos = 0; • var pos = theReply.indexOf("OUTPUT"); • if (pos != -1) { • theURL = getInsideString(theReply,'url="',dQuote,pos,0,false); • } • legendImage = getLegendURL(theReply); • //* ISGS ArcMap Server fix added here • theURL = theURL.toLowerCase(); • //* end fix • return theURL; • } • // getLegendURL

50. Technical Nuts and Bolts • Customizing the Toolbar Frame output • Show one tool per line • Insert table cell with tool description • Re-order tool selection • Insert blank table cells for logical spacing