Defining our first map

It is one of the main objectives of the project is to find the visualizing tools to facilitate the general public to process data from climate data sources. Our first business case is to display surface temperature. As we investigate this week and next, we are coming close to define the User Interface (UI) as the combination of two maps.

A definite example to follow is this map of the boss. as it shows the concerts of Bruce in the US. We plan to use the HeatMap layer as part of the Google Maps API for styled maps.

Another example that complements our effort is vote night. Which shows a combination of user control with charts displays. We want the map to be the UI!

As Giuseppe said this week in finalizing the details of the business case,

This visualization can be used to show the variability in time of T in an area that the user can select. We should think about what is the best variable to show. Temperature varies within each day; thus, we may show the animation of monthly mean (or minimum or maximum) temperature for the all set of years.
And we may create some flash marker that appears when we reach, for example, the maximum (and/or the minimum) temperature ever in that area. After appeared, the marker will remain in the area with the data shown until the animation ends. We may have a few markers with different spatial information on the records of data we have shown.

On another note, Sri is working in setting his workarea with the svn repo and the app engine project ready to go. He will be installing Eclipse with all the support tools for Django and python. 

The Beginning

This is our first post in the blog. We'll provide with the latest update on the project that is a finalist of the Google App Engine Research Award.

After Enrique workout the details and redtape behind accepting the award, we are currently on the requirement definition and functional specification for the project.