We are in the process of creating a process to validate the accuracy of an addre

Josh over 8 years ago

We are in the process of creating a process to validate the accuracy of an address and retrieve latitude and longitude values. We are attempting to use the Google Maps Geocoding API for this purpose. We are a Google Maps for Business API customer, which requires that each request to the Maps API contain a client and signature parameter. The client value is static, but the signature is a dynamically generated, URL safe Base64 encoded value . I've already created the expression that generates the signature but am having issues when sending the value as a parameter in both the httpquery expression and http query smart service. Has anyone successfully integrated with the Google Maps Geocoding API, specifically as a Google Maps for Business customer? If so, I would like to hear about your experience.

Discussion posts and replies are publicly visible

Parents

0 Josh over 8 years ago

I changed to Commons Codec 1.10 and specified the charset as UTF-8 and the issue is gone. I did some more research and it turns out that Commons Codec 1.4 was the culprit. The encodeBase64String method in 1.4 used multi-line chunking, placing a \\r\
at the end of each line, even if the there is only one line. That was changed in 1.5 to single-line non-chunking. Thank you very much for your help!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Josh over 8 years ago

I changed to Commons Codec 1.10 and specified the charset as UTF-8 and the issue is gone. I did some more research and it turns out that Commons Codec 1.4 was the culprit. The encodeBase64String method in 1.4 used multi-line chunking, placing a \\r\
at the end of each line, even if the there is only one line. That was changed in 1.5 to single-line non-chunking. Thank you very much for your help!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data