Developing for the GeoWeb: Notes From The Field Dev Summit 2009

notes from the field

most of

are technologists

we are comfortable with complexity

how does this impact our projects

February 2005

Techical: Google Maps is released Jesse

So what?

web 2.0

expectations changed

forever.

we (technologists)

what box?

“data”

“interface”

“tools”

“tasks”

we must throw out…

simple tools answering complex questions

the lesson of February 2005

where to start?

GeoWeb

address spatial business problems in a browser

publish &consume services

but…

to be successful…

we must understand…

trumps features usability

we must master…

Atom WFS .NETXHTML CSS Ajax TDD Javascript RSS JSON REST XML GeoRSS WMS

more to learn

Todays Lesson Plan Same tools Javascript 1. Object Oriented 2. Ajax: GETting and POSTing Same workflows 3. Intro to JQuery and Dojo 4. Designing RESTful services Same terminology 5. JSON and JSONP 6. CSS and browser tweaks Worse performance 7. Silverlight & Flex

more tools

we must understand…

what users want

users want

how do we tackle this?

design ideas

examples please!

1 Road Project Management Internal workflow application SAP integration OpenLayers + WMS + Dojo ArcGIS Server 9.2

2 Emergency Response workflow application multi-service “mash-up” ESRI JS API + Dojo ArcGIS Server 9.3 REST

3 avian influenza tracking system public facing focused search tools virtual earth + dojo ArcGIS Server 9.2 + Custom Tile Server

interface design

fewer layers

Cram desktop into A browser

Screen shot of CDOT

provide feedback!

what should I do?

handle the “null-case”

make it fast!

SAP Get Project List

hold their hand

hide the details language matters

Locate structures near my project.

really means…

generic tool could work…

for technologists

reassure the user.

validate as soon as possible

SAP Ref Selection

pre-validate whenever possible

protect users from themselves

system design

project process

low value

just-enough design

map the workflow

iterate on paper

• Create wireframes

choose a map canvas

keep it simple

define services

REST API

custom services

not available

possible but not optimal

“chatty”

faster

details please!

1 use the SOAP API

ArcGIS Server Web Server ASP.NET MVC App SOAP SOC Process AGS SOAP API Controller IIS JSON

2 COM utilities & server object extensions

IIS ASP.NET MVC App Controller JSON Web Server SOAP Web Service ADF Connection COM Utility SOC Process ArcGIS Server

can we code now?

start coding!

match the model

MARC SCREENS

release early

release often

listen feedback

Summary:

expectations: changed

kung-fu: needed

design: workflow

focus: usability

performance: critical

details: hidden

Dave Bouwman dbouwman@dtsagile.com http://blog.davebouwman.net http://twitter.com/dbouwman

http://www.dtsagile.com	237
http://blog.davebouwman.net	88
http://blog.davebouwman.com	39
http://dtsagile.com	31
http://www.moderne-unternehmenskommunikation.de	18
http://gisdk.blogspot.com	5
http://www.slideshare.net	5
file://	1
http://www.arcexperts.net	1

Developing for the GeoWeb: Notes From The Field Dev Summit 2009

by Dave Bouwman on Mar 26, 2009

Accessibility

Categories

Tags

Upload Details

Usage Rights

9 Embeds 425

Statistics

Developing for the GeoWeb: Notes From The Field Dev Summit 2009 — Presentation Transcript