Weave Code
Location Bundle Laravel Package
happyr/location-bundle
A Symfony bundle for adding location support to your application: geocode addresses, store latitude/longitude and address details on entities, and resolve coordinates via pluggable geocoder services. Useful for building location-aware features without wiring geocoding logic yourself.
A Symfony2 Bundle to handle geographic location of your entities
Frequently asked questions about Location Bundle
- Can I use happyr/location-bundle in a Laravel application?
- No. It is a Symfony bundle built on Symfony's dependency injection container, Doctrine ORM embeddables, and bundle configuration, and Laravel exposes none of those extension points. Installing it with Composer will not produce a working geocoding integration in a Laravel app. You would need a fork that rewrites every service definition and persistence mapping. For Laravel, use a maintained geocoding client or a small in-app service instead.
- What does happyr/location-bundle actually do?
- It wraps forward geocoding (address to coordinates) and reverse geocoding (coordinates to formatted address) behind an injectable Symfony service layer. It lets you configure a provider and API key through bundle config and includes Doctrine embeddables for storing location data on entities. The core ideas are portable, but the implementation is tied to Symfony conventions. Laravel developers can reuse the domain model without using the bundle.
- Is happyr/location-bundle maintained and safe for production?
- It was last released in 2020 and has four stars and zero dependents, which is a null signal rather than a small user base. Zero dependents means no downstream consumers are filing bugs, so there is no evidence it works against current PHP or Symfony versions. It also handles user-supplied addresses and makes outbound HTTP calls, so an unmaintained release is an unpatched input and egress surface. Treat it as high risk for production, especially in a Laravel app.
- Does happyr/location-bundle support Laravel 10 or Laravel 11?
- No. The bundle's Symfony 2 lineage implies symfony/* 2.x or 3.x constraints and PHP 5.5 to 7.x, which will not resolve on the PHP 8.2+ versions used by Laravel 10 and 11. Even if you forced the install, the code would hit removed functions and stricter type handling. Laravel's container is PSR-11 compatible but not driven by Symfony compiler passes, so the bundle's service registration model does not apply.
- How do I install happyr/location-bundle?
- In a Symfony application you would require it with Composer, register the bundle in the kernel, and configure the provider and API key. Laravel has no bundle registration step and no matching configuration tree, so a Composer require does not lead to a usable integration. For Laravel, skip this package and install a maintained geocoding client such as geocoder-php/geocoder behind your own service.
- What is a good Laravel alternative to happyr/location-bundle for geocoding?
- Use geocoder-php/geocoder behind a narrow GeocoderService interface, or a hosted API SDK such as Google Maps or Mapbox. For spatial queries, consider grimzy/laravel-mysql-spatial or PostGIS with latitude and longitude decimal columns. A value object, an Eloquent cast, a queued job for batch work, and a migration with a spatial index cover most needs in roughly 200 to 300 lines. That approach stays fully owned and on current dependencies.
- How should I store latitude and longitude on an Eloquent model?
- Use decimal columns such as decimal(10,7) for latitude and longitude, or a JSON column if you need structured address components alongside the coordinates. Add a spatial index if your database supports one, for example MySQL spatial types or PostGIS. Pair the columns with an Eloquent cast that validates ranges and clamps values. Keep coordinates separate from the display address so reverse geocoding results can change without corrupting the stored point.
- How do I test geocoding in a Laravel app without calling a real API?
- Put geocoding behind a narrow interface with one forward and one reverse method, then bind a fake implementation in your tests. In feature tests, swap the binding through Laravel's container or use Http::fake() if your client makes HTTP calls. This keeps tests fast, deterministic, and free of per-request API costs. Design for swappability from the start rather than mocking a concrete client.
- What are the risks of using an unmaintained geocoding package?
- Unmaintained packages can carry unpatched input-validation issues and outdated HTTP clients that conflict with modern Guzzle versions. They may also call removed PHP functions or fail under stricter type handling in PHP 8+. Geocoding accepts user-supplied addresses and IPs and makes outbound network calls, so stale dependencies create a real security and reliability surface. Prefer a maintained client or a hosted API with a current SDK.
- Can I migrate a Symfony app using happyr/location-bundle to Laravel?
- Migrate the concepts, not the code. Map the Location value object to a PHP value object plus an Eloquent cast, Doctrine embeddables to decimal or JSON columns, and the Symfony DI service to a GeocoderService bound in a Laravel service provider. Keep the geocoder behind your own interface so the provider stays swappable and testable. If the legacy Symfony service still runs in production, keep it running until the Laravel replacement is live rather than porting the bundle.
Weaver
How can I help you explore Laravel packages today?