-
This is the page where we apply the filter of the place of which problems we want to see.
-
This is the page from which we can add the problem for the exact place.
-
This page is for showing the required result of the filter.
Inspiration
In many communities, local problems such as broken roads, garbage issues, water shortages, and damaged street lights often go unreported or unresolved because there is no simple and organized reporting system. I was inspired to build the Community Problem Reporter System to give citizens an easy way to report issues and to make problem visibility location-specific and transparent.
What it does
The Community Problem Reporter System allows users to report community issues by selecting their province, district, municipality, and ward. Users can also upload images and descriptions of the problem. On the main page, users can filter and view problems based on location, ensuring they only see issues relevant to their area. An admin panel allows administrators to update the status of reported problems.
How we built it
The project was built using PHP for server-side logic, MySQL for database management, HTML and CSS for structure and styling, and JavaScript for dynamic location-based dropdowns. Location filtering was implemented using a structured locations JSON file, enabling province-to-district-to-municipality selection. Prepared SQL statements were used to securely fetch and display data.
Challenges we ran into
One of the major challenges was implementing hierarchical location filtering while keeping the system flexible, such as allowing users to view problems for an entire province or a specific ward. Debugging database errors and maintaining consistent UI styling across multiple pages were also challenging but helped improve problem-solving skills.
Accomplishments that we're proud of
We successfully built a fully functional, location-based problem reporting system with secure database queries, dynamic dropdown filters, and a clean user interface. The project demonstrates real-world applicability and follows good development practices suitable for civic technology solutions.
What we learned
Through this project, we learned how to design a complete CRUD-based web application, handle user input securely, manage relational databases, and implement real-time filtering logic. We also gained experience in debugging server-side errors and improving user experience.
What's next for Community Problem Reporter System
In the future, we plan to add map-based issue visualization, email notifications, user authentication, pagination, and advanced admin analytics. These features would make the system more scalable and useful for larger communities.
Log in or sign up for Devpost to join the conversation.