Difference between revisions of "Group11 proposal V2"

From Visual Analytics for Business Intelligence
Jump to navigation Jump to search
Line 170: Line 170:
 
|
 
|
 
<center></br> '''Dashboard 2: '''</br>
 
<center></br> '''Dashboard 2: '''</br>
[[File:Sketch3.jpg|600px|frameless|center]]
+
 
 
</br>
 
</br>
 
</center>
 
</center>

Revision as of 14:18, 27 March 2020

WeHouse Logo.png

Proposal

 

Poster

 

Application

 

Research Paper

 

Roles


Version 1

 

Version 2


Problem

Cheatsheet.jpg

The above is an example of information online in helping Singaporeans decide the type of house they could choose from. In the context of this project, Resale HDBs is the focal point of our project. Choosing a resale HDB has never been easy as there are many factors to consider such as location, HDB type, number of remaining lease years, resale value, etc. On top of that, thousands of Resale HDBs transactions are happening each month, making it almost impossible for an owner to get a view of every transaction. Therefore, the majority of buyers and/or sellers have to consult property agents for their services.

However, there are times where the service of a property agent may not be satisfactory to the buyer and/or seller. It is still advisable for the buyer and/or seller to have a better understanding of the resale market before making an informed decision. In most cases, people tend to rely on multiple platforms to help them in understanding and predicting the market trend. On that note, our team would like to know whether the information provided to them is truly insightful or usable. Thus, WeHouse comes into play to provide greater insights for people to better understand the HDB resale market which can provide better aid in making more informed decisions.

Motivation

Given the abundance of information available on the internet in terms of resale prices, there are online resources provided to map out HDB locations and prices. However, such visualisations tend to be overwhelming due to vast data and non-specialised focus on visualisations. Throughout the course, we have learned how to discern between a good and bad visualised graph. This has allowed us to decide the usefulness of the charts displayed on various platforms. Therefore, instead of leaving people unsettled about the kind of housing choice to make, we are here to aid with our proposed visualisations! Coupled with the hands-on in-class sessions, we are able to reinforce what we learnt to play and explore re-organisation of the data to present an interactive dashboard, specifically pertaining to HDB dwellings, to empower users to make better-informed choices of their HDB location.

Objectives

In this project, we aim to deliver a focused and compact visualisation to allow Singaporeans to be well-informed of the average HDBs resale prices around their desired location.

  1. Overall changes in the flat prices over time for each subzone by estates.
  2. Price differences for each estate and subzone depending on the remaining lease of the flat.
  3. Find out which month sells at the highest and lowest resale price and transactions
  4. Specifically identify the most expensive street within each town area

Data Set(s) Used

Background Survey


Example Takeaways



  • New Insights / Comparisons and what to do better



  • New Insights / Comparisons and what to do better



  • New Insights / Comparisons and what to do better



  • New Insights / Comparisons and what to do better

List of References

Proposed Storyboard


Dashboards Rationale

Dashboard 1:


  • New Dashboard

Dashboard 2:


  • New Dashboard

Dashboard 3:
Reference.gif


  • New Dashboard

Technologies Used

Our Current Timeline

Key Technical Challenges

Challenges Actions Taken

Unfamiliarity with R Shiny and little knowledge of R

  • Recap on R through past slides and exercises
  • Learning of R shiny will be done through class lessons and weekly use of Datacamp to further reinforce the learning.

Limited knowledge in storyboard designing

Explore online resource through Tableau Public / Viz CookBook and Datacamp


Lack of postal code provided in the data

Use of OneMap API, together with python script, to retrieve Postal Codes of the Area and Street level. However, Postal Codes are insufficient for Tableau to zoom into street level visualization.

  • Hence, we will use QGIS learnt in SMT 201 for better visualisation.

Team Milestones

Our Current Timeline


Comments

Do Leave a Comment on how we can improve :)
No. Name Comments

1

Name

Insert Comment Here

2.

Name

Insert Comment Here

3.

Name

Insert Comment Here