Segment distance calculation fails when modifying points

By providing a segment even for points, we have less distinction
points between points and other geometry types, and are able to
do the segment distance calculation also for points.
srsName should be optional in BBOX
initial version of the WFS parser for 1.0.0 and 1.1.0
ability to write out PropertyNames in a GetFeature request
starting to add tests for WFS 1.1.0

make sure we don't override the wfs:FeatureCollection reader with the one from GML
ability to read boundedBy from FeatureCollection
need the ability to set axisOrientation

We need to be able to set axisOrientation on the underlying GML parser of the Filter subparser of ol.parser.WFS*, also only options and no properties on the instance anymore
write out GetFeature in WFS 1.1
port over another WFS 1.1 testcase
ability to parse a FeatureCollection

The trick here was to delete featureNS so autoConfig would kick in
more tests and typedefs.

Once feature editing is more stable, this format can be extended with Update, Delete and Insert
same solution for axisOrientation as for WFS 1.1.0
move the typedefs out of objectliterals
rename this.gml_ to this.gmlParser_
Merge pull request #1160 from bartvde/wfst

Add parser for WFS (r=@ahocevar)
Return for getFeatureInfoForPixel

In b8a9aeb14ed6089d9d676c7e8682f0db5a6d5304 a return was added to `ol.renderer.Layer.prototype.getFeatureInfoForPixel`.  The `ol.renderer.canvas.VectorLayer.prototype.getFeatureInfoForPixel` method needs the same.
Merge pull request #1311 from ahocevar/modify-points

Segment distance calculation fails when modifying points
Merge pull request #1315 from tschaub/gfi-return

Return for getFeatureInfoForPixel.
Add ol.extent.extendXY
Fix order of arguments to ol.extent.createOrUpdate