Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for GetAddress UK Postcode Geocoding and Lookups #1645

Closed

Conversation

mark-young-atg
Copy link

@mark-young-atg mark-young-atg commented Jan 9, 2024

Add support for GetAddressUk lookups

phil-johnson and others added 30 commits June 14, 2016 16:22
This commit adds support for GetAddress (getaddress.io) postcode geocoding and lookups.
This commit removes the sanitize method from query (as it's never a hash) and instead ensures the query string doesn't contain whitespace.
This commit adds support for GetAddress (getaddress.io) postcode geocoding and lookups.
* add trimble maps backend

https://developer.trimblemaps.com/restful-apis/location/single-search/single-search-api/

* add tests & fix a few bugs

* add url escaping

* add Trimble Maps to API guide

* don't depend on activesupport

* raise an error if api key is invalid

* rename to PC Miler

The company is Trimble.
The mapping product is Trimble Maps.
The geolocation service is PC Miler.
* adds metadata

add metadata option to single search for trimble maps api call

* modify fixtures

* Revert "modify fixtures"

This reverts commit 67334e3.

* copy metadata over to each location so data object would include that
adds test for that

* update fixtures

* add bang to add_metadata_to_locations method name
* Remove double encoding

* Fix existing test
@mark-young-atg mark-young-atg marked this pull request as ready for review January 9, 2024 16:30
@alexreisner
Copy link
Owner

Thanks for this. From what I can tell it looks pretty good, but could you please rebase to current master so I can run tests and review properly? Thanks!

@mark-young-atg
Copy link
Author

Apologies @alexreisner. I'm not sure how this PR turned into such a fresh hot mess so quickly. I've given up with trying to maintain any sort of history of the original commits for this work. Instead I've opened a fresh PR which is straight forward and clean. I'll close this one. Thank you very much in advance for looking at this new functionality. I stand ready to address any concerns you may raise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.