- How do I install lemonpatwari/bangladeshgeocode in a Laravel app?
- Install it with Composer using composer require lemonpatwari/bangladeshgeocode. It is a Laravel package with auto-discovery, so manual service provider registration should not be needed. After installation, run the package migrations and seeders to load divisions, districts, upazilas, unions, and villages. Check the README for the exact publish and seed commands before running them in production.
- Does this package bundle Bangladesh geocode data or fetch it from an API?
- The package is described as shipping migrations, seeders, models, and helpers for Bangladesh geocode data, which indicates the dataset is bundled and loaded into your database rather than fetched from a remote API at runtime. That is the preferable shape for reliability because address forms do not depend on network availability. Confirm in the repository that no runtime HTTP calls are made before adopting it.
- Will the package migrations collide with my existing addresses or locations tables?
- The package publishes migrations for divisions, districts, upazilas, unions, and villages, so collisions are only likely if your application already uses those exact table names. Review the migration files before running them and check whether table names or prefixes are configurable. If there is no documented escape hatch, plan to rename your tables or fork the migrations.
- Which Laravel and PHP versions does lemonpatwari/bangladeshgeocode support?
- The package is intended for standard Laravel applications on modern PHP and uses Composer and Eloquent. The provided evaluation does not state exact Laravel or PHP constraints, so inspect the require section of composer.json and any CI matrix. Because the package has a single maintainer and few dependents, verify support for your target Laravel major before upgrading.
- Does it provide cascading division, district, upazila, and union dropdowns?
- The package overview says it includes helpers for building cascading location dropdowns and address forms. The expected hierarchy is division to district to upazila to union, with villages as the deepest level. You will still need to wire the frontend behavior, but the models and helpers should supply the filtered options. Confirm the foreign-key chain and nullability in the migrations.
- Are Bengali and English names both available for divisions, districts, and upazilas?
- The package description does not specify which name columns are included, so this is a key item to verify before adoption. Bangladesh address forms often need both Bengali and English labels, and the TPM assessment flags bilingual names as an open question. Inspect the seeder data and model fillable fields to confirm whether both are present. If only one language is shipped, you can extend the schema or fork the dataset.
- What are the primary keys—auto-increment IDs or stable BBS/LGED geocodes?
- The available context does not state whether the tables use auto-increment integers or stable administrative codes. Stable codes matter because they make future data refreshes and cross-system references much less painful. Check the migration definitions and seeder values before relying on IDs in your application. If only auto-increment IDs exist, avoid exposing them as permanent external identifiers.
- How current is the Bangladesh geocode data in this package?
- The package overview does not state an upstream source or snapshot date, which is the most serious omission for a dataset package. Bangladesh administrative geography changes over time, including the creation of Mymensingh division and proposed reorganizations, so stale data is a real risk. Check the repository for a stated source such as BBS or LGED and the date the data was captured. If that provenance is missing, treat the dataset as a starting point and plan to verify or refresh it.
- Is lemonpatwari/bangladeshgeocode safe to use in production?
- It is MIT-licensed and mechanically simple to integrate, but it has a single maintainer, no organizational backing, and very few dependents. The main production risks are stale administrative data and migration collisions with existing address schemas, not runtime instability. Because the payload is static reference data, you can fork and vendor it if the package is abandoned. Test the seeders and row counts in staging before running them in production.
- What should I check before adopting this package, or what are alternatives?
- Before adopting, confirm whether data is bundled or fetched, the upstream source and snapshot date, whether migrations are published, table name configurability, bilingual name support, primary key strategy, and Laravel version constraints. Alternatives include maintaining your own Bangladesh geocode tables seeded from BBS or LGED data, or using a static JSON or PHP array package if you do not want package-owned migrations. For a small read-mostly dataset, forking this package or vendoring the data is a reasonable fallback.