Repository navigation
Conversation
…n area When several coordinate operations connect two coordinate reference systems, the operation was chosen without an area of interest. A national operation then ranks before a more accurate regional one, even when the regional grid file is available, e.g. a gridless Helmert transformation instead of the HeTA2010 grid for DHDN to ETRS89 in Hessen. The new provider option transformationArea (a bounding box in CRS84) is passed to the operation selection for all transformations of the provider, so the most accurate operation whose area of use contains the box is used. Without the option the selection is unchanged. CrsTransformerFactory gets an overload with an area of interest and a view that applies an area to all transformers; transformers are cached per area. A box that covers the whole world selects like no box.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When several coordinate operations connect two coordinate reference systems, the operation was chosen without an area of interest. A national operation then ranks before a more accurate regional one, even when the regional grid file is available, e.g. a gridless Helmert transformation instead of the HeTA2010 grid for DHDN to ETRS89 in Hessen.
The new provider option transformationArea (a bounding box in CRS84) is passed to the operation selection for all transformations of the provider, so the most accurate operation whose area of use contains the box is used. Without the option the selection is unchanged.
The box has to lie completely within the area of use of the intended transformation. If it extends beyond it, even by a few hundredths of a degree, a less accurate transformation that covers the whole box is selected instead. For this reason, the spatial extent of the data, of an API or of a provider is often not suitable: for a dataset that covers the region of a regional transformation completely, the extent usually extends slightly beyond its area of use, for example because of features on the boundary, or because the extent of data stored in a projected coordinate reference system becomes larger when it is converted to CRS84.
CrsTransformerFactory gets an overload with an area of interest and a view that applies an area to all transformers; transformers are cached per area. A box that covers the whole world selects like no box.