Back to YDN Documentation Forum
0

http://where.yahooapis.com/geocode?appid=..&flags=PE returning XML not PHP

Something changed in the last few days. Our geocode queries requesting PHP are having XML
returned.
http://where.yahooapis.com/geocode?appid=...&location=2780%20cottonwood%20ct.,%20Clearwater,%20FL,%2033761-3809&gflags=Q&flags=EP

<ResultSet version="2.0" xml:lang="en-US"><Error>0</Error><ErrorMessage>No error</ErrorMessage><Locale>en-US</Locale><Found>1</Found><Quality>87</Quality><Result><quality>87</quality><latitude>28.015209</latitude><longitude>-82.722389</longitude><offsetlat>28.01545</offsetlat><offsetlon>-82.722443</offsetlon><radius>400</radius><name/><line1>2780 Cottonwood Ct</line1><line2>Clearwater, FL 33761-3809</line2><line3/><line4>United States</line4><house>2780</house><street>Cottonwood Ct</street><xstreet/><unittype/><unit/><postal>33761-3809</postal><neighborhood/><city>Clearwater</city><county>Pinellas County</county><state>Florida</state><country>United States</country><countrycode>US</countrycode><statecode>FL</statecode><countycode/><uzip>33761</uzip><hash>82261C741FBC9921</hash></Result></ResultSet><!-- nws02.maps.bf1.yahoo.com uncompressed/chunked Mon Oct  1 10:27:21 PDT 2012 --><!-- wws01.geotech.bf1.yahoo.com uncompressed/chunked Mon Oct  1 10:27:21 PDT 2012 -->

We used to get:
a:1:{s:9:"ResultSet";a:7:{s:7:"version";s:3:"1.0";s:5:"Error";i:0;s:12:"ErrorMessage";s:8:"No error";s:6:"Locale";s:5:"us_US";s:7:"Quality";i:87;s:5:"Found";i:1;s:6:"Result";a:1:{i:0;a:27:{s:7:"quality";i:87;s:8:"latitude";s:9:"28.015223";s:9:"longitude";s:10:"-82.722071";s:9:"offsetlat";s:9:"28.015349";s:9:"offsetlon";s:10:"-82.722075";s:6:"radius";i:500;s:4:"name";s:0:"";s:5:"line1";s:18:"2780 Cottonwood Ct";s:5:"line2";s:26:"Clearwater, FL  33761-3809";s:5:"line3";s:0:"";s:5:"line4";s:13:"United States";s:5:"house";s:4:"2780";s:6:"street";s:13:"Cottonwood Ct";s:7:"xstreet";s:0:"";s:8:"unittype";s:0:"";s:4:"unit";s:0:"";s:6:"postal";s:10:"33761-3809";s:12:"neighborhood";s:0:"";s:4:"city";s:10:"Clearwater";s:6:"county";s:15:"Pinellas County";s:5:"state";s:7:"Florida";s:7:"country";s:13:"United States";s:11:"countrycode";s:2:"US";s:9:"statecode";s:2:"FL";s:10:"countycode";s:0:"";s:4:"uzip";s:5:"33761";s:4:"hash";s:16:"82261C741FBC9921";}}}}

