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

   
   ## Did you read the Contributor Guide?
   
   - Yes, I have read [Contributor 
Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and 
[Contributor Development 
Guide](https://sedona.apache.org/latest-snapshot/community/develop/)
   
   ## Is this PR related to a JIRA ticket?
   
   - Yes, the URL of the associated JIRA ticket is 
https://issues.apache.org/jira/browse/SEDONA-269. The PR name follows the 
format `[SEDONA-269] my subject`.
   
   ## What changes were proposed in this PR?
   
   1. Add a new built-in data source called `raster` designed for writing 
rasters
   2. This raster data source takes 2 options
        - `rasterType`: this can be any supported raster types. Currently, we 
support `geotiff` and `arcgrid`
        - optional `pathField` which indicates each raster file name. If not 
given, it will use UUID as the name of each raster
        - Raster name is an quite important field as many libraries need raster 
file names for additional information.
   3. Move raster logics from `io` to `io.raster`. 
   
   The future plan of Sedona raster data sources:
   
   1. We will deprecate the current Sedona built-in `geotiff` data source in 
`1.4.1` (around 1 month from now) as it is not convenient for our upcoming 
raster operations and completely remove it in `1.5.0` (I guess around 4 months 
from now). To make this happen, a few other PRs that bridge Array[Double] and 
RasterUDT must be made. My idea is to completely get rid of Array[Double] and 
migrate Array[Double] based RS functions to RasterUDT environment. But let's 
see.
   2. With this PR in place,  we will start to use `binaryFile` data source and 
`RS_FromXXX` for reading rasters and `raster` data source for writing rasters. 
This gives us much more flexibility and introduces opportunities for brining a 
flurry of new raster functions.
   
   ## How was this patch tested?
   
   Added new unit tests.
   
   ## 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/master/pom.xml#L29) in since 
`vX.Y.Z` format.
   


-- 
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