jesspav opened a new pull request, #2053:
URL: https://github.com/apache/sedona/pull/2053

   Work-In Progress
   
   There are still a few outstanding issues here:
   * Apache SIS sometimes throwing for missing grid files, that should not be 
there.  Working with Apache SIS folks to get some clarity on what is happening, 
but for now this means that a test fails when the EPSG dataset is there.
   * We have lost the basic validation of the transform.  If a point is out of 
the scope for the transform it may have NaNs or other unexpected numbers and 
fail silently.  The best practice for a check for this is not working.  Need to 
work with Apache SIS to understand why.
   * Have not validated the embedded database that we are recommending in the 
docs.  All testing was with the derby ESPG dataset to date.  Need to make sure 
that works.
   
   
   
   
   ## Did you read the Contributor Guide?
   
   - Yes, I have read the [Contributor 
Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor 
Development Guide](https://sedona.apache.org/latest/community/develop/)
   
   
   ## Is this PR related to a ticket?
   
   - Yes, and the PR name follows the format `[SEDONA-XXX] my subject`.
   - Yes, and the PR name follows the format `[GH-XXX] my subject`. Closes 
#<issue_number>
   
   - No:
     - this is a documentation update. The PR name follows the format `[DOCS] 
my subject`
     - this is a CI update. The PR name follows the format `[CI] my subject`
   
   ## What changes were proposed in this PR?
   
   
   ## How was this patch tested?
   
   
   
   
   ## Did this PR include necessary documentation updates?
   
   - Yes, I am adding a new API. I am using the [current SNAPSHOT version 
number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29)
 in `vX.Y.Z` format.
   - Yes, I have updated the documentation.
   - No, this PR does not affect any public API so no need to change the 
documentation.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to