Your SlideShare is downloading. ×
Smallworld and Google: the best of both worlds
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Smallworld and Google: the best of both worlds

1,624

Published on

My presentation at the Smallworld User Conference in Baltimore, talking about the benefits of combining the strengths of Smallworld and Google Maps (the work we are doing with Ubisense myWorld).

My presentation at the Smallworld User Conference in Baltimore, talking about the benefits of combining the strengths of Smallworld and Google Maps (the work we are doing with Ubisense myWorld).

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,624
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
60
Comments
0
Likes
1
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
  • This is a typical utility basemap in Smallworld – fairly sparse. But you can see with the raster tiled approach that the data looks exactly like it does in Smallworld
  • Adding in a Google Street Map gives a lot more context. Maintaining base maps is not a core activity for utilities, and is very expensive. It really makes sense to use basemaps maintained by somebody else. There are ways that you can add updates where necessary, for example adding a new subdivision which isn’t on the basemap yet.
  • And Google satellite imagery is good for many applications. I hear a lot of people say that Google imagery is out of date but I think they are updating it more and more frequently.
  • What if your data doesn’t match the Google landbase? Many utilities have an old and inaccurate landbase and want to transform or conflate their network data to a new and more accurate landbase, for multiple reasons – sharing data with other entities, using GPS, and working with external data like Google Maps, or imagery from other sources. This is an example of some data from PNG, who went through such a conflation exercise. You can see here how much better their pipes align with a Google map background after the conflation progress. That’s not the main focus of my talk today, but
  • Google street view can give you valuable extra information about facilities. Often you can see details on pole configuration and so on that may not be stored in the database. We’ve integrated tightly with this, so that when you click on a facility you automatically get the right street view displayed. In cases where the data doesn’t line up exactly it’s easy to adjust the view and save that for next time.
  • A very powerful feature is that you can display icons in the street view itself and mouse over or click them for more information.
  • In this example we can see several poles further away as we look along the street.
  • You need a wireless connection in general … but this massively reduces admin. No need to sync, no need to install software on any devices, no need to upgrade, no need to do anything when you change your data model. If you have foreign crews, they just need any device with a web browser and some login information.
  • Another thing we can make far more use of in mobile applications is georeferenced photos. These pictures were taken with my iPhone, the location was automatically recorded by the built in GPS, and the pictures were uploaded wirelessly by email and appeared on the map automatically like this – I have not adjusted anything manually.
  • These type of photos can be displayed on the map in near real time, and have huge potential for damage assessment after storms … just get members of the public to email pictures from their smart phones (in addition to your crews), and you have a really powerful crowdsourced solution, that can give you a much better near real time view of the situation than you have today.
  • Mention example of field systems – how are these currently secured?Growth in customer web portals – need to work out internet securityMore complex network security challenges in smart grid
  • The back button is the most used feature of web browsers
  • Mention change from enterprise driven innovation to consumer driven innovation
  • Transcript

    • 1. Smallworld and GoogleThe best of both worlds
      Peter Batty
      September 10, 2010Smallworld User Conference, Baltimore
    • 2. 1: The Revolution
    • 3. 2: Different Approaches
      flic.kr/p/pWMRk
    • 4. 3: The Cloud
      flic.kr/p/7Bzn5E
    • 5. 4: Usability
      flic.kr/p/kjwKm
    • 6. The Revolution
    • 7. GIS has been a specialized backroom technology for many years
    • 8.
    • 9. flic.kr/p/7A6vVg
    • 10. flic.kr/p/7NEJzF
      Location is now
      Pervasive and Simple
      in consumer applications
      flic.kr/p/7rnNAD
    • 11. Disruptive technology
      Functionality /
      performance
      Established technology
      Mainstream
      Market
      requirements
      Disruptive technology
      Time
    • 12.
    • 13. flic.kr/p/7UjM5T
    • 14. flic.kr/p/4UoT3s
    • 15. Ease of use
    • 16. Access to data: imagery
    • 17. Access to data: street view
    • 18. Access to data: geocoding & local search
    • 19. Directions
    • 20. Live or predicted traffic data
    • 21. Ease of scaling and administration
    • 22. Different Approaches
      to Google integration
      flic.kr/p/pWMRk
    • 23. Sparse data
      Sparse data
      Trucks
      Outages
      Jobs
      Often don’t need GIS maps
      KML and GeoRSS are good formats
    • 24. KML
      is child’s play!
      <?xml version="1.0" encoding="UTF-8"?>
      <kmlxmlns="http://www.opengis.net/kml/2.2">
      <Placemark>
      <name>Simple placemark</name>
      <description>Attached to the ground. Intelligently places itself
      at the height of the underlying terrain.</description>
      <Point>
      <coordinates>-122.0822035425683,37.42228990140251,0</coordinates>
      </Point>
      </Placemark>
      </kml>
    • 25. So is
      geoRSS
      <entry>
      <title>M 3.2, Mona Passage</title>
      <link href="http://example.org/2005/09/09/atom01"/>
      <id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
      <updated>2005-08-17T07:02:32Z</updated>
      <summary>We just had a big one.</summary>
      <georss:point>45.256 -71.92</georss:point>
      </entry>
    • 26. Marketing application
      KML viewable in Google Earth or Maps on multiple devices including iPhone etc
    • 27. You can use KML in lots of places
      KML uploaded to GeoCommons and used for thematic mapping
    • 28. KML
      flic.kr/p/8eZBZk
      The Good
      Simple
      Good for sparse and dynamic data
      Works with multiple platforms / products
    • 29. KML
      The Bad
      Hard to match Smallworld styles
      Hard to scale to large data volumes
      flic.kr/p/6hwSwn
    • 30. Dense Data
    • 31. Raster map tiles
      Pre-render maps into image files
      Approach used by Google, Microsoft, etc
      Very high performance and scalability
      Easy to integrate with Google Maps etc
    • 32. Tile data volumes (global)
      Calculations by Charlie Savage
    • 33. System Architecture
      Overall
      sync
      Other enterprise systems
      Web mapping server(s)
      Google/Bing servers
      Smallworld
      OMS, WMS, CIS …
      Streetview, geocoding
      Spatial database
      Raster map tiles
      Base maps, imagery
      GSS
      REST, GeoRSS, …
      End user
      Any web browser
      Desktop or mobile
      Easy to use
      High performance and scalability
    • 34. Google strengths
      Smallworld GSS
      strengths
      Simple viewing and query
      Rich data
      Additional functionality:
      geocoding, routing
      Simple “data mashups”
      Rich functionality
      Leverage existing applications
      Business process integration
      Network tracing
      Data update
      Highly complementary!
    • 35.
    • 36. Matches Smallworld styles
    • 37. Google basemap gives context
    • 38. Google satellite map
    • 39. What if my data doesn’t match?
    • 40. Street View gives extra info
    • 41. Street View gives extra info
    • 42. Street View gives extra info
    • 43. Google style one box search
      Something on “Google style search”
    • 44. Autocomplete search
    • 45. Autocomplete search
    • 46. Reports in search too
    • 47. Reports from search
    • 48. Reports from search
    • 49. Google geocoding very flexible
    • 50. Google local search
    • 51. “Enterprise mashups”
      Outages
      Trucks
      WMS
      CIS
      Smart Grid
    • 52. Ability to link to maps
    • 53. Click link, no software needed!
    • 54. Google Maps is mobile too!
      … and tablets including iPad
      Runs on smart phones including iPhone…
    • 55. Geo-referenced photos
    • 56. Damage assessment
    • 57. …/a2e/data/datasources/Pole/90974
      REST APIs
    • 58. …/a2e/data/datasources/Pole/90974?f=gjson
      REST APIs: simple and powerful
    • 59. …/a2e/data/datasources//Pole/search?f=gjson
      &lat=42.600&lon=-76.1780&d=4
    • 60.
    • 61.
    • 62.
    • 63.
    • 64.
    • 65. REST is good!!
      Jason Birch
      <Picture of Jason>
      City of Nanaimo
    • 66. Running in the
      Cloud
      flic.kr/p/7Bzn5E
    • 67. This is an old Google data center (2005)
      Each container holds
      servers
      1,160
      This facility holds an estimated
      150,000
      servers
    • 68. 40
      Google has an estimated
      data centers…
      1 million
      …holding an estimated
      servers
    • 69. 3 billion
      35,000
      searches per day
      searches per second
    • 70. 2 billion
      videos per day
    • 71. 100 million
      monthly users
    • 72. one zillion times more computer science PhDs than your company or mine has
    • 73. HUGE
      economies of scale
      Google
      Amazon
      Your IT department
    • 74. Save BIG!!
      flic.kr/p/64kFKH
    • 75. EC2 Pricing
      September 5, 2010
    • 76. My daily quotas (max $5 per day)
      46.5 CPU hours
      6.5 CPU hours free
      43.2m web requests!
    • 77. My total server costs for development of myWorld so far
      13c
    • 78. flic.kr/p/4iCux7
      but is it SECURE???
    • 79. $24.5bn
      2009 revenue
    • 80. 4th
      fastest growing
      company in Fortune top 100, 2010
    • 81. 170 million users, Feb 2010
    • 82. “Government’s record year of data loss”
      Daily Telegraph, UK, 2008
      The biggest single loss was in November when Alistair Darling, the Chancellor, revealed two CDs with personal details of 25 million child benefit claimants and their parents had gone missing in the post.
      Last February it emerged 80 passports are lost in the post every month.
      Last month, CDs with personal information on thousands of benefit claimants were found at the home of a former contractor to the Department of Work and Pensions.
      Three weeks ago Ruth Kelly, the Transport Secretary, admitted that the details of three million learner drivers had gone missing when a hard drive was lost in Iowa.
      http://bit.ly/c1ry5s
    • 83. There is a strong case that
      your data
      is
      more secure
      in the cloud
    • 84. Agility
      Google Maps had 400 releases in its first 4 years
      flic.kr/p/7BM8zr
    • 85. Cloud benefits
      Ultra scalable
      Secure
      Major cost savings
      Hardware, admin, upgrades
      Much faster enhancements & fixes
      flic.kr/p/7Bzn5E
    • 86. Usability
      flic.kr/p/kjwKm
    • 87. I highly recommend this book
    • 88. My top 3 rules for good usability
      1
      Do usability testing
      2
      Do usability testing
      3
      Do usability testing
    • 89. Doing a usability test
      Put application in front of user
      Shut up
      Watch
      flic.kr/p/72M6L
      flic.kr/p/53WUkg
      flic.kr/p/7UqPo1
    • 90.
    • 91.
    • 92. We don’t read web pages, we skim them
      flic.kr/p/6Ab8j
    • 93. We don’t evaluate all the options, we pick the first plausible one
    • 94. What the designer sees
    • 95. What the user sees
    • 96. What the user sees
    • 97. What the user sees
    • 98. We usually just see a fraction of what is on the page
    • 99. Use conventions
    • 100. Omit needless words
      Get rid of half the words on each page,
      then get rid of half of what’s left
      Krug’s third law of usability
    • 101. Don’t make me think
      Krug’s first law of usability
      flic.kr/p/28o3cz
    • 102. Summary
    • 103. Fast train?
      flic.kr/p/7b5sKd
    • 104. Usability / simplicity
      flic.kr/p/3guaAu
    • 105. Cloud
      flic.kr/p/6aJDqo
    • 106. ?
      peter.batty@ubisense.net
      geothought.blogspot.com
      twitter.com/pmbatty

    ×