Not that long ago Google updated the Terms of Service on Google Maps API – I guess mainly in responce to issues brought up on the Mail group, and elsewhere. As a result of that edit there where many concerns raised (and more)- and a further edit was made. (note, only linked to some of the blogs etc – follow links to read more) This was over a week ago, but due to non online commitments haven’t really had a time to follow this up. You can read my early reaction here, which has been edited in to Mikes post.

11. Licenses from You to Google.

11.1 Content License. Google claims no ownership over Your Content, and You retain copyright and any other rights you already hold in Your Content. By submitting, posting or displaying Your Content in the Service, you give Google a perpetual, irrevocable, worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publicly perform, publicly display and distribute Your Content through the Service and as search results through Google Services. This license is solely for the purpose of enabling Google to operate the Service, to promote the Service (including through public presentations), and to index and serve such content as search results through Google Services. If you are unable or unwilling to provide such a license to Your Content, please see the FAQ for information on configuring your Maps API Implementation to opt out.

11.2 Brand Features License. You grant to Google a nontransferable, nonexclusive license during the Term to use Your Brand Features to advertise that you are using the Service.

11.3 Authority to Grant Licenses. You confirm and warrant to Google that you have all the rights, power and authority necessary to grant the above licenses.

To be honest still unsure how I feel about this section, and finding it very hard to vocalise (well to put to pixels) the concerns. I certain its not compatible with a number of situations where the Maps would otherwise be ideal, but that I guess is real life – just need to move on an find something that is more suitable. But its still gauling to have invested so much in Google Maps API to have it all disappear in puff of legal smoke, I guess its now going to be“Once Burnt, Twice Shy” as they say.

How can I opt out of including my content in Google search results?
To remove your page or site from search results, follow the instructions provided in our webmaster help center. If we enable indexing of any content that is a part of your Maps API implementation, we will provide updated instructions to opt out of including that content in search results.

This seems to equate ‘indexing’ with ‘licence’.

Now I kinda understand why Google are doing this, they want to legalise the crawling they are doing – so they have a get out that the data has been licensed to them specifically.

So does that mean if we don’t agree to the licence – the data wont be crawled and indexed? But we do want content to be indexed – previously we’ve never agreed by allowing content to be crawled we giving a licence to that data.

… so with Geograph at least – I cant grant the licence – but I cant use the elusive ‘opt out’ (boils down to robots.txt I guess), as I do want the content to be indexed. So can Geograph use the Google Maps API or not? I still can’t see how it can – if it did it would be contravening the TOS of the API (cant confirm as per 11.3), and/or violating the Creative Commons licence (see section 4.a. of the legal code, “You may not sublicense the Work.” which is the most succinct expression of the issue).

Another silly issue in all of this, users displaying Geograph content on Google Maps website itself (eg via KML files) are basically agreeing to the same terms (by way of here and here [see section 11]). So the same issue displaying such content is not actually abiding by the terms and licence. And by providing links to Google Maps we inciting users to do this :p – but that is a step away from doing it wholesale on the website itself?

* sorry this has taken so long, truly sorry for the inconvenience. In retrospect maybe was a bit hasty – but couldnt allow the licence to data been entrusted with the be undermined.

/me wanders off to play (but dont have much time at the moment )

but before I go, I note that the api doesn’t appear to offer KML output :p

… unless of course the actual GeoSearch API is something bigger!

update: try it out:

http://www.nearby.org.uk/google/geoweb_explorer.php

Not much to look at, but does show the json in a slightly easier to read format. Of course need to make a Maps API based map to try it out, but not tonight… (but did get as far as KML output – with source code!)

