Harmonized dimension estimation in OracleGeometryWriter #14
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.
There was an inconsistency in getting the correct dimension from th e geomtry to be transformed to SdoGeometry. One was based on the Coordinate property and one on the coordinatesequence dimension. It seems that internally all coordinates are 3D now, even for 2D (Z is NaN then). This lead to incorrect SdoGeometry having ElemInfo telling 2D and an ordinate array containing 3 ordinates (including NaN).
The pull request fixes this by defining the dimension prior to conversion based on coordinate property and storing it in private variable in the Writer instance.
fixes #11