Add Geo Models for Division, District, and Thana

TasfiqulGhani commented 3 weeks ago

Summary

This PR introduces three new models to the project: Division, District, and Thana. These models are designed to represent geographical divisions with associated polygon data.

Changes:

Division Model: Added to represent major administrative divisions. Each division includes a name, a polygon for geographical boundaries, and an optional description.
District Model: Added to represent districts within divisions. Each district is associated with a division, has a polygon field for geographical boundaries, and an optional description.
Thana Model: Added to represent thanas within districts. Each thana is linked to a district, includes a polygon for geographical boundaries, and an optional description.

Admin Panel Enhancements:

Registered the Division, District, and Thana models in the Django admin panel.
Configured list views, search fields, and filters for better management of geographical data in the admin interface.

Additional Notes:

These models lay the groundwork for handling geographical data in the project. Further enhancements may include integrating GIS functionalities or adding additional fields as required.

dg1223 commented 1 week ago

@TasfiqulGhani @skfarhad Hi! I am working on #38 to create a database for admin boundaries using the model in address.py.

I was looking at the database table structure in address.py. I noticed that it is missing Upazila, which is the admin level between District and Thana. I'm not sure if it is intended. We can create relationships even if we skip this level but I wanted to bring this to your attention nonetheless.

If you want, I can add it to the model in address.py and update the foreign keys accordingly. Let me know.

Here are the official admin levels from the latest available shapefiles.

adm = Administration Regions

adm0 = Entire Bangladesh
adm1 = 8 Divisions
adm2 = 64 Districts/Zilas
adm3 = 544 Upazilas
adm4 = 5160 Thanas/Unions

skfarhad commented 1 week ago

@TasfiqulGhani @skfarhad Hi! I am working on #38 to create a database for admin boundaries using the model in address.py.

I was looking at the database table structure in address.py. I noticed that it is missing Upazila, which is the admin level between District and Thana. I'm not sure if it is intended. We can create relationships even if we skip this level but I wanted to bring this to your attention nonetheless.

If you want, I can add it to the model in address.py and update the foreign keys accordingly. Let me know.

Here are the official admin levels from the latest available shapefiles.

adm = Administration Regions

adm0 = Entire Bangladesh

adm1 = 8 Divisions

adm2 = 64 Districts/Zilas

adm3 = 544 Upazilas

adm4 = 5160 Thanas/Unions

@dg1223 you may add a new column Upazila. And, is Union goin to be one level higher than corresponding Thana? Or they are in the same admin level?

dg1223 commented 1 week ago

@TasfiqulGhani @skfarhad Hi! I am working on #38 to create a database for admin boundaries using the model in address.py. I was looking at the database table structure in address.py. I noticed that it is missing Upazila, which is the admin level between District and Thana. I'm not sure if it is intended. We can create relationships even if we skip this level but I wanted to bring this to your attention nonetheless. If you want, I can add it to the model in address.py and update the foreign keys accordingly. Let me know. Here are the official admin levels from the latest available shapefiles. adm = Administration Regions

adm0 = Entire Bangladesh

adm1 = 8 Divisions

adm2 = 64 Districts/Zilas

adm3 = 544 Upazilas

adm4 = 5160 Thanas/Unions

@dg1223 you may add a new column Upazila. And, is Union goin to be one level higher than corresponding Thana? Or they are in the same admin level?

@skfarhad Union and Thana are at the same level.

skfarhad / hazard_reporting_system