Stay on the world when transforming coords.

Instead of a transform that results in +/- Infinity northing, we can constrain the results to be within the world bounds.
Filter.v1 methods need to be available when using Filter writers

Format classes that define member methods need to be mixed into other
format classes that use their writers. In this case, methods from
Filter.v1 were missing so a test for Format.WPSExecute failed.
Merge pull request #747 from ahocevar/wpsexecute-mixin

Filter.v1 methods need to be available when using Filter writers. r=@bartvde
Making OpenLayers play well with Bootstrap

Bootstrap CSS sets the max-width for images to 100%.  This makes it so
OpenLayers maps don't render (the layer container has 0 width, so all images
are given the same).  Even if our layer container had a more sensible width
(e.g. 100% of the viewport), we would still have issues with tiles that are
larger than the viewport.

Since the OpenLayers stylesheet may be loaded before or after bootstrap.css,
we should use !important when setting the max-width to none for images we
control.
Merge pull request #755 from tschaub/bootstrap-css

Making OpenLayers play well with Bootstrap
Make sure config.headers does not overwrite DEFAULT_CONFIG.headers in OpenLayers.Request.issue
Merge pull request #757 from bartvde/ajax

make sure config.headers does not overwrite DEFAULT_CONFIG.headers in OpenLayers.Request.issue (r=@ahocevar)
Merge pull request #435 from tschaub/kind-transform

Stay on the world when transforming coords.
Correct handling of 0 and Infinity ScaleHint

minScale and maxScale values of 0 and Infinity do not make sense in
OpenLayers, but they are used in WMS GetCapabilities 1.1.1 to indicate
that there is no minScale or maxScale restriction. Assuming that the
capability values for minScale and maxScale are passed as config options
to a WMS layer, it is better to not set minScale and maxScale when 0 or
Infinity are found in the ScaleHint.
Fix exporting empty vector layers to OWSContext.

When a vector layer is exported to an OWSContext document, we throw an
exception when the layer contains no features, and the geometries are to be
exported inside of an InlineGeometry-element.

This commit fixes this behaviour by exporting sth. like this in such cases:

<Layer name="vector" hidden="0">i
  <ows:Title xmlns:ows="http://www.opengis.net/ows"/>
  <InlineGeometry/>
</Layer>
Reuse variable, thanks @bartvde.
Merge pull request #761 from marcjansen/owsc-inlinegeometry

Fix exporting empty vector layers to OWSContext (p=me,@chrismayer;r=@bartvde).
parse annotation from WFS DescribeFeatureType schemas
remove JSON parsing from format, applications should handle this, as suggested by @ahocevar
appinfo can be specified multiple times, so use an array instead thanks @ahocevar
documentation is also an array, and lang is optional thanks @ahocevar for the catch
Documenting ScaleHint parsing, as suggested by @marcjansen
Merge pull request #760 from ahocevar/wmscaps-scalehint

Correct handling of 0 and Infinity ScaleHint. r=@marcjansen
Merge pull request #762 from bartvde/schema

parse annotation from WFS DescribeFeatureType schemas (r=@ahocevar)
make sure we can have multiple feature ids in InsertResults