Hi,
2 identical configured geoserver (2.4.3) instances return different accuracy of geometry when reprojecting from native EPSG:31256 to EPSG:4326.
Both seperate geoserver instances have identical GEOSERVER_DATA_DIR and Geoserver binaries through RPM-deployment
So I don't know why output is different. Also numberOfDeciamls is not implemented for JSON output in WFS-1.1.0
url-syntax: geoserver/ows?service=WFS&request=GetFeature&version=1.1.0&typeName=vienna:myFeatureTyp&srsName=EPSG:4326&maxFeatures=1&outputFormat=json
Geoserver A returns: 16.338768648508466,48.17213508918381
Geoserver B returns: 16.33876864850847 ,48.17213508918381
Does anyone have a clue what could cause this behaviour?
Cheers Rudi
On Tue, Apr 8, 2014 at 10:39 AM, Hochmeister Rudolf <
rudolf.hochmeister@anonymised.com> wrote:
Hi,
2 identical configured geoserver (2.4.3) instances return different
accuracy of geometry when reprojecting from native EPSG:31256 to EPSG:4326.
Both seperate geoserver instances have identical GEOSERVER_DATA_DIR and
Geoserver binaries through RPM-deployment
So I don't know why output is different. Also numberOfDeciamls is not
implemented for JSON output in WFS-1.1.0
url-syntax:
geoserver/ows?service=WFS&request=GetFeature&version=1.1.0&typeName=vienna:myFeatureTyp&srsName=EPSG:4326&maxFeatures=1&outputFormat=json
Geoserver A returns: 16.338768648508466,48.17213508918381
Geoserver B returns: 16.33876864850847 ,48.17213508918381
Does anyone have a clue what could cause this behaviour?
No idea... but the difference is roughly 0.4 nanometers (making the rough
assumption that one degree = 110km) ...
does it matter? 
Cheers
Andrea
--
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------