Facebook graph API explorer query not extracting all columns - json

I am a newbie to this Graph API Explorer, which, I found today, is something that lets me extract data from FB. This is really cool!
I was trying to extract user demographic information using the Graph API explorer from a group with about 2300 members that I own, however for some reason the query is not extracting anything other than name and id as you can see from the screen.
Experts, why is this happening? I believe I have ticked all relevant permission tick boxes to be able to perform this query.
Thanks in advance.

Related

Missing return information in Google Knowledge Graph API response

We used to get "detailedDescription" field in the result when querying "kgsearch.googleapis.com/v1/entities:search" REST API for an id.
This is not the case anymore (regression from the recent days). I also tried using Google API explorer and their sample and it's not returning the field as well.
https://developers.google.com/knowledge-graph/reference/rest/v1/?apix_params=%7B%22ids%22%3A%5B%22%2Fm%2F0dl567%22%5D%7D
Can someone know when it'll be fixed?
Should we add extra info now in order to get this field as before?
Thanks in advance.
According to Google example documatation
No detailedDescription field in result

Facebook API posts photos

I am using the Facebook api to grab all the posts from a public page. Everything works great except for the photo they provide is very low quality and small. How do you modify your graph api query to get a better quality photo?
This was the original query I used to obtain an access token in the graph explorer:
1650393515218783?fields=posts
After reading similar questions and some documentation I tried this query
1650393515218783?fields=posts,picture.type(large)
But this still returned a low quality photo. Does anyone know how to get around this?
This may help
developers.facebook.com/docs/graph-api/reference/photo/

where is a thorough, accurate and complete description of Google Contacts API 3.0?

Google Contacts API 3.0 is described here:
https://developers.google.com/google-apps/contacts/v3/reference But this document is not complete.
In googles contacts form I can enter a name that is used to file the record rather than the contacts full name. I can access the record via XML or JSON and I get this field as gContact:fileAs. But the reference-Document does not contain a description of gContact:fileAs.
What else is missing in this reference-document?
On the other hand the description contains fields like gContact:billingInformation or gContact:jot or gContact:mileage that seem not to have a place in the contact form. So to me there seems to be no way to enter values into one of those fields, so they never will contain anything, and so they never will appear in the xml- or json-file that I can get from google. So I think there is no need to implement those fields in my application. - Or am I wrong with this?
So, please:
Where is a thorough, accurate and complete description of Google Contacts API 3.0?
Currently the best resource is: https://developers.google.com/google-apps/contacts/v3/ & https://developers.google.com/google-apps/contacts/v3/reference, this is the most accurate and up-to-date resource available at this time.
I realise this is not the answer you want, but it is the correct answer nonetheless.

Google provide JSON form query result?

I am doing some web mining tasks using Google.
Though using the ordinary Google search engine might help, I still need to analyse the web pages.
I want to ask:
Does Google provide query results in JSON form?
PS:
I know one place,Google Custom Search, but the query amount for free user is limited, which can not satisfy my need.
So, anyone know other solutions?
Google does not provide search results in JSON format unless you use the custom search API.
A 'Bing search engine' query can be run through a Yahoo Pipe and posted out as JSON.

Google Location API vs. Maps: Why are identical queries yielding different results?

I'm losing some hair over Google's AJAX API currently. What I do is turning structured location data into a Google local search API query in order to give users an alternative result list of places.
ex.:
http://ajax.googleapis.com/ajax/services/search/local?v=1.0&key=XXX&hl=en_US&mrt=localonly&rsz=large&q=pizza+Neustadt+DE
However, the API behaves very oddly at times, often not taking into account certain parameters I pass to it. For instance:
If I search for "term Rome Roma IT" on Google Maps, then it finds all terms in Rome as expected. If I repeat the same search on the API, I get zero results (I have to remove either 'Roma' or 'Rome' for it to work -- Roma is the administrative region here, and Rome the city name).
Why is that?
Another example. There is like 20 different towns, cities and boroughs called Neustadt in Germany. Now, when I search on Google Maps, it only finds one, unless I specify an additional qualifier, like a region or something.
Now, on the API level I kinda expected that when passing lat/lon parameters along with a query for Neustadt then it would be clever enough to pick the correct Neustadt by looking at the geo coding. But that doesn't happen, it always picks the same Neustadt and ignores the geo data.
q=pizza+Neustadt+DE&sll=48.8053,11.7579
I had similar problems when doing bounding box searches. The bounding box seems to be ignored completely, since I'm still getting result data which is a hundred kilometers off:
q=pizza+Neustadt+DE&sll=48.8053,11.7579&sspn=0.00001,0.00001
The last result is not even in the same city; shouldn't the tiny bounding box not result in any data whatsoever? I could even pass a zero size BBox and I would still get results.
I know there's an actually quite extensive documentation for the Local Search API, but it never goes into detail about which parameters are used when and how a query has to be structured and is evaluated, which makes it very difficult to get decent results.
Do you have any hints, tipps, suggestions on how to get to grips with Google Local search?
UPDATE:
I just found something REALLY odd. Could someone please go to this website:
http://code.google.com/apis/ajaxsearch/documentation/localsearch/index.html
open firebug, and monitor the HTTP traffic when typing in this search query:
test Rome Roma IT
You will get a bunch of results on the map. Now copy the URL that was contacted via AJAX and send a request to it on the command line:
curl "http://www.google.com/uds/GlocalSearch?key=internal-sample&v=1.0&rsz=large&sll=41.97684819454683%2C12.486648559570312&sspn=0.204185%2C0.549316&q=test%20Rome%20Roma%20IT&lssrc=lsc&lscstyle=final&start=0&callback=_callbacks_._5g139yfuc"
Now I get ZERO results. How can that possibly be? It's definitely not the key or callback args, I removed them without any change to the outcome of that query.
Is Google extending their search results when a query comes from one of their servers?
I've encountered exactly this same problem and it seems to be down to a combination of licensing issues and the fact that what Google exposes via its APIs and what it displays in the Maps/Google search pages are a combination of different searches (search, maps, base, data etc.etc.)
On the licensing issue, it seems that Google can display more information when a user goes via the browser, compared to requests via API calls (which could theoretically be automated).
See here for example.