Yes it can. It is relatively straightforward to write a simple program to retrieve real-time stock quote using just Google Spreadsheet Data API. Below is a simple proof-of-concept script which does the job. To make it work, create a new Spreadsheet on Google Docs and int the cell A1 fill in a formula for your favorite stock quote, something like:

=GoogleFinance("GOOG")

You will see the price in your spreadsheet:

The script to retrieve the quote:

#!/bin/bash

wget -O ClientLogin.txt --no-check-certificate --post-file=post.txt \
"https://www.google.com/accounts/ClientLogin" >/dev/null 2>&1

TOKEN=`cat ClientLogin.txt | grep Auth \
| sed "s#Auth=##" | xargs echo -n`

wget -O Spreadsheets.txt --header="Authorization: GoogleLogin auth=${TOKEN}" \
--header="GData-Version: 2" \
http://spreadsheets.google.com/feeds/spreadsheets/private/full >/dev/null 2>&1

WORKSHEET=`cat Spreadsheets.txt | \
sed "s#\(.*\)src=\([']*\)\([^']*\)\([']\)\(.*\)#\3#"`

wget -O Worksheet.txt --header="Authorization: GoogleLogin auth=${TOKEN}" \
--header="GData-Version: 2" ${WORKSHEET} >/dev/null 2>&1

cat Worksheet.txt | sed 's#\>#\>\
#g' >WorksheetFormatted.txt

CELLSFEED=`cat WorksheetFormatted.txt | grep cellsfeed | \
sed "s#\(.*\)href=\([']*\)\([^']*\)\([']\)\(.*\)#\3#"`

wget -O Cells.txt --header="Authorization: GoogleLogin auth=${TOKEN}" \
--header="GData-Version: 2" ${CELLSFEED} >/dev/null 2>&1

cat Cells.txt | sed 's#\>#\>\
#g' >CellsFormatted.txt

REALTIMEQUOTE=`cat CellsFormatted.txt | grep numericValue | \
sed "s#\(.*\)numericValue=\([']*\)\([^']*\)\([']\)\(.*\)#\3#"`

echo "Quote = ${REALTIMEQUOTE}"

where post.txt is something like:

POST /accounts/ClientLogin HTTP/1.0
Content-type: application/x-www-form-urlencoded

accountType=HOSTED_OR_GOOGLE&Email=__EMAIL__&Passwd=__PASSWD__
&service=finance&source=yken.org-GoogleStockQuote-0.1

A few notes on the script:

• Replace __EMAIL__ and __PASSWD__ in post.txt with your Google credentials
• This will only work when you have just one spreadsheet on your Google Docs
• The script does not parse the XML replies, it just gets the values it needs using brute force (as it is just a proof of concept).
• Three requests (four with login) just to get a quote is definitely over the top. The Google API allows batch operations, too.
• I tried this on Max OS X 10.5 only

To make the script actually useful, it would be good to modify it to take some parameters, for instance at least the desired stock symbol and then to use that stock symbol to write the =GoogleFinance() formula to A1. Google Data API allows it. This way, the script could be used for retrieving any quote (available on Google Finance), not only just the hardcoded one. Also, there are many Google Data API Client Libraries available, allowing to rewrite this script into something proper. I will try both and will post the result here.

Important note: all stock data obtained by the above script can be used for personal informational purposes only, see the Google disclaimer.

It turned out hat the cause of getting the 401 error was in the way I set up the Authorization header sent with my requests. Unlike with AuthSub Authorization header used for web applications, the token value for ClientLogin authentication must not be enclosed in (double-)quotes. This is a mistake easy to make when switching from AuthSub to ClientLogin, resulting in HTTP status 401 reply for any Data API request. Remove the quotes around the token and the Data API request will work fine.

A small sample:

#!/bin/bash

if [ -e ClientLogin ]
then
  rm ClientLogin
fi

wget --no-check-certificate --post-file=post.txt \
https://www.google.com/accounts/ClientLogin

TOKEN=`cat ClientLogin | grep Auth | \
sed "s#Auth=##" | xargs echo -n`

wget --header="Authorization: GoogleLogin auth=${TOKEN}" \
http://finance.google.com/finance/feeds/default/portfolios

where post.txt is something like:

POST /accounts/ClientLogin HTTP/1.0
Content-type: application/x-www-form-urlencoded

accountType=HOSTED_OR_GOOGLE&Email=__EMAIL__&Passwd=__PASSWD__
&service=finance&source=yken.org-learningGoogleAPI-0.1

Replace __EMAIL__ and __PASSWD__ with appropriate value. When the script is finished, you will have the relevant portfolio information saved in the “portfolio” file.

Detailed satellite imagery of Slovak Republic on Google Earth was very limited until recently. Only the country’s capital Bratislava and a few more other regions were covered with detailed photographs, dated to summer of year 2005 or earlier. For detailed satellite imagery of the entire country, users would turn to maps on ATLAS.sk, a project which aspires to be a leader in localization services in Slovakia.

This has changed recently as detailed coverage of the entire country was added on Google Earth and Google Maps, although not in such great detail as observed on previously existing detailed photographs. Previously existing detailed imagery remained the same, with no update.

A quick comparison of satellite imagery on Google Earth and ATLAS reveals that while ATLAS offers much more detailed imagery (50 cm / px), the imagery on Google is more recent. I zoomed in on a site where the largest highway crossing in the country is being build, west of city of Prešov. ATLAS photograph (top) reveals an untouched, old crossroad, while the image on Google already shows signs of work, which began in April 2008 (below). Geographic coordinates: 48°59′53.24″N, 1°12′11.29″E

Update, 5 Oct 2008: It appears that for entire region of Slovakia, Google switched to Eurosense/Geodis imagery data, the same as used by ATLAS. This blog post is hereby not valid anymore.

Update, 19 Oct 2008: Recently, ATLAS made available the updated Eurosense/Geodis imagery for Bratislava, dated to April 2007, the same resolution.

Not that I would follow “the search industry leader” steps too closely, yet one thing I was happy to notice recently: Prešov, the Eastern Slovakian town where I was born, got updated on Google Maps and so was whole of Slovakia and some other CEE countries. It appears that Google had published the 2007.1 TeleAtlas data with the detailed street coverage available for some new CEE regions, some advanced details (such as POIs) are however still missing.

I compared the Google Maps version with the most recent version of proprietary CEE Maps available for TomTom devices (version 6.75) – both Google and TomTom maps of Slovakia are the same, apparently based on 2007.1 TeleAtlas data (including all the mistakes). Google Earth has the same update, the countdown now started for the detailed satellite images coverage…