by
Report Abuse
3 Replies
  • I also experienced this hiccup. I updated 2 sites to match the new spec... and then it changed back again. luckily I use git, so it was easy to roll back. IS there any documentation on this? I'd like to have proof when I cite the bug.


    QUOTE(Stephen @ 1 Oct 2012 10:33 AM)
    Something changed in the last few days. Our geocode queries requesting PHP are having XML
    returned.
    http://where.yahooapis.com/geocode?appid=...&location=2780%20cottonwood%20ct.,%20Clearwater,%20FL,%2033761-3809&gflags=Q&flags=EP

    <ResultSet version="2.0" xml:lang="en-US"><Error>0</Error><ErrorMessage>No error</ErrorMessage><Locale>en-US</Locale><Found>1</Found><Quality>87</Quality><Result><quality>87</quality><latitude>28.015209</latitude><longitude>-82.722389</longitude><offsetlat>28.01545</offsetlat><offsetlon>-82.722443</offsetlon><radius>400</radius><name/><line1>2780 Cottonwood Ct</line1><line2>Clearwater, FL 33761-3809</line2><line3/><line4>United States</line4><house>2780</house><street>Cottonwood Ct</street><xstreet/><unittype/><unit/><postal>33761-3809</postal><neighborhood/><city>Clearwater</city><county>Pinellas County</county><state>Florida</state><country>United States</country><countrycode>US</countrycode><statecode>FL</statecode><countycode/><uzip>33761</uzip><hash>82261C741FBC9921</hash></Result></ResultSet><!-- nws02.maps.bf1.yahoo.com uncompressed/chunked Mon Oct  1 10:27:21 PDT 2012 --><!-- wws01.geotech.bf1.yahoo.com uncompressed/chunked Mon Oct  1 10:27:21 PDT 2012 -->

    We used to get:
    a:1:{s:9:"ResultSet";a:7:{s:7:"version";s:3:"1.0";s:5:"Error";i:0;s:12:"ErrorMessage";s:8:"No error";s:6:"Locale";s:5:"us_US";s:7:"Quality";i:87;s:5:"Found";i:1;s:6:"Result";a:1:{i:0;a:27:{s:7:"quality";i:87;s:8:"latitude";s:9:"28.015223";s:9:"longitude";s:10:"-82.722071";s:9:"offsetlat";s:9:"28.015349";s:9:"offsetlon";s:10:"-82.722075";s:6:"radius";i:500;s:4:"name";s:0:"";s:5:"line1";s:18:"2780 Cottonwood Ct";s:5:"line2";s:26:"Clearwater, FL  33761-3809";s:5:"line3";s:0:"";s:5:"line4";s:13:"United States";s:5:"house";s:4:"2780";s:6:"street";s:13:"Cottonwood Ct";s:7:"xstreet";s:0:"";s:8:"unittype";s:0:"";s:4:"unit";s:0:"";s:6:"postal";s:10:"33761-3809";s:12:"neighborhood";s:0:"";s:4:"city";s:10:"Clearwater";s:6:"county";s:15:"Pinellas County";s:5:"state";s:7:"Florida";s:7:"country";s:13:"United States";s:11:"countrycode";s:2:"US";s:9:"statecode";s:2:"FL";s:10:"countycode";s:0:"";s:4:"uzip";s:5:"33761";s:4:"hash";s:16:"82261C741FBC9921";}}}}
    Report Abuse
    0
  • I'm so sorry I missed this!

    The main discussion on this was in the Placefinder forum.  http://developer.yahoo.com/forum/PlaceFinder-General-Discussion/PlaceFinder-API-v2-released-/1349096254137-b9ba25b6-f983-4fed-afc6-97a35e7fb644

    It was an inadvertent switch and when we realized our error, we reverted.

    Robyn
    Report Abuse
    0
  • This is still happening for me, when requesting JSON on the GeoPlanet API.
    I also sometimes get a 400/Bad Request error for a request that was previously returning a 200 status code.

    Example:
    => "http://where.yahooapis.com/v1/places.q('London+-++UK')?format=json&appid=MYAPPID"

    QUOTE(duzins @ 5 Oct 2012 2:25 PM)
    I'm so sorry I missed this!

    The main discussion on this was in the Placefinder forum.  http://developer.yahoo.com/forum/PlaceFinder-General-Discussion/PlaceFinder-API-v2-released-/1349096254137-b9ba25b6-f983-4fed-afc6-97a35e7fb644

    It was an inadvertent switch and when we realized our error, we reverted.

    Robyn
    Report Abuse
    0
✕ This forum is locked.
Ask a Question

Recent Posts

in YDN Documentation