release 1.0.0 beta 2

30/05/2016 : 1.0.0 beta2 release of geoportal access library

Summary

This is a minor bug fix version.

Anyway some interface changes have to be noticed :

• Gp.Services.route() : #5, #7

provideGeometry option is replaced by geometryInIntsructions instead. When it is set to true, the routeGeometry property of Gp.Services.RouteResponse response object is null and the route geometry can be found, instruction by instruction, in the new geometry property of Gp.Services.Route.RouteInstruction object.

• Gp.Services.reverseGeocode() : #10

The default coordinate system for position parameter is CRS:84 (and no longer EPSG:4326) : this means that position.x holds the longitude and position.y holds the latitude : in the request and also in the response (see : Gp.Services.Geocode.GeocodedLocation). When srs is set to "EPSG:4326", position.x will hold the latitupe and position.y the longitude.

• All Gp.Services methods : #1

A new callbackSuffix parameter is available which allows developers to provide a customised callback name for JSONP services invocations which will be in a "callback[callbackSuffix]" form. If not used. The callback suffix will be automatically generated on a timestamp basis.

Complete ChangeLog

#1 - Erreur du web service pour autoComplete qui retourne un XML au lieu d'un JSON
#2 - Erreur Internet Explorer
#3 - Erreur sur les "CadastralParcels"
#4 - Correction documentation suite à faute de typo
#5 - Route service : avoir la geometrie des instructions séparément de la géométrie globale
#6 - JSONP : nettoyage de la balise script lors d'un timeout
#7 - gestion de la simplification des tronçons lors du calcul d'itineraire…
#8 - Route service : erreur lorsque l'une des coordonnées est nulle
#9 - enable input coordinates to equal zero (but not to be null or undefined)
#10 - geographical coordinates management

Thanks to @ThomasG77 for his contribution on #4.