REST API does not deliver the correct coordinate value after the decimal.

[StefanP__Jung]

When accessing a feature via REST API I get different results to the real coordinates. The feature is saved @ArcSDE with a resolution of 1000, but the REST API result has more numbers after the decimal. So there might be a problem of displaying the double value?

Sample SQL Statement:

SELECT sde.st_astext(g.shape) as wkt  FROM geodata g  WHERE gisid in (1234)

Result:

POLYGON  (( 818052.36380000 5742316.96420000,  ...)

When accessing the same feature class via REST API Query from ArcGIS Server i will get:

[       [        818052.3638000004,        5742316.9641999993       ], ... ]

The feature class has a correct topology but when accessing one feature via ST_GEOMETRY and a neighbour feature via REST API the topology is not correct any more.

Is this a general problem with ArcGIS Server REST API or only with ArcGIS Server for Java? Maybe it is a localization problem, any Idea?

Reference to the ArcSDE Post

Stefan

System:
- ArcGIS Server Java 10 SP 2 on Windows 2008 english
- ArcSDE 10 SP 2, using direct connect for all features @ mxd
- Oracle 11.2.0.3 on Windows 2008 german

[StefanP__Jung · Accepted solution]

Esri was able to reproduce this issue:

NIM078128 REST JSON geometry query returns incorrect level of precision.

Stefan