Wed, 10/19/2022 - 00:52
#1
Error 500, Geocode Failed: 400, Missing location object in JSON
Hello,
since today we are having problems with the Directions-API route call()
It returns: Illegal argument from request: Missing location object in JSON request
The locations object looks fine and the code worked for month.
Has anyone an idea how to wworkaround this?
{"locations":[null,{"latLng":{"lat":"52.775301","lng":"13.258308"}},{"latLng":{"lat":"52.8051558","lng":"13.0434855"}},{"latLng":{"lat":"52.7611813","lng":"13.0251667"}},{"latLng":{"lat":"52.7348326","lng":"12.5791113"}},{"latLng":{"lat":"52.7395869","lng":"12.5848501"}},{"latLng":{"lat":"52.7375987","lng":"12.5789778"}},{"latLng":{"lat":"52.7348326","lng":"12.5791113"}},{"latLng":{"lat":"52.6712398","lng":"12.3427011"}},{"latLng":{"lat":"52.858298","lng":"12.4343744"}},{"latLng":{"lat":"52.9372255","lng":"12.3956337"}},{"latLng":{"lat":"53.313445","lng":"12.250278"}},{"latLng":{"lat":"53.359251","lng":"12.3592918"}},{"latLng":{"lat":"53.15915","lng":"12.45341"}},{"latLng":{"lat":"52.775301","lng":"13.258308"}},null],"options":{"shapeFormat":"cmp6","timeType":1,"useTraffic":true,"doReverseGeocode":false,"conditionsAheadDistance":200,"generalize":0}}
The map route narrative initially used to used map-icon-nav-pin to inidcate POI along the route. Now all these are shown as map-icon-nav-straight. Is there a way to get to know the POI;s in the narrative. As we had some logic build around it in our UI , now it fails as the class does not exists.
s
We are experiencing the same issue. It seems that at somepoint the account/key gets transistioned to a new version of the API. This is easliy identifed by looking at the respone area. The new version puts the Session ID as the first element of the response. The new version has an issue with geocode location input.
The only way around this that we have found is to create a new account/key (new key by itself does not work).
The will use the orignal API version. (But for how long is a guess, the last time we did this the new account/api worked for 23 days).
Our problem was resolved by removing the sign character from postive latitude / longitude values in the JSON block.
I fixed it by settinging the start and end property,
In a previous version it was okay to set the waypoints object only.