Skip to content

UC00198_WASTE_MANAGEMENT_AND_HEALTH_RISKS-100%-COMPLETE#1545

Merged
deepthireddy03 merged 1 commit intomasterfrom
deepthireddy
Sep 21, 2025
Merged

UC00198_WASTE_MANAGEMENT_AND_HEALTH_RISKS-100%-COMPLETE#1545
deepthireddy03 merged 1 commit intomasterfrom
deepthireddy

Conversation

@deepthireddy03
Copy link
Copy Markdown
Contributor

This pull request includes the final updates and enhancements for the project:

  • Cleaned and aligned waste, complaints, zones, and social datasets; built a monthly table with a guard against partial-month bias.
  • Created visuals: waste vs complaints (3-month rolling), stacked area of top streams plus other, and a Top Movers bar chart (last 12 vs prior 12 months).
  • Found a strong waste–complaints link (same-month r≈0.81; lag-1 r≈0.81), so a waste spike is a good early signal for next month’s complaints.
  • Built a suburb risk matrix and K-Means clusters (silhouette≈0.44); hotspots are Melbourne, Carlton, West Melbourne; Residential drives growth with Recycling and Mattresses rising; month clustering and IsolationForest flagged peaks and anomalies.

Copy link
Copy Markdown
Contributor

@Nidhi-kanchepalle Nidhi-kanchepalle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Deepthi,

This use case is excellent! The data has been accessed using APIs, the correct template has been used, and the pull request has been raised in the right folder. You’ve presented some really valuable insights, especially around waste composition over time and identifying the top streams. All visualisations are neat and clear, with proper legends.

The code documentation is particularly impressive. Including sections like “What the code does,” “Why this visualisation,” and “Conclusion” for each snippet makes the use case very easy to follow. The logical flow is strong, and the tutorial-style approach adds great value for readers.

I did notice that “standardize” has been used instead of “standardise” in a few places—this just needs a quick fix before merging into the master branch. Apart from that, everything else is spot on. Fantastic work!

Copy link
Copy Markdown
Contributor

@nelkin01 nelkin01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Deepthi,

Great work!

Your use case is well-defined and easy to understand. Every section is well put together with a proper set of explanation throughout the analysis you have performed.

Data has been pulled using API, which satisfies the requirement.

The use of Australian English is missing in a few places but overall well done.

I also liked the detailed references you have added which is helpful for someone going through your work, who has minimal knowledge.

Approving the merge! Thanks.

@deepthireddy03 deepthireddy03 merged commit b7388a1 into master Sep 21, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants