This is an example request:
http://maps.google.com/maps/geo?q=3353+Peachtree+Road+NE+#130,atlanta,ga&output=csv&key=****
This is the response:
{
"name": "3353 Peachtree Road NE ",
"Status": {
"code": 200,
"request": "geocode"
},
"Placemark": [ {
"id": "p1",
"address": "3353 Peachtree Rd NE, Atlanta, GA 30326, USA",
"AddressDetails": {"Country": {"CountryNameCode":
"US","CountryName": "USA","AdministrativeArea":
{"AdministrativeAreaName": "GA","Locality": {"LocalityName":
"Atlanta","Thoroughfare":{"ThoroughfareName": "3353 Peachtree Rd
NE"},"PostalCode": {"PostalCodeNumber": "30326"}}}},"Accuracy": 8},
"ExtendedData": {
"LatLonBox": {
"north": 33.8510057,
"south": 33.8447105,
"east": -84.3640258,
"west": -84.3703210
}
},
"Point": {
"coordinates": [ -84.3671734, 33.8478581, 0 ]
}
} ]
}
If I simply remove the # from the request, the response is:
200,8,33.8478581,-84.3671734
AJ
On Apr 3, 1:44 pm, Andrew Leach <[email protected]> wrote:
> On Apr 3, 6:20 pm, AJ <[email protected]> wrote:
>
> > When I submit a geocoding request with output=csv and the address
> > contains a pound sign (#), the response is returned in JSON format
> > rather than CSV. Is this a bug?
>
> It could be, I suppose: if you ask for CSV the error code could be
> returned as CSV. When I try an address including a hash sign I get a
> 400 error. If you get a 200 success result but in JSON instead of CSV,
> please do give an example.
>
> Andrew
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---