diff --git a/doc/authors.txt b/authors.txt
similarity index 100%
rename from doc/authors.txt
rename to authors.txt
diff --git a/build/license.txt b/build/license.txt
index 38898679e1..9c7635d802 100644
--- a/build/license.txt
+++ b/build/license.txt
@@ -2,14 +2,14 @@
OpenLayers.js -- OpenLayers Map Viewer Library
- Copyright 2005-2011 OpenLayers Contributors, released under the FreeBSD
- license. Please see http://svn.openlayers.org/trunk/openlayers/license.txt
- for the full text of the license.
+ Copyright (c) 2006-2012 by OpenLayers Contributors
+ Published under the 2-clause BSD license.
+ See http://openlayers.org/dev/license.txt for the full text of the license, and http://openlayers.org/dev/authors.txt for full list of contributors.
Includes compressed code under the following licenses:
- (For uncompressed versions of the code used please see the
- OpenLayers SVN repository: )
+ (For uncompressed versions of the code used, please see the
+ OpenLayers Github repository: )
*/
diff --git a/doc/customization b/doc/customization
deleted file mode 100644
index f4b5b98aa9..0000000000
--- a/doc/customization
+++ /dev/null
@@ -1,49 +0,0 @@
-Customizing OpenLayers
-======================
-
-OpenLayers is designed to fit many needs -- fitting in alongside all kinds of
-various applications which are currently in use.
-
-Currently, OpenLayers supports a 'theme' option when creating a map. This
-theme option allows you to specify the location of a CSS theme which should
-be included.
-
-A default theme is available as an example in the theme/ directory: the setup
-is:
-
- * theme/
- * theme/default/
- * theme/default/style.css
- * theme/default/img/
-
-Currently, the OpenLayers code does not support class names, and therefore,
-it is not possible to control many aspects of OpenLayers code with CSS
-classes. However, with this framework in place, we expect to invest time
-to make existing features and new features use the CSS theming framework
-where apropriate.
-
-
-Class Naming
-============
-Elements should have class names which are descriptive of the Javascript
-class from which they come. For example, the main layer switcher element
-in the OpenLayers.Control.LayerSwitcher would be classed:
-
- olControlLayerSwitcher
-
-This would allow users to add to their style.css class in their theme,
-changing, for example:
-
-::
-
- .olControlLayerSwitcher input {
- width:10px;
- }
-
-Sub elements of a particular control can add to the class name:
-
-::
-
- .olControlLayerSwitcherBaseLabel {
- color: red;
- }
diff --git a/doc/readme.txt b/doc/readme.txt
deleted file mode 100644
index d02540af67..0000000000
--- a/doc/readme.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-Automatically generated OpenLayers API documentation is online:
-
- http://dev.openlayers.org/apidocs
-
-More information on documentation is available from:
-
- http://trac.openlayers.org/wiki/Documentation
diff --git a/examples/data/tazdem.tiff b/examples/data/tazdem.tiff
new file mode 100644
index 0000000000..4f5840268f
Binary files /dev/null and b/examples/data/tazdem.tiff differ
diff --git a/examples/fusiontables.html b/examples/fusiontables.html
new file mode 100644
index 0000000000..8c75d6c1a3
--- /dev/null
+++ b/examples/fusiontables.html
@@ -0,0 +1,32 @@
+
+
+
+ OpenLayers Example For Reading Features From Google Fusion Tables
+
+
+
+
+
+
+
+
+
Reading Features From A Google Fusion Tables Table
+
+ protocol, script, fusion tables
+
+
+ Demonstrates how, with a custom read method, the script protocol and GeoJSON format can be used to read features stored in a table on Google Fusion Tables.
+
+
+
+
+ Google Fusion Tables can be used to store features, and access them using SQL-type commands over HTTP. Tables can be made public, in which case no authorization is needed to read them. Geometries can be stored in Location columns in KML format. The default output is a CSV dump of each table row/column selected. Multi-line CSV files are not easy to parse in Javascript, but by adding a jsonCallback parameter to the HTTP command, the output will be a JSON object with the geometry as GeoJSON. With a custom read method, this example parses the geometry for each row, storing the other columns as feature attributes. You can of course add a 'where' clause to the SQL statement or change the column names to limit the data retrieved. Point geometries can also be stored in Latitude/Longitude columns, and the script could easily be modified to use those instead.
+
Uses a BBOX strategy to request features within a bounding box.
@@ -67,6 +97,10 @@
previously requested data bounds are invalidated (by browsing to
some area not covered by those bounds), another request for data
is issued.