- How do I install netsells/laravel-geoscope in a Laravel application?
- Install it with Composer using composer require netsells/laravel-geoscope, then follow the package's service provider and config publishing steps if they are not auto-discovered. Run php artisan migrate if the package ships migrations. Check the README for the exact publish tags and any required configuration values.
- Which Laravel and PHP versions does laravel-geoscope support?
- The provided context does not include the Composer version constraints, so check the package's composer.json before installing. The latest visible release is 2.0.2 from December 2020, which means it predates recent Laravel and PHP majors. Verify compatibility against your Laravel and PHP versions rather than assuming current support.
- How do I find records within a radius using latitude and longitude in Laravel?
- GeoScope is designed to add Eloquent query scopes that filter by latitude and longitude and calculate distance. You typically call the package's radius scope on your model with a center latitude, longitude, and distance value. Check the README for the exact scope name and units, then chain normal Eloquent conditions as needed.
- Does netsells/laravel-geoscope support MariaDB?
- Release 2.0.2 added MariaDB support according to the changelog. The note is a single line and does not document which MariaDB versions were tested, so treat it as a compatibility claim to verify. Test your specific MariaDB version and query paths before relying on it in production.
- How does laravel-geoscope calculate distance between coordinates?
- The package calculates distance from latitude and longitude values so you can order or filter records by proximity. The provided release notes do not specify the SQL formula, whether it uses Haversine, or whether spatial indexes are involved. Inspect the package source or README to confirm the calculation and performance characteristics.
- Can I use laravel-geoscope with MySQL 8 or PostgreSQL?
- The MariaDB compatibility patch strongly suggests the package targets MySQL-family databases rather than PostgreSQL. MySQL 8 may work, but the 2020 release date means it was not validated against newer MySQL behavior. PostgreSQL support is not indicated, so do not assume it without checking the source.
- Is laravel-geoscope maintained and safe for production use?
- The only visible release is 2.0.2 from December 2020, which is a stale maintenance signal for a package with database coupling. It may still work for older Laravel stacks, but assess risk for current projects. Pin the version, run integration tests against your database, and consider a maintained alternative if you need long-term support.
- How do I test laravel-geoscope scopes without a production database?
- Use a test database that matches your production engine, ideally MySQL or MariaDB in a container, because geographic SQL and dialect behavior can differ from SQLite. Write feature tests that create known coordinates and assert radius and distance results. Avoid relying only on SQLite if the package uses MySQL-specific SQL.
- Does laravel-geoscope require its own database tables or migrations?
- The package follows standard Laravel conventions and is described as config-publishable and migration-bearing, so plan for a migrate step if you publish its migrations. Confirm whether those migrations create package-owned tables or add indexes to your existing tables. If you only use query scopes, check the README to see whether schema changes are optional.
- What are alternatives to laravel-geoscope for location-based queries in Laravel?
- Alternatives include writing your own Haversine query scope, using MySQL spatial types and ST_Distance_Sphere, or choosing an actively maintained geospatial Laravel package. The right choice depends on whether you need simple radius filtering or full spatial indexing. Evaluate maintenance cadence and database support before switching.