Day 197 to 207 – Fri 28th March to Sun 6th April 2014

During this time, I managed to complete the charts I set out to do in my last post. I have also managed to implement responsive web design, so that the website can be viewed well on devices with varying sizes. Some screenshots demonstrating this are below:

320 x 480 responsive demo

480 x 320 responsive demo

600 x 800 responsive demo

800 x 600 responsive demo

768 x 1024 responsive demo

1024 x 768 responsive demo

After implementing the responsive web design/development, my attention then turned to more robust error checking for the chart forms. After testing on the local server, I came across numerous exceptions that I should have caught. I then looked at the class code responsible for the errors and refactored accordingly – before, that chart automatically was created on class creation, but I knew this was a bad idea so I corrected it. Below are screenshots showing examples of errors – the form input before the error, and the error message displayed afterwards:

Half hourly energy usage, on a given date

Before error:

Half hourly use before error demo

After error:

Half hourly use after error demo

Energy usage between two times, on a given date:

Before error:

Usage between times on day - before error demo

After error:

Energy usage between two times on day - after error demo

After I had done this, I started looking at how census data can somehow be integrated into the project – in other words, how I could map population data to areas that have data recorded. Through Sam’s wise words, I had a look at some census data and seen that I am more than capable of storing the data required (and coming up with necessary algorithms necessary for calculations). The data involves series or area units (townships, suburbs) which link to meshblocks (streets/zones). If I can get an index of streets from each access point area (from Delta), I can link these to the meshblocks – and then link meshblocks to the access point areas. With that, it will be more possible to map suburb areas (like the current access point areas, but mapping the suburb areas more recognizable to people). Below is an initial update to my current database model, which will be able to store this data:

Updated database model - 6th April 2014

After posting some recent updates for the energy meter website, Sam Mann mentioned he would like to see the numbers ‘constantly’ changing. One idea I had was to calculate the difference between the ‘current’ and previous reading, add it to the overall average, divide that in half, divide it by a further 1800 (the amount of seconds in a half-hour period), and add it to the ‘current’ total every second. This would require another function in the code, but will be no problem. I’ll be spending some time testing it to see if the numbers are realistic, and see what happens each half-hour period (will the accumulated readings every second be in line with the reading on the half-hour mark).

To do – day 208 to 215 (7th to 14th April 2014)

  • Request meeting with client, EnviroSchools on key messages to communicate
  • Discuss competition in schools idea (in same meeting)
  • Implement database tables as in updated model
  • Follow up on street name index for access point areas, from Delta
  • Start constructing charts for ‘real-time’ data (e.g. data sourced every half hour)
  • Create charts to compare access point data with areas (users picking up to 3 areas)
  • Create user testing instructions (by 13th April at very latest)
Scan to Donate Bitcoin
Like this? Donate Bitcoin to at:
Bitcoin 13vYNWKj3npQTYr7EJVBhcoVkwncEbDUvJ
Donate

Share