I have a REST service that returns shapes as json. The shapes represent various natural features.
The problem is the precision of the coordinates. Currently, nine decimal places of precision are returned for each vertex. For these features, that level of precision is ridiculous and one or two places is more than adequate.
As mentioned, the REST service is returning nine decimal places. The database also stores nine places.
I'm not sure of this can easily be controlled at the service level or if I can do this at the SDE level. At this point, I just want to control the number of decimal places returned for the vertices and it doesn't matter where I make the change. If I need to create a duplicate feature class that contains reduced precision and access it with another service, I'm okay with that.
أكثر...
The problem is the precision of the coordinates. Currently, nine decimal places of precision are returned for each vertex. For these features, that level of precision is ridiculous and one or two places is more than adequate.
As mentioned, the REST service is returning nine decimal places. The database also stores nine places.
I'm not sure of this can easily be controlled at the service level or if I can do this at the SDE level. At this point, I just want to control the number of decimal places returned for the vertices and it doesn't matter where I make the change. If I need to create a duplicate feature class that contains reduced precision and access it with another service, I'm okay with that.
أكثر...