0
notes
 from the
       field
most
 of
are
 technologists
we
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 JQu...
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 Til...
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
whew!
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




                                  ...
2
COM utilities
  &
 server object
     extensions
IIS

       ASP.NET MVC App

          Controller




JSON
                                          Web 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
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Developing for the GeoWeb: Notes From The Field Dev Summit 2009
Upcoming SlideShare
Loading in...5
×

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

4,028

Published on

Describes the thought process and concepts needed to create compelling and successful "geoweb" applications. Presented at the 2009 ESRI Developer Summit in Palm Springs, CA

Published in: Technology
2 Comments
14 Likes
Statistics
Notes
No Downloads
Views
Total Views
4,028
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
331
Comments
2
Likes
14
Embeds 0
No embeds

No notes for slide

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

  1. 1. notes from the field
  2. 2. most of
  3. 3. are technologists
  4. 4. we
  5. 5. we are comfortable with complexity
  6. 6. how does this impact our projects
  7. 7. February 2005
  8. 8. Techical: Google Maps is released Jesse
  9. 9. So what?
  10. 10. web 2.0
  11. 11. expectations changed
  12. 12. forever.
  13. 13. we (technologists)
  14. 14. what box?
  15. 15. “data”
  16. 16. “interface”
  17. 17. “tools”
  18. 18. “tasks”
  19. 19. we must throw out…
  20. 20. simple tools answering complex questions
  21. 21. the lesson of February 2005
  22. 22. where to start?
  23. 23. GeoWeb
  24. 24. address spatial business problems in a browser
  25. 25. publish &consume services
  26. 26. but…
  27. 27. to be successful…
  28. 28. we must understand…
  29. 29. trumps features usability
  30. 30. we must master…
  31. 31. Atom WFS .NETXHTML CSS Ajax TDD Javascript RSS JSON REST XML GeoRSS WMS
  32. 32. more to learn
  33. 33. 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
  34. 34. more tools
  35. 35. we must understand…
  36. 36. what users want
  37. 37. users want
  38. 38. how do we tackle this?
  39. 39. design ideas
  40. 40. examples please!
  41. 41. 1 Road Project Management Internal workflow application SAP integration OpenLayers + WMS + Dojo ArcGIS Server 9.2
  42. 42. 2 Emergency Response workflow application multi-service “mash-up” ESRI JS API + Dojo ArcGIS Server 9.3 REST
  43. 43. 3 avian influenza tracking system public facing focused search tools virtual earth + dojo ArcGIS Server 9.2 + Custom Tile Server
  44. 44. interface design
  45. 45. fewer layers
  46. 46. Cram desktop into A browser
  47. 47. Screen shot of CDOT
  48. 48. provide feedback!
  49. 49. what should I do?
  50. 50. handle the “null-case”
  51. 51. make it fast!
  52. 52. SAP Get Project List
  53. 53. hold their hand
  54. 54. hide the details language matters
  55. 55. Locate structures near my project.
  56. 56. really means…
  57. 57. generic tool could work…
  58. 58. for technologists
  59. 59. reassure the user.
  60. 60. validate as soon as possible
  61. 61. SAP Ref Selection
  62. 62. pre-validate whenever possible
  63. 63. protect users from themselves
  64. 64. whew!
  65. 65. system design
  66. 66. project process
  67. 67. low value
  68. 68. just-enough design
  69. 69. map the workflow
  70. 70. iterate on paper
  71. 71. • Create wireframes
  72. 72. choose a map canvas
  73. 73. keep it simple
  74. 74. define services
  75. 75. REST API
  76. 76. custom services
  77. 77. not available
  78. 78. possible but not optimal
  79. 79. “chatty”
  80. 80. faster
  81. 81. details please!
  82. 82. 1 use the SOAP API
  83. 83. ArcGIS Server Web Server ASP.NET MVC App SOAP SOC Process AGS SOAP API Controller IIS JSON
  84. 84. 2 COM utilities & server object extensions
  85. 85. IIS ASP.NET MVC App Controller JSON Web Server SOAP Web Service ADF Connection COM Utility SOC Process ArcGIS Server
  86. 86. can we code now?
  87. 87. start coding!
  88. 88. match the model
  89. 89. MARC SCREENS
  90. 90. release early
  91. 91. release often
  92. 92. listen feedback
  93. 93. Summary:
  94. 94. expectations: changed
  95. 95. kung-fu: needed
  96. 96. design: workflow
  97. 97. focus: usability
  98. 98. performance: critical
  99. 99. details: hidden
  100. 100. Dave Bouwman dbouwman@dtsagile.com http://blog.davebouwman.net http://twitter.com/dbouwman
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×