Your SlideShare is downloading. ×
Why your users want Google Maps, not your GIS ... And what to do about it!
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Why your users want Google Maps, not your GIS ... And what to do about it!

1,106
views

Published on

Google Maps is a hugely successful product. Initial popularity due to great speed, cartography, and user interface design grew to near dominance of online mapping when routing and Street View were …

Google Maps is a hugely successful product. Initial popularity due to great speed, cartography, and user interface design grew to near dominance of online mapping when routing and Street View were added. Once GIS users realized there was a better way to access spatial data and functionality, they quickly became dissatisfied with traditional GIS. But GIS is much more than what Google Maps provides ... Paul Joyce of we-do-IT addresses the issue of Why your users want Google Maps, not your GIS ... And what to do about it!
Paul has worked extensively with Smallworld, ESRI and Intergraph GIS systems. A recent project of his involved establishing an enterprise-wide adoption of GIS technology, using a combination of consumer-targeted (Google Earth, Google Maps), and open source server technologies (GeoServer, PostgreSQL).

youTube ...
Pt One: http://www.youtube.com/watch?v=yT3-3aMX44o
Pt Two: http://www.youtube.com/watch?v=tJSpDbi12zQ
Pt Three: http://www.youtube.com/watch?v=ImBywcXTH0c

http://www.gita.org.au
http://www.we-do-IT.com

Published in: Technology

1 Comment
0 Likes
Statistics
Notes
  • I already use Google Maps as GIS to build road maps (graph structures). The problem I stumble upon is collaboration. Specifically, collaboration in building datasets -- not using them. Majority of GIS portals I know are there for 2 purposes:

    (1) to use a GIS dataset together
    (2) to build a dataset based on the interface provided by the portal.

    The simple purpose I am trying to pursue is left unfulfilled by both the above. Which is actually strange because quotas on requests exist for any existing API -- GoogleMapsAPI or ArcGIS, although it could be in slightly varied forms -- ArcGIS is paid from the start and has rather big quotas while GoogleMapsAPI has very restrictive quotas in its free form.

    For example:

    http://t.co/3SmOedz2l0

    is a simple serverless web application which uses client's daily quota to suck routes from GoogleMapsAPI and stored them in my Dropbox folder. All clients write to the same folder. Collisions are resolved by the web application. This is a very simple collaboration.

    Note that its purpose is different from that of default modes of ArcGIS or GoogleMaps (API or Engine) and cannot be created by the either of them. I am surprised to find myself in the position that public collaboration on a (useful?) dataset is completely impossible just because it departs -- a little bit -- from the default use.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total Views
1,106
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
1
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. GITA gisDrinks
    Why your users want Google Maps, not your GIS ... and what you can do about it
  • 2. Comparing Google Maps with Others
    Cartography
    Speed
    User Interface
    Functionality
  • 3. Cartography – Typical GIS
  • 4. Cartography – Yahoo Maps
  • 5. Cartography – Bing Maps
  • 6. Cartography – Google Maps
  • 7. Cartography
    41latitude.com
    Label readability
    Number of labels
    Label placement
    Town icons
    ... more
  • 8. Speed
    No waiting 5-15 seconds for a redraw
    No refresh button
    Google’s infrastructure > your IT department’s
  • 9. UI – SIAS
  • 10. UI – G/NetViewer
  • 11. UI – G/MobileViewer
  • 12. UI – ArcGIS Explorer Online (ribbon)
  • 13. UI – ArcGIS Explorer Online (new)
  • 14. UI – ArcGIS Viewer for Flex
  • 15. UI – ArcGIS.com Viewer
  • 16. UI – Bing Maps
  • 17. UI – Google Maps
  • 18. Functionality
    What your GIS looks like to most of your users
  • 19. Functionality
    Less is more
    Web GIS ≠ Desktop GIS
    Web GIS = Workflow support server-based geoprocessing
  • 20. Good Reasons To Surrender
    >150 million users
    >19 billion km of routes served last year
    Cartography, Speed, UI
    Street View
    API
    Hundreds of updates per year
    training, implementation, licence costs ↓
    productivity, scalability ↑
  • 21. When
    Internet and users that only need location are candidates for a Google Maps-based solution
  • 22. How
    Google Maps + placemarkers
    Google Fusion Tables
    Google Maps API + custom/product
  • 23. If You Can’t Or Don’t Want To
    Just support workflows
    Pay attention to user experience
    cartography: basemap + operational, imagery
    speed: maps, geoprocessing
    ui: simple, clean, workflow support
  • 24. Thanks