update2: Its been formally announced! (also if you find the ‘blended’ doesnt return results you expect, see this thread

Flash Earth Layer

Conclusions

1. Google Earth does request a link for the initial view on startup – that point in the Atlantic.
2. I guess North American installs have two slightly different default placemarks; has it changed, or maybe Canada gets a different one?
3. But that doesnt explain the lines from there – people must have their links set to periodically refresh?
4. Germany likes FlashEarth (or rather people like looking at Germany with FlashEarth link enabled)
5. Many people leave the links open even when not in use – e.g. the British Isles links show worldwide usage, notably over Russia.
6. MGRS notably has high usage in two areas.
7. The Far east likes to know what direction they facing.

Update: In a total forehead slapping momont realised these unprojected whole world images, are exactly what is used in GroundOverlays, so the the pages now include links to view the higher resolution images directly in Google Earth, duh!

Example: View In Google Earth (don’t forget to try adjusting the tranparency slider!) [Update, to fix broken link, sorry!]

So what is the response to this type of thing (and I have no idea of the identity of users)?

1. Blacklist at firewall level – effectively cutting them off from using nearby ever again.
2. Blacklist them from that feature permanently
3. Impose a temporally ban
4. Add a throttling to the service for everyone, such as a quota or rate limiting – difficult to get the sweat spot
5. Google Earth offers <maxSessionLength> which could be used to curtail the long term effect, but this would have a minor effect on legitimate users
6. similar to last but only start adding it once they trigger some limit

So far (and only in a handful of cases) have done either 1 or 2. In the example that has triggered this post have done 1. but might change it to 3.

(the api and coordinate converter have their own dynamic limit, essentially 4. )

Updating the documentation noticed the API was last updated in 2005 – gulp, how time flies! Anyway as a celebration have upped the throttling on the API, now three times the previous limit. Running on much improved hardware than when it was launched so maybe the limit can be tweaked even more, will run some analysis of its impact – it already seems the API is a minor part of the overall load on the server – particularly against the Google Earth layers.

Open in Google Earth

Hopefully needless to say the map inside the balloon is static and non draggable.

Update to clarify: You get to draw 1,000 maps daily, which is probably plenty, but go over that and the maps will stop working for you.

Update: as alluded to in the official post, you can use the static API to load a quick map, while the rest of the page loads, then at the last minute change it into a dynamic map. A series of demos showing various ways of lazy loading!

So to that end of created a whole bunch of demos based around the flexible indexing it provides, location based searching is even possible!

At the most basic is simple text based search, one point of note, there is no pagination, simply add more keywords (including negative) or grid references to refine the selection.

Next is a ‘auto-complete’ style image finder, this is designed to find ‘that image’ quickly, in a similar way to the above but shows the results in a autocomplete box immediately!

A refinement of the first is search with location, this allows you limit the search to near a particular Grid References – this is particully cool in that there is Sphinx powered auto-complete for place names for finding GRs. (a real auto-complete not a like the search in the previous one pretending to be one)

This is all building towards the Illustrator demo. Which from a block of text attempts to find relevent images. The idea is that a (geolocated) news article, walking route, place description and such could be automatically have relevent(ish) images shown. (an example demo here)

(a few more ‘toys’ can be found in GeographTools!)…. Try them out and let me know how you get on…

I have learnt a lot about search indexing from this, including how to perform location searches in the index (I know latest versions of sphinx include a lat/long based geosearch – but I think this r-tree method in text has better scalability), and how to create an autocomplete function with sphinx. If anybody is interested in these, they will eventually make it into the geograph codebase, or let me know and I might make a separate post.

Interestingly (huh?), it was actually creating a ‘autocomplete’ textbox for finding trigpoints (which included the forerunner to the sphinx location search in but implemented in mysql), is actually what inspired me to actually go the trouble if figuring out how to install Sphinx on linux, which I have been interested in for a long time! – that is also now sphinx powered for text searches

As a side note have now reached the ‘linux sysadmin’ level that I can compile it on Geographes servers, yay! But I do worry for the sanity of others due to this (a little knowledge is a dangerous thing!)

1. The zoom is a LOT closer matched, this is thanks to the inspiring formula: $z = (-1.4956 * log($range/1000) + 16.529; (yes really!); brought to you by the wonder of plotting a graph in Excel, creating a trendline, turning on the formula display option. Probably could get an even better match with more patience, but probably about as good as it going to get really.
2. Removed the title and the directions links, makes the balloon looks a bit nicer, couldn’t get it to go transparent for me tho… suggestions welcome.
3. When the network link is now a folder so can choose the size of your popup The previous version is now the ‘medium’ one.

Though the magic of the web, you get 1) and 2) automatically, if want 3) just download it again:

Open in Google Earth (Required: GE 4.2 Windows)

Thanks again to everyone involved.

Has Google taken over the Royal Mail too now?

(the official announcement)

Update Nov ’07: … well it seems the postcodes was only a dream, and have now been withdrawn! Time will tell if this can be rectified. Ho hum…

Update Dec ’07: … the ToU have now been updated to clarify that the (http) geocoder is for the express use of ‘pre-caching’ geocodes for use on a Google Maps API map. (I’ve also clarified the above paragraph in regards to this). This also prevents some interesting uses, eg store locators that work before a map is shown (but an intereactive one with a map should be fine), which is a shame.

And it turns out they are really easy to code for been based on Google Gadgets (which I haven’t used before) and Google Maps API (which I have ), but I also congratulate Google on including in the package ‘Developer’ mapplets that make developing relatively painless.

Anyway onto the demos, just visit http://maps.google.com/preview (it’s a Developer orientated demo for the moment), click the ‘Mapplets’ tab, goto ‘Add Content’ and see what takes your fancy. To try out my (very humble!) demo, use the ‘Add by URL’ and paste in the following URL: http://www.geograph.org.uk/stuff/gmapplet0.xml

(more about maplets in the post linked in the first paragraph!)