1. I open an incognito window in chrome.
2. I go to the location https://maps.google.com/locationhistory
3. I have to login. I do so. 🙂
4. I am redirected to https://maps.google.com/locationhistory/b/0 , and I can see where I’ve been today.
5. I open the extension, get a list of 15 cookies (not counting header comments) and saving them to cookies.txt (using a coder’s editor, UTF-8, Unix-Linebreaks, no BOM-Header,… the usual stuff for text files for command line usage. (Tried Windows and Classic Mac also, with no better result)
6. I enter that command:
curl -b cookies.txt “https://maps.google.com/locationhistory/b/0/kml?startTime=1398510000000&endTime=1398517922000”

Result is output to screen:

The document has moved , http://www.google.com/accounts/ServiceLogin

A redirect to the login screen.

If I enter the same URL in the Chome incognito tab, I get a KML-file (looking inside: Yes, geodata). That also proofs they don’t check the referer.

Since the cookie-textfile mentions an example that uses wget I try that also. wget also is redirected and then downloads the html of the website. Which is not useful, but at least its funny. 🙂

I’ve noticed your cookie file has 16 entries (mine has 15), however, since the „interesting parts“ are blured for good reason and my lines have a different order I cannot find out which one is missing (and if thats the reason).

7. Blamed the Mac. Used a VM with Debian Squeeze Linux instead. Same result.

8. Just to understand what’s going on I use curl without the cookie file. Same result.

Hm.