1 / 21

Google Maps Representation of Geo-Scientific Data

Overview. IntroductionThe Mapping APIJDBCWeb ServiceResultsFuture Work. Introduction. Aim of the project is to create an API between GoogleMaps and a database of Geo-scientific data.Enable scientists to visualize the content of the database on an online mapping system.Java-based system gener

maura
Download Presentation

Google Maps Representation of Geo-Scientific Data

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. Google Maps Representation of Geo-Scientific Data Team Members: Jing Huang Neha Majithia Samar Bajaj Sudeep Singla Team Advisor: Rami Al Ghanmi

    2. Overview Introduction The Mapping API JDBC Web Service Results Future Work

    3. Introduction Aim of the project is to create an API between GoogleMaps and a database of Geo-scientific data. Enable scientists to visualize the content of the database on an online mapping system. Java-based system generates Keyhole Markup Language (KML) versions of the database content to facilitate use of Google Maps and Google Earth. Develop a web service that accepts requests and plots results on the requested map.

    4. Why do we need an interface between Google Maps and Geo-scientific data? Convenient representation of fault data for ease in identifying fault areas in particular locations. Representation of co-ordinates as markers and fault zones and data related to the fault in a graphical way. Ease in locating fault areas and querying the earthquake fault database. Can be used for live GPS feed and current information on fault stability. Could be used for prompt response to earthquakes and fault locating in inhabited areas.

    5. Sample Fault Data

    6. Diagrammatic Representation

    7. The Mapping API The back-end supporting all these interfaces will be the same. The outcome of this API is a set of faults and/or points of interest displayed as lines (or a connection of line segments) on a Google Maps/ Google Earth map. The API provides the features of including metadata about the fault, links to live GPS readings, current information regarding the stability of the fault. The entire API is developed in Java.

    8. JDBC JDBC consists of two parts: JDBC API, a purely Java-based API JDBC Driver Manager,which communicates with vendor-specific drivers that perform the real communication with the database. Point: translation to vendor format is performed on the client No changes needed to server Driver (translator) needed on client

    9. Java API with JDBC We are using MySQL for the database and the querying, as we were not provided the actual database we used sample fault data. We use JSP to connect with MySQL database. We use the TomCat server. The JSP file uses JDBC for connectivity with the database. It queries the database and we get the result from the database. The API then generates the KML file which is given to Google Maps to display fault data.

    10. Sample KML file for displaying markers on Google Maps <?xml version="1.0" encoding="UTF-8"?> <kml xmlns="http://earth.google.com/kml/2.0"> <Document> <name>KML Example file</name> <description>Simple markers</description> <Placemark> <name>Marker 1</name> <description>Some stuff to put in the first info window</description> <Point> <coordinates>-122.1,37.4,0</coordinates> </Point> </Placemark> <Placemark> <name>Marker 2</name> <description>Some stuff to put in the second info window</description> <Point> <coordinates>-122.0,37.4,0</coordinates> </Point> </Placemark> </Document> </kml>

    12. Web Services

    15. Web Services We are using the Tomcat server, MySQL for the database and Axis in Tomcat webapps. The MySQL JDBC jar file is copied into Tomcat along with all the API Java files for XML . We wrote a java servlet to get data from MySQL and generate a KML file with the results of the query. The web service is then deployed in the system. To access the web services we can use a web service client so that it can be accessed from any system, messages are exchanged in XML format, the client will convert the XML file to KML format and give it to Google maps to display.

    18. Results

    19. A Java API was created which provides the user representation of geo-scientific information on Google Maps & Google Earth. The user to this API has the choice to use one of two interfaces: JDBC Interface Web Service Although these interfaces are a lot diverse, the back-end supporting them is the same. The outcome of this API is a set of faults and/or points of interest displayed as lines (or connection of line segments) on a Google Maps/Google Earth map. The API provides the feature of including meta data about a fault or any displayed location on the map. There is no predefined set of the meta data. Such data appears in the information window (a.k.a bubble) when a marker is clicked on the map. Different faults and zones are displayed in different colors.

    20. Future Work Other interfaces can be made to provide a greater diversity to the user. e.g. CLI. The database used currently is only a sample database, an actual Geo-scientific fault database should be interfaced to provide actual factual information about the faults and earthquake zones.

    21. Thank You

More Related