Geospatial queries

After working on the decoding of the GLDAS files, our next step is in optimizing the geospatial queries  for the project. On one hand we need to have the right UI controls as part of the map interfaces. And on the backend, we need to have the ability to do the bounding box queries needed for the different resolutions.

The first part we have it under control. We are able to detect the zooming behavior in Google Maps API as part of the javascript code.

For the latter part we are going to be using Geomodel a nice open source project to do the geospatial work.

Validating our data points

Happy new year 2013!

During the weeks of the holiday we were validating the data points extracted from the GRIB files.

Giuseppe and Mario took the average temperature for the month of June and compared against the city where they live. In order to do that, they found out the latitude and longitude of the city and looked it up in the excel. Thus far the temperatures make sense.

In the meantime Jyothi has been looking at mastering the Google Maps API event handlers fro zooming in and zooming out of the maps. This will help us reload the Heatmap layer with different resolutions depending on the zooming behavior. The idea is to have a set of data points with different resolutions.