Forum Replies Created
Data updated for the 15 – 27 July time period after model re-run.
July 2020 v1.4.1
- Bug fix where some Perth LGAs did not appear on heatmap
- Added number of rows toggle to ranking tables
- Added invoicing feature to the account dashboard
- Data for ~1,500 previously excluded suburbs added to ranking tables, charts, heatmaps
- Tableau Reports out of Beta
- Added confidence filter to Tableau Reports
- ~30 outlier localities removed from ranking tables after improved data clean procedure
June 2020 v1.4
- Ranking Table JSON structure updated to improve performance
- Launched Growth Rate Cycle metric (replaced Beta Market Cycle metric)
- GRC column is now an optional toggle
- Added “Buy Now Pay Later” option to report checkout on the store
- Beta version of Tableau Reports available
May 2020 v1.3.4
- Improved data clean procedure for listings
- Improved general SQL queries for better performance
- Cosmetic improvements to ranking table
- Yearly subscriptions introduced
- Updated Pricing Tables so that all features are clearly explained
- Bug fix in automated cycle detection logic
April 2020 v1.3.3
- Responsive changes to ranking table HTML
- Improved JSON pre-processing in ranking tables
- Introduced automated cycle detection logic
- Added beta version of Market Cycle metric
March 2020 v1.3.2
- Bug fixes in forecast LGA procedure for when limited sales data is encountered
- Bug fixes due to geopandas upgrade
- Homepage layout updates
February 2020 v1.3.1
- Started new v2 baseline code branch (alpha)
- Styling updates to ranking tables
- Free Tier Subscriptions introduced
January 2020 v1.3
- Improved navigation on LGA pages
- Digital Store fully launched
- New site theme to improve usability and performance
December 2019 v1.2.2
- Introduced suburb level store reports
- Bedroom filter introduced to suburb ranking tables
It is now possible to select the amount of rows displayed as per your request. This is only enabled on the home page at this point. We may also add it to LGA pages in the future.
Thanks for your request. I will pass it on to our dev team for assessment.
In the meantime, you can download the ranking table data from our store. Downloaded reports have an export feature which will allow you to view the data in excel without the page limit.
Here is the link to the store: https://www.htag.com.au/store
You can find capital growth heatmaps on all of our LGA pages. To view the heat map, click on the Heatmaps tab.
Thanks for raising this.
When you click through to the LGA page, the first tab ranks all suburbs within the LGA. The data in every row of the table is referent to each suburb listed and not to the LGA as a whole.
You did correctly point out that there is only one locality in this LGA, and the expectation would be that the LGA values should be comparable to the locality values in the table (Kalbarri). However, we calculate the LGA-level metrics independently from suburb/locality -level metrics.
As we only list the suburbs/localities for which there is significant sales data and the rest of the suburbs are omitted, it is possible for aggregated LGA values to differ from each individual locality within the LGA. In other words, even though the data from other localities in the LGA (15 in the case of Northampton) is accounted for in the calculation of LGA-level metrics, it is so thinly spread across multiple localities that it only transpires in 1 locality out of 15 at the suburb-level.
Also note the Very Low confidence assigned to Kalbarri, indicating the low sales volume and therefore high data error in this particular locality.
This scenario is more of an exception than a rule as you have come across a rural area with very limited data. If you are interested in researching this area, I would suggest focusing on the LGA-level data and discarding suburb-level data due to Very Low Confidence ranking.
Googled and found your original article Jeremy. Thanks for pointing this out. Here is the link https://www.yourinvestmentpropertymag.com.au/market-analysis/the-great-population-growth-myth-200331.aspx
This is now done!