You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Project Goal

To develop an API which will convert the perfSONAR NMWG format into a format which is recognizable by  a  visualization tool such as  ( Google Maps or Yahoo Maps)  and vice versa. The conversion from NMWG format to Visualization recognizable format is needed to visually display that data and the conversion of the visualization recognizable format to NMWG is needed to conduct test on the fly and get its results.  It will use the web services of  PerfSONAR's Look up Service and PerfSONAR's Measurement  Archive in order to fetch the data. It is not clear at this specific time which language to use. I will prefer to use JSP . We will consider some other alternatives as well.

Visualization Features Required

  •  Icons ( Display Measurement Points on a World Map)
  •  Lines / Arrows (Display Links between sites  / Color, thickness may represent the quality)
  •  Chart / Graphs (To present a time Series description of a particular Network Metric)

Comparison of Google Maps vs Yahoo Maps 

 Google Maps 

  Google Maps now  supports KML (KeyHole Markup Language) essentially XML, which was previously only supported by . The KML file has to be uploaded to a web server and then the URL has to be provided to Google Maps in order to display it. (Also this support for KML is provided by 3rd party not google ). So the problem with using KML is that URL of the form http://maps.google.com/maps?f=q&hl=en&q=http://www.slac.stanford.edu/comp/net/wan-mon/viper/l.kml&layer=&ie=UTF8&z=17&om=1 will be displayed to the user.

Pros:

  • Fluid interface, brilliant looking map marker flyouts
  • Largest developer base
  • Lots of hacks and how-to's available
  • Supports KML which is essentially XML.

Cons:

  • Lack of support for Geo Coding Service (which we do not need any way)  

Yahoo Maps

Pros

  • Very flexible and open API's.
  • Flash Version available.
  • Easy to implement.
    Cons: 
  •  API is not as powerful and flexible as Google Maps.

Examples of Google Maps Features

  The fallowing sample KML  will display a place marker at the latitude and longitude supplied to it

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://earth.google.com/kml/2.1">
  <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>

http://maps.google.com/maps?f=q&hl=en&q=http://www.slac.stanford.edu/comp/net/wan-mon/viper/l.kml&layer=&ie=UTF8&z=17&om=1

  JFreeChart or any other graphing API can be used to display Router Utilization Graphs. The Graphs can be saved as images and then there URL can be provided to the CallOut to display the graph. Here is a sample code

<?xml version="1.0" encoding="UTF-8"?><kml xmlns="http://earth.google.com/kml/2.1">
<Document>
<Placemark>
<name>CDATA example</name>
<description>
<\!\[CDATA\[
 <h1>Network Utilization Graphs</h1>
 <img src="http://www.slac.stanford.edu/comp/net/wan-mon/viper/graph.png"></img>
 \]\]>
 </description>
 <Point>
 <coordinates>102.595626,14.996729</coordinates>
 </Point>
 </Placemark>
 </Document>
</kml>

http://maps.google.com/maps?f=q&hl=en&q=http://www.slac.stanford.edu/comp/net/wan-mon/viper/fourth.kml&layer=&ie=UTF8&z=3&ll=52.05249,98.4375&spn=81.078359,163.476563&om=1&iwloc=A

 \
 
 

  • No labels