Weave Code
Geo Laravel Package
yandex/geo
yandex/geo is a PHP client for the Yandex Geocoder API that converts addresses to coordinates and coordinates to addresses. It supports configurable language, precision, and result limits, making geocoding and reverse geocoding straightforward in Laravel/PHP applications.
PHP-library for interactions with geo-coding Yandex.Maps
Frequently asked questions about Geo
- How do I install yandex/geo in a Laravel application?
- Install it with composer require yandex/geo, then wrap the client in your own Laravel service provider or container binding. Because yandex/geo is framework-agnostic, expect no package auto-discovery, facade, config publishing, or migrations. Verify Composer constraints against your Laravel and PHP versions before adopting it.
- Does yandex/geo support Laravel 10, 11, or 12 and PHP 8.2 or 8.3?
- yandex/geo is not a Laravel package, so Laravel 10, 11, or 12 support depends on its PHP, Guzzle, and PSR dependency constraints. The last release was in 2019 and it has zero dependents, so modern downstream validation is limited. Run composer why-not and composer audit, then test PHP 8.1, 8.2, and 8.3 in a CI matrix. If conflicts appear, isolate it or fork it.
- How should I configure the Yandex Geocoding API key in Laravel?
- Store the Yandex Geocoding API key in an environment variable and expose it through config/services.php, then pass it into your own Yandex adapter. Do not commit the key or hard-code it in controllers. Add timeout, retry, logging, and locale settings at the adapter boundary. The package likely has no Laravel config publishing, so your app owns configuration.
- Can yandex/geo do reverse geocoding from coordinates to an address?
- Yes. yandex/geo wraps the Yandex Geocoder API and supports both forward geocoding from address to coordinates and reverse geocoding from coordinates to address. Normalize the returned structured objects into your own DTOs before they reach domain code. Test ambiguous addresses and missing address components in staging.
- How do I set locale, precision, and result limits with yandex/geo?
- The package supports configurable API key, locale, result limits, and precision when building requests. Set the locale and limits in your adapter configuration rather than scattering options through controllers. Validate the values and cache normalized results where appropriate. Confirm the exact option names against the package source before relying on them.
- Does yandex/geo integrate with Laravel caching and queues?
- There is no built-in Laravel cache or queue integration, so you should wrap yandex/geo in an adapter and add caching yourself. Cache normalized geocoding results with a sensible TTL and keep last-known results for fallback. Move bulk geocoding to queued jobs with rate limiting so you do not exhaust Yandex quotas. Monitor cache hit rate, latency, and error rate.
- What are the rate limit and quota concerns with yandex/geo in production?
- The package handles request building and API error handling, but it does not manage your Yandex quota, rate limits, or cost. Yandex API terms, quotas, and pricing can change and may constrain production use. Add throttling, exponential backoff, monitoring, and a fallback geocoder for critical workflows. Confirm your expected QPS, daily volume, and peak bursts with the Yandex plan.
- Is yandex/geo maintained and safe for production in 2025?
- Treat it as high risk for production because the last release dates to 2019 and there are zero dependents, so there is little modern validation. The MIT license is permissive but provides no support or warranty. It is reasonable as a short-term accelerator or spike dependency, not a strategic platform component. Assume internal ownership and have a fork or replacement exit plan.
- What alternatives or fallback geocoders should I consider instead of yandex/geo?
- First confirm whether Yandex Geocoding is mandatory, preferred, or replaceable. Define an internal Geocoder interface and compare yandex/geo against a minimal direct HTTP client and maintained alternatives. Add a fallback provider adapter for critical journeys and normalize all responses into internal DTOs. This keeps vendor lock-in contained and lets you swap providers without touching business logic.
- How should I test a yandex/geo integration in Laravel?
- Start with a time-boxed spike in a branch using a real API key in staging. Unit-test your adapter with mocked HTTP responses and cover timeouts, retries, and malformed inputs. Add contract or integration tests for ambiguous addresses, missing components, and rate-limit responses. Also verify composer why-not and composer audit against your target Laravel and PHP matrix.
Weaver
How can I help you explore Laravel packages today?