Hi everyone,
in recent weeks we rolled out new versions of both our PHP (4.1.0) and our Python geocoding API SDKs
Some of the fixes:
Our PHP geocoding SDK (v4.1.0)
Main changes:
-
now requires PHP 8.3 or newer
-
now comes with Laravel fascade to make installing and using the library inside the popular web framework easier (see example in the README)
-
updates to various deependencies
Please see our PHP geocoding tutorial for usage examples.
Our Python geocoding SDK (v3.5.0)
Main changes:
-
Requires python 3.10, tests with python 3.15
-
Add warning and safeguard that overlapping/nested context managers on one instance aren’t supported
-
Redact API key in error messages
-
Network errors from requests and aiohttp treated differently
-
Async: like with sync, non-JSON responses now raise UnknownError
-
updates to various deependencies
Please see our Python geocoding tutorial for usage examples.
What about other languages?
If neither PHP nor Python is your cup of tea (and who can blame you, when Perl is obviously better!) then fear not, as we have geocoding SDKs for over 40 different languages and frameworks
We continually roll out various fixes and improvements, and code contributions are of course also gladly received.
Final Points
You may be asking yourself why to use aan SDK at all. I mean surely AI can just whip up an implementation on the fly. Our strong advice is to use one of our SDKs which have been tested by hundreds of developers over the years. There are so many edge cases, particularly around things like error handling or issues and best practices related to security it really is better to rely on our SDK.
Our geocoding Agent Skill, which includes reference files for working with various popular languages, including both Python and PHP, can be used to inform your AI agent how to use the SDKs
Happy geocoding (be it in Python, PHP or any other language),