Make decimal places of numeric values in GetFeatureInfo for cover configurable #1395
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR extends the GetFeatureInfo configuration and adds the new attribute
decimalPlaces
.The intended use-case is to request a fixed number of decimal digits on numerical data extracted from coverage data.
On coverage (raster) data, feature info gets sampled or aggregated, so that it is not unusual to have many decimal digits, which can lead to a false interpretation of accuracy.
Note on MapOptions: During the integration of the changes into the current
main
the remaining uses of MapOptions constructors was cleaned up to use the previously introducedMapOptions.Builder
.