1 / 54

The Case for 3D Singapore

The Case for 3D Singapore. Terence Tan Infocomm Development Authority of Singapore. Spatial Cloud Computing on AppEngine. Desktop GIS, Web GIS, is Cloud the next Step?. Prabuddha Ghosh 20 th Jan 2011 GeoSpatialWorld2011 Developers Forum. Timeline of GIS Platforms. Outline.

jwheeler
Télécharger la présentation

The Case for 3D Singapore

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Case for 3D Singapore Terence Tan Infocomm Development Authority of Singapore

  2. Spatial Cloud Computing on AppEngine Desktop GIS, Web GIS, is Cloud the next Step? Prabuddha Ghosh 20th Jan 2011 GeoSpatialWorld2011 Developers Forum

  3. Timeline of GIS Platforms

  4. Outline The What and Why of Spacial Cloud Computing (SC2) Challenges and solutions of SC2 on AppEngine CloudGIS

  5. What is the Cloud? NIST Definition : http://csrc.nist.gov/groups/SNS/cloud-computing/index.html • 5 Characteristics of Cloud Computing • 3 Service Models • 4 Deployment Models

  6. Cloud Characteristics • On-demand self-service • Broad network access • Resource pooling • Rapid elasticity • Measured Service

  7. Cloud Service Models • Cloud Software as a Service (SaaS). • Cloud Platform as a Service (PaaS). • Cloud Infrastructure as a Service (IaaS).

  8. Cloud Deployment Models • Private cloud. • Community cloud. • Public cloud. • Hybrid cloud.

  9. Comparing Cloud & Data Centers (Source Communications of the ACM)

  10. What is Spatial Cloud Computing SC2? • Cloud Computing with Geography added • 90% of business data has a Geographical component

  11. Why SC2 for Clients • On Demand Scalability • Low upfront Cost • No IT costs • High security • Latest software • Opex instead of Capex

  12. Why SC2 for IGSV • Sell to new categories of customers • Concentrate on core competency • Monthly revenues • Fast to market • Support massive scaling with low upfront cost

  13. Costs

  14. Growth of Cloud Computing

  15. How to do SC2 ? Challenges and Solutions of SC2 on AppEngine

  16. Technology Stack Used

  17. What is Appengine? • Google Cloud Platform • Python & Java • Self Service Administration • Integration with Google APIs (GALGWT)

  18. AppEngine Architecture

  19. Dashboard

  20. What is the DataStore • Not an RDBMS. • Scalable • NoSQL based pseudo HashMap • JDO/JPA support

  21. DataStore Viewer

  22. Other Supporting components • GWT • GALGWT ( maps, charts, reports) http://code.google.com/p/gwt-google-apis/ • JavaApiForKML http://code.google.com/p/javaapiforkml/ • Apache Commons FileUploading etc • JTS (For spatial analysis) • Any Other Java component on whitelist http://code.google.com/appengine/docs/java/jrewhitelist.html

  23. Structure of an Appengine Application • UI- GWT/GXT/SmartGWT (Flex is an option) /Client Directory • Middleware (Java based POJOs) /server directory • Database – Google Bigtable based Datastore • .gwt.xml file Module descriptor • Web.xml, appengine-generated.xml , datastore-indexes.xml, local_db.bin • Main html Page

  24. Tools for working with AppEngine • Google plug-in for Eclipse • AppEngine Datastore • Appspot • SVN/ Subclipse/ Googlecode • Appcfg.sh+ Ant • Local Admin (ah_admin)

  25. Major Challenges • Appengine DataStore does not have Spatial Indexing • Loading Data to Appstore from any machine in the world as Java Appengine does not have good bulk upload tools • Supporting GIS functionalities without reinventing the wheel

  26. Solutions • We can use JavaGeoModel an existing open source project which supports creation of spatial indexes using Geohashing feature. • Use Apache Commons Framework and JavaAPIforKML for handling the data upload task • Use Java Topology Suite for GIS processing

  27. What is Geohashing?

  28. Store GeoHash in Datastore

  29. CloudGIS POC RMSI in the Cloud

  30. Where we are? • POC created on Google Appengine platform • Work started for a telecom sector client using this platform

  31. Functionalities available now • Can load KML data to Appengine from any computer • Can do proximity searches using the DataStore Geohashes • Display the same using Google Maps and make available Google Maps Based Tools • Can do Attribute Based Search, LatLong Search, Geocoded Search, Administrative Boundary Based Drill Down Search.

  32. Screenshots/Demo

  33. Screenshots/Demo

  34. Screenshots/Demo

  35. Screenshots/Demo

  36. Screenshots/Demo

  37. Screenshots/Demo

  38. Screenshots/Demo

  39. Screenshots/Demo

  40. Screenshots/Demo

  41. Screenshots/Demo

  42. Screenshots/Demo

  43. Screenshots/Demo

  44. Screenshots/Demo

  45. Screenshots/Demo

  46. Future Work • Support formats besides KML • Integrate Administration with AppEngine Admin Panel • Create Pay as you go Billing (using AppEngines existing billing engine) • Expose more JTS functionalities • Utilize TaskQueues for running background reports • Port to VMForce when VMForce is in General Availability (port to Spring in preparation) • Support user created data

  47. Adding Data via user clicks

  48. In Conclusion • We saw what is SC2 and why it makes sense • We talked about AppEngine and how to use AppEngine for a SC2 implementation • And we had a look at an implementation of an SC2 application for Tower Location Planning

  49. Something to Think About • Cloud Computing in India to grow from a from a $50 million industry in 2009 to a $15 billion industry by 2013. (Source Communications of the ACM). How much will be Cloud GIS??

  50. Thank You!! Questions?

More Related