You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I save a tile from a RasterFrameLayer as GeoTiff, I would expect that the size of the pixel would be the same for the output GeoTiff than the RasterFRameLayer.
Current situation
When I use a filter condition to keep only a tile from a RasterFrameLayer and I write it as GeoTiff, the resulting GeoTiff has the number of pixels than the original image instead of the number of pixels of the tile.
* fix/366:
Added abiltiy to pass a crs specification string to `rf_crs`.
Reworked TestEnvironment to make it easier to override SparkContext settings.
Add rf_mask unit test in python, import geomesa types with module import
Bumped development version.
0.8.2 release prep.
Updated release notes.
IT regression fixes.
Fixed handling of aggregate extent and image size on geotiff write.
Unit test reproducing locationtech#360.
Pass kwargs in python create_rf_spark_session to spark conf
Tweaks to RasterSource-related code for easier extendability.
Doc fixes missing @ref: prefixes.
Doc fixes missing @ref: prefixes.
Zonal stats page and other refactoring (locationtech#342)
Bumped Spark version to 2.3.4
Added rasterio and decartes.
Display-oriented tweaks to docs
Expected situation
When I save a tile from a
RasterFrameLayer
asGeoTiff
, I would expect that the size of the pixel would be the same for the outputGeoTiff
than theRasterFRameLayer
.Current situation
When I use a filter condition to keep only a tile from a
RasterFrameLayer
and I write it asGeoTiff
, the resultingGeoTiff
has the number of pixels than the original image instead of the number of pixels of the tile.How to reproduce
See: https://gist.github.com/jdenisgiguere/980ca9f28d5ded5da0d30c39fea17e2f based on code provided by @metasim on gitter.im.
The text was updated successfully, but these errors were encountered: