You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2021. It is now read-only.
We need to document the fact that its just far easier to POST json to our services than to GET with it. json is awesome but it makes use of a lot of characters that need urlencoded. On top of that some of our API's like you to send the polyline encoded string as input instead of literal coordinates. The polyline encoded string is all visible ascii so that is nice but it has even more characters that need to be urlencoded. Couple that with the fact that it allows for escape chars and you are in for a painful bit of programming. At any rate at this point we have assembled workign code for POSTing in ruby and javascript and we can add python too. We can also describe the pitfalls above and suggest some best practices.
The text was updated successfully, but these errors were encountered:
We need to document the fact that its just far easier to POST json to our services than to GET with it. json is awesome but it makes use of a lot of characters that need urlencoded. On top of that some of our API's like you to send the polyline encoded string as input instead of literal coordinates. The polyline encoded string is all visible ascii so that is nice but it has even more characters that need to be urlencoded. Couple that with the fact that it allows for escape chars and you are in for a painful bit of programming. At any rate at this point we have assembled workign code for POSTing in ruby and javascript and we can add python too. We can also describe the pitfalls above and suggest some best practices.
The text was updated successfully, but these errors were encountered: