ffi-gdal 1.0.1 → 1.0.3

data/Changelog-0.x.md

@@ -1,9 +1,11 @@
 # Changelog: 0.x
 
-Changes listed in this file (somewhat) reflect changes throughout 0.x-1.0.0-beta releases. The
-1.0.0-beta\* releases ended up with many unexpected changes, often leading to API changes that didn't
-get documented. Instead of keeping a mish-mash of valid and invalid change entries in the proper
-[Changelog](Changelog.md), we've moved those here, as they were just prior to the 1.0.0 release.
+Changes listed in this file (somewhat) reflect changes throughout 0.x-1.0.0-beta
+releases. The 1.0.0-beta\* releases ended up with many unexpected changes, often
+leading to API changes that didn't get documented. Instead of keeping a
+mish-mash of valid and invalid change entries in the proper
+[Changelog](Changelog.md), we've moved those here, as they were just prior to
+the 1.0.0 release.
 
 ---
 
@@ -13,7 +15,8 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 - Added `.release` class method for many `GDAL` types.
 - Added `GDAL::Dataset.copy_whole_raster`.
-- Added exception messages for `OGR` methods that raised using `OGR::ErrorHandling`.
+- Added exception messages for `OGR` methods that raised using
+  `OGR::ErrorHandling`.
 - Added alias for `OGR::SpatialReferenceMixins::Exporters#to_gml` to `to_xml`.
 - Wrapped `OGR_G_ExportToIsoWkt` and `OGR_G_ExportToJsonEx`.
 - Merged `ffi-gdal-extensions` gem back to `ffi-gdal`.
@@ -25,10 +28,10 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 #### GDAL
 
-- _BREAKING_: `GDAL::RasterBand#no_data_value=` now accepts `nil` to allow unsetting the NODATA
-  value.
-- _BREAKING_: Many methods were not communicating errors `CPLErr` back to the caller; these now
-  raise on `CE_Failure` or `CE_Fatal`:
+- _BREAKING_: `GDAL::RasterBand#no_data_value=` now accepts `nil` to allow
+  unsetting the NODATA value.
+- _BREAKING_: Many methods were not communicating errors `CPLErr` back to the
+  caller; these now raise on `CE_Failure` or `CE_Fatal`:
   - `GDAL::Dataset#add_band`
   - `GDAL::Dataset#build_overviews`
   - `GDAL::Dataset#create_mask_band`
@@ -60,30 +63,37 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
   - `GDAL::RasterBand#write_block`
 - `GDAL` errors that return `CPLE_AppDefined` now raise `GDAL::Error`.
 - `GDAL` errors now truncate less of the backtrace.
-- `GDAL::RasterBand#scale` and `#offset` now return the `Float` value and raise on a failed call
-  instead of returning a `Hash` with that info.
+- `GDAL::RasterBand#scale` and `#offset` now return the `Float` value and raise
+  on a failed call instead of returning a `Hash` with that info.
 
 #### OGR
 
-- _BREAKING_: `OGR::DataSource#copy_data_source` now raises instead of returning `nil` on a failure
-  to copy.
-- _BREAKING_: `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#set_utm`'s second param is
-  now a keyword arg, `north:` that defaults to `true` (like GDAL's default).
-- `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#set_towgs84`'s `z_distance` requires a
-  value internally, but was defaulted to `nil`; changed the default value to `0.0`.
-- _BREAKING_: `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#axis`'s `target_key` is
-  now required.
-- _BREAKING_: `OGR::CoordinateTransformation.new` raises a `GDAL:Error` instead of `OGR::Failure`.
-  In GDAL 3, the GDAL error handler kicks in when bad data is used to instantiate the
-  `CoordinateTranformation`. In < 3, the Ruby code checks the returned pointer and raises if it's
-  null. Now these raise the same exception.
-- _BREAKING_: `OGR::Driver.create_data_source` raises on failure instead of returning `nil`.
-- `OGR::SpatialReferenceMixins::Importers` now return `self` instead of the `OGR` error code
-  `Symbol`.
+- _BREAKING_: `OGR::DataSource#copy_data_source` now raises instead of returning
+  `nil` on a failure to copy.
+- _BREAKING_:
+  `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#set_utm`'s second
+  param is now a keyword arg, `north:` that defaults to `true` (like GDAL's
+  default).
+- `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#set_towgs84`'s
+  `z_distance` requires a value internally, but was defaulted to `nil`; changed
+  the default value to `0.0`.
+- _BREAKING_:
+  `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#axis`'s
+  `target_key` is now required.
+- _BREAKING_: `OGR::CoordinateTransformation.new` raises a `GDAL:Error` instead
+  of `OGR::Failure`. In GDAL 3, the GDAL error handler kicks in when bad data is
+  used to instantiate the `CoordinateTranformation`. In < 3, the Ruby code
+  checks the returned pointer and raises if it's null. Now these raise the same
+  exception.
+- _BREAKING_: `OGR::Driver.create_data_source` raises on failure instead of
+  returning `nil`.
+- `OGR::SpatialReferenceMixins::Importers` now return `self` instead of the
+  `OGR` error code `Symbol`.
 
 ### Fixed
 
-- [DEV-12827] Fixed lots of double-free crashes resulting from misuse of `FFI::Pointer#autorelease`:
+- [DEV-12827] Fixed lots of double-free crashes resulting from misuse of
+  `FFI::Pointer#autorelease`:
   - `GDAL::CPLErrorHandler#custom_handle`
   - `GDAL::ColorInterpretation.name`
   - `GDAL::ColorTable#clone`
@@ -125,12 +135,13 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 ### GDAL
 
-- `GDAL::RasterBand#no_data_value` uses `BigDecimal` for checking the returned float value.
+- `GDAL::RasterBand#no_data_value` uses `BigDecimal` for checking the returned
+  float value.
 
 #### OGR
 
-- [DEV-12827] Fixed a number of memory leaks where returned strings should be released using
-  `FFI::CPL::VSI.VSIFree()`:
+- [DEV-12827] Fixed a number of memory leaks where returned strings should be
+  released using `FFI::CPL::VSI.VSIFree()`:
   - `OGR::Geometry#to_gml`
   - `OGR::Geometry#to_kml`
   - `OGR::Geometry#to_geo_json`
@@ -142,52 +153,60 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
   - `OGR::SpatialReference#to_wkt`
   - `OGR::SpatialReference#to_pretty_wkt`
   - `OGR::SpatialReference#to_xml`
-- `OGR::SpatialReferenceMixins::Importers::ClassMethods#new_from_epsga` was incorrectly calling
-  `import_from_epsg` instead of `import_from_epsga`.
-- `OGR::SpatialReference.release` fixed to use `OSRRelease()` in order to avoid use-after-free.
-- `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#set_utm`'s internal call was expecting
-  an `int`, but was getting passed a `bool`.
-- `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#towgs84` now properly reads data out
-  of the internal C array.
-- `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#axis`: the `orientation` value in the
-  returned `Hash` wasn't calling a fully qualified module.
+- `OGR::SpatialReferenceMixins::Importers::ClassMethods#new_from_epsga` was
+  incorrectly calling `import_from_epsg` instead of `import_from_epsga`.
+- `OGR::SpatialReference.release` fixed to use `OSRRelease()` in order to avoid
+  use-after-free.
+- `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#set_utm`'s
+  internal call was expecting an `int`, but was getting passed a `bool`.
+- `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#towgs84` now
+  properly reads data out of the internal C array.
+- `OGR::SpatialReferenceMixins::CoordinateSystemGetterSetters#axis`: the
+  `orientation` value in the returned `Hash` wasn't calling a fully qualified
+  module.
 - `OGR::SpatialReferenceMixins::Exporters#to_xml` now actually works.
 
 ### Removed
 
 - [DEV-361] Move extension methods to ffi-gdal-extensions.
-- Removed attach_function to CPLURLGetValue and CPLURLAddKVP as they are not in GDAL 2.
+- Removed attach_function to CPLURLGetValue and CPLURLAddKVP as they are not in
+  GDAL 2.
 - `GDAL::MajorObject#description=`
 
 ## 1.0.0.beta16 / 2022-06-09
 
 ### Bug Fixes
 
-- [DEV-34269] Ensure `GDAL::RasterBandClassifier#equal_count_ranges` returns a range when only one is requested.
+- [DEV-34269] Ensure `GDAL::RasterBandClassifier#equal_count_ranges` returns a
+  range when only one is requested.
 
 ## 1.0.0.beta15 / 2022-05-12
 
 ### Improvements
 
-- [DEV-20059] Ensure `GDAL::RasterBandClassifier#equal_count_ranges` has a minimum spacing between breakpoints.
+- [DEV-20059] Ensure `GDAL::RasterBandClassifier#equal_count_ranges` has a
+  minimum spacing between breakpoints.
 
 ## 1.0.0.beta14 / 2022-05-06
 
 ### Bug Fixes
 
-- [DEV-34133] Don't URI.parse path in `GDAL::Dataset#initialize` and `OGR::DataSource#initialize`.
+- [DEV-34133] Don't URI.parse path in `GDAL::Dataset#initialize` and
+  `OGR::DataSource#initialize`.
 
 ## 1.0.0.beta13 / 2022-04-20
 
 ### Bug Fixes
 
-- [DEV-20247] Fix return value for `OGR::LayerMixins::Extensions#point_values` when no features are found.
+- [DEV-20247] Fix return value for `OGR::LayerMixins::Extensions#point_values`
+  when no features are found.
 
 ## 1.0.0.beta12 / 2021-06-07
 
 ### Removed
 
-- Removed `GDAL::MajorObject#description=`, as this shouldn't be called and causes problems.
+- Removed `GDAL::MajorObject#description=`, as this shouldn't be called and
+  causes problems.
 
 ### Bug Fixes
 
@@ -203,7 +222,8 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 ### Fixed
 
-- [DEV-7980] Ensure `OGR::Feature#field_as_string` returns a UTF-8 encoded String.
+- [DEV-7980] Ensure `OGR::Feature#field_as_string` returns a UTF-8 encoded
+  String.
 
 ## [1.0.0.beta9] - 2018-03-26
 
@@ -224,7 +244,8 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 ### Fixed
 
-- Ensure `GDAL::RasterBandMixinsIOExtensions#read_blocks_by_block` always yields an Array of pixels.
+- Ensure `GDAL::RasterBandMixinsIOExtensions#read_blocks_by_block` always yields
+  an Array of pixels.
 
 ## [1.0.0.beta7] - 2016-09-21
 
@@ -232,17 +253,20 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 #### GDAL
 
-- Added wrapper for GDALCreateAndReprojectImage in `gdal/dataset_mixins/warp_methods.rb`.
+- Added wrapper for GDALCreateAndReprojectImage in
+  `gdal/dataset_mixins/warp_methods.rb`.
 - Added `GDAL::Options.to_hash` to convert a pointer of options to a Ruby Hash.
 
 ### Changed
 
 #### GDAL
 
-- (BREAKING CHANGE) Additionally, changed `GDAL::DatasetMixins::WarpMethods#reproject_image`'s
-  `destination_spatial_reference` named param to `destination_projection` which takes a String of
-  WKT for a projection instead of an `OGR::SpatialReference`.
-- Return `nil` for missing NODATA values in `GDAL::RasterBand#no_data_value` and `#no_data_value=`.
+- (BREAKING CHANGE) Additionally, changed
+  `GDAL::DatasetMixins::WarpMethods#reproject_image`'s
+  `destination_spatial_reference` named param to `destination_projection` which
+  takes a String of WKT for a projection instead of an `OGR::SpatialReference`.
+- Return `nil` for missing NODATA values in `GDAL::RasterBand#no_data_value` and
+  `#no_data_value=`.
 
 ### Fixed
 
@@ -252,9 +276,10 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 #### GDAL
 
-- `GDAL::RasterBandMixins::IOExtensions#write_xy_narray` no longer duplicates data when blocks have
-  a remainder.
-- `GDAL::WarpOptions` should properly act as a wrapper for `FFI::GDAL::WarpOptions`.
+- `GDAL::RasterBandMixins::IOExtensions#write_xy_narray` no longer duplicates
+  data when blocks have a remainder.
+- `GDAL::WarpOptions` should properly act as a wrapper for
+  `FFI::GDAL::WarpOptions`.
 - `Updated extract methods to be compatible with latest `GDAL::Driver#create_dataset`.
 - `GDAL::MajorObject` now gets autoloaded.
 - Fix `GDAL::DatasetMixins::AlgorithmMethods` to use the right `FFI` module for
@@ -262,13 +287,15 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 #### OGR
 
-- [AGDEV-17357] Define constants from C using `const_set` instead of `class_eval`.
+- [AGDEV-17357] Define constants from C using `const_set` instead of
+  `class_eval`.
 - Fixed `OGR::GeometryTypes::Curve#points` (missing local variable).
 
 ### Removed
 
-- Removed all `#as_json` and `#to_json` definitions. They were out of date, not used, and sometimes
-  confusing (ex `OGR::Geometries#to_json` vs `#to_geo_json`).
+- Removed all `#as_json` and `#to_json` definitions. They were out of date, not
+  used, and sometimes confusing (ex `OGR::Geometries#to_json` vs
+  `#to_geo_json`).
 
 ## [1.0.0.beta6] - 2016-04-18
 
@@ -276,148 +303,172 @@ get documented. Instead of keeping a mish-mash of valid and invalid change entri
 
 #### GDAL
 
-- Added wrappers for the Grid API. It uses `GDAL::Gridder`, which is the programmatic equivalent to
-  the `gdal_grid` command-line utility, `GDAL::GridderOptions`, which is an object used to mimic the
-  options you pass to `gdal_grid`, and `GDAL::Grid`, which is the simple object that performs the
+- Added wrappers for the Grid API. It uses `GDAL::Gridder`, which is the
+  programmatic equivalent to the `gdal_grid` command-line utility,
+  `GDAL::GridderOptions`, which is an object used to mimic the options you pass
+  to `gdal_grid`, and `GDAL::Grid`, which is the simple object that performs the
   gridding.
-- Added first wrapper of `gdalwarper.h` methods, found in `GDAL::DatasetMixins::WarpMethods`.
-- Added `GDAL::GeoTransformMixins::Extensions.new_from_envelope` which lets you create a
-  `GDAL::GeoTransform` using the points from an `OGR::Envelope` and the destination raster's width
-  and height. It's convenient because it calculates the pixel size for you.
-- Added `GDAL::RasterBand#write_block`. Somehow this went missing from previous `RasterBand`
-  wrapping.
-- Added `GDAL::InternalHelpers._buffer_from_data_type` to compliment the existing
-  `._pointer_from_data_type`. Useful for creating buffer-specific pointers from a GDAL data type.
-- Added `GDAL::InternalHelpers` methods for creating NArrays based on GDAL data types.
-- `GDAL::Options` values all have `#to_s` called on them to ensure they're Strings before handing
-  them over to GDAL. The GDAL options "hash" requires that both keys and values be Strings.
-- `GDAL::RasterBandMixins::AlgorithmMethods` that use GDALProgressFunc functions can now participate
-  in GDALScaledProgress functions.
+- Added first wrapper of `gdalwarper.h` methods, found in
+  `GDAL::DatasetMixins::WarpMethods`.
+- Added `GDAL::GeoTransformMixins::Extensions.new_from_envelope` which lets you
+  create a `GDAL::GeoTransform` using the points from an `OGR::Envelope` and the
+  destination raster's width and height. It's convenient because it calculates
+  the pixel size for you.
+- Added `GDAL::RasterBand#write_block`. Somehow this went missing from previous
+  `RasterBand` wrapping.
+- Added `GDAL::InternalHelpers._buffer_from_data_type` to compliment the
+  existing `._pointer_from_data_type`. Useful for creating buffer-specific
+  pointers from a GDAL data type.
+- Added `GDAL::InternalHelpers` methods for creating NArrays based on GDAL data
+  types.
+- `GDAL::Options` values all have `#to_s` called on them to ensure they're
+  Strings before handing them over to GDAL. The GDAL options "hash" requires
+  that both keys and values be Strings.
+- `GDAL::RasterBandMixins::AlgorithmMethods` that use GDALProgressFunc functions
+  can now participate in GDALScaledProgress functions.
 - Added `GDAL::RasterBandMixins::Extensions#pixel_count`.
-- Allow `GDAL::Dataset`s to be open in shared mode vs non-shared mode. All Datasets now default to
-  use shared mode.
-- Added enumerator `RasterAttributeTableMixins::Extensions#each_column` to allow nicer iterating
-  over columns.
+- Allow `GDAL::Dataset`s to be open in shared mode vs non-shared mode. All
+  Datasets now default to use shared mode.
+- Added enumerator `RasterAttributeTableMixins::Extensions#each_column` to allow
+  nicer iterating over columns.
 
 #### OGR
 
 - Added `OGR::CoordinateTransform#transform_ex`.
-- Added `OGR::FeatureExtensions#field()` which gets the field using the associated
-  `OGR::FieldDefinition#type`. Makes so you don't always have to request the field by its type
-  (`field_as_double`).
-- Added `OGR::LayerMixins::Extensions#point_values()` which gets values for all of the points in the
-  layer. It also allows you to specify getting field values with that, which helps retrieving data
-  for the Grid API. You can also pass it a block to filter out points that don't match some criteria
-  defined in the block.
-- Added `OGR::LayerMixins::Extensions#any_geometries_with_z?` which simply checks to see if the
-  layer has any geometries with Z values.
-- `GDAL::DataType.by_name` always calls `#to_s` on the param now, letting you pass in Symbols.
-- Added `OGR::Point#set_point`, `OGR::Point25#set_point`, and `OGR::GeometryTypes::Curve#set_point`
-  wrappers for `OGR_G_SetPoint_2D` and `OGR_G_SetPoint`.
-- Added `OGR::LineString#add_geometry` to allow adding a OGR::Point object to the LineString instead
-  of having to pass coordinates in to #add_point.
-- Added `OGR::GeometryMixins::Extensions#invalid?` to compliment `OGR::Geometry#valid?`.
-- Added `OGR::LayerMixins::Extensions#point_geometry`, `#each_point_geometry`, and
-  `point_geometries`. Since `#point` implies it returns a Point object, but the OGR API's related
-  method returns point values (x, y, z), it seemed like it would be useful to have a method that
-  returned a geometry.
+- Added `OGR::FeatureExtensions#field()` which gets the field using the
+  associated `OGR::FieldDefinition#type`. Makes so you don't always have to
+  request the field by its type (`field_as_double`).
+- Added `OGR::LayerMixins::Extensions#point_values()` which gets values for all
+  of the points in the layer. It also allows you to specify getting field values
+  with that, which helps retrieving data for the Grid API. You can also pass it
+  a block to filter out points that don't match some criteria defined in the
+  block.
+- Added `OGR::LayerMixins::Extensions#any_geometries_with_z?` which simply
+  checks to see if the layer has any geometries with Z values.
+- `GDAL::DataType.by_name` always calls `#to_s` on the param now, letting you
+  pass in Symbols.
+- Added `OGR::Point#set_point`, `OGR::Point25#set_point`, and
+  `OGR::GeometryTypes::Curve#set_point` wrappers for `OGR_G_SetPoint_2D` and
+  `OGR_G_SetPoint`.
+- Added `OGR::LineString#add_geometry` to allow adding a OGR::Point object to
+  the LineString instead of having to pass coordinates in to #add_point.
+- Added `OGR::GeometryMixins::Extensions#invalid?` to compliment
+  `OGR::Geometry#valid?`.
+- Added `OGR::LayerMixins::Extensions#point_geometry`, `#each_point_geometry`,
+  and `point_geometries`. Since `#point` implies it returns a Point object, but
+  the OGR API's related method returns point values (x, y, z), it seemed like it
+  would be useful to have a method that returned a geometry.
 
 ### Changed
 
 #### GDAL
 
-- Renamed `GDAL::GridTypes` to `GDAL::GridAlgorithms`. This shouldn't impact anyone/thing since it's
-  only relative to the newly added Grid API wrapper. There just happened to me some Grid cruft that
-  had been laying around for some time.
-- Renamed `GDAL::RasterBandMixins::Extenions#each_by_block` to `#read_by_block`. Its functionality
-  was doing reading, yet implied reading or writing; since writing by block isn't needed anywhere
-  internally yet, I just renamed this.
-- Renamed `GDAL::RasterBandMixins#write_array` to `#write_xy_narray`. This method's name inferred
-  that it could write any old Array, but that's not the case--it only writes 2D NArray data.
-- `GDAL::DatasetMixins::Extensions#extent` now manually builds an `OGR::Polygon` instead of
-  polygonizing the entire dataset and taking the envelope of that. Much faster this way.
-- Refactored `GDAL::RasterBandMixins::Exsentions#projected_points` to return a 3D NArray (indicating
-  pixel/row position) instead of just a 2D NArray of coordinates.
+- Renamed `GDAL::GridTypes` to `GDAL::GridAlgorithms`. This shouldn't impact
+  anyone/thing since it's only relative to the newly added Grid API wrapper.
+  There just happened to me some Grid cruft that had been laying around for some
+  time.
+- Renamed `GDAL::RasterBandMixins::Extenions#each_by_block` to `#read_by_block`.
+  Its functionality was doing reading, yet implied reading or writing; since
+  writing by block isn't needed anywhere internally yet, I just renamed this.
+- Renamed `GDAL::RasterBandMixins#write_array` to `#write_xy_narray`. This
+  method's name inferred that it could write any old Array, but that's not the
+  case--it only writes 2D NArray data.
+- `GDAL::DatasetMixins::Extensions#extent` now manually builds an `OGR::Polygon`
+  instead of polygonizing the entire dataset and taking the envelope of that.
+  Much faster this way.
+- Refactored `GDAL::RasterBandMixins::Exsentions#projected_points` to return a
+  3D NArray (indicating pixel/row position) instead of just a 2D NArray of
+  coordinates.
 - Allow `GDAL::RasterBand#create_mask_band` to take a single flag or many.
-- Allow `GDAL::Driver#create_dataset` and `GDAL::Dataset.open` to take a block, yielding the dataset
-  then closing it afterwards.
-- `GDAL::RasterBandClassifier` now uses NArray to classify. Can result in quite a large performance
-  gain.
-- `GDAL::RasterAttributeTable` methods that returned -1 when a value can't be returned now return
-  nil instead.
-- Renamed `GDAL::RasterAttributeTable#value_to_*` methods to be named after their C functions. Also,
-  renamed `#add_value` to `#set_value` and refactored into `RasterAttributeTableMixins::Extensions`.
-- Swapped order of params in `GDAL::Driver#rename_dataset` to be (old, new) instead of (new, old).
+- Allow `GDAL::Driver#create_dataset` and `GDAL::Dataset.open` to take a block,
+  yielding the dataset then closing it afterwards.
+- `GDAL::RasterBandClassifier` now uses NArray to classify. Can result in quite
+  a large performance gain.
+- `GDAL::RasterAttributeTable` methods that returned -1 when a value can't be
+  returned now return nil instead.
+- Renamed `GDAL::RasterAttributeTable#value_to_*` methods to be named after
+  their C functions. Also, renamed `#add_value` to `#set_value` and refactored
+  into `RasterAttributeTableMixins::Extensions`.
+- Swapped order of params in `GDAL::Driver#rename_dataset` to be (old, new)
+  instead of (new, old).
 - `GDAL::Driver#copy_dataset` now yields a writable Dataset.
 - `GDAL::Driver#copy_dataset` now properly takes progress block arguments.
 
 #### OGR
 
-- `OGR::DataSource.open` can now take a block, yielding the data source, then closing it afterwards.
-- Extracted `OGR::LayerMixins::Extensions#each_feature` from `OGR::LayerMixins::Extensions#features`
-  to provide an Enumerator. This lets consumers utilize yielded `OGR::Feature`s as they're retrieved
-  instead of after the `features` Array has been built. `OGR::LayerMixins::Extensions#features` now
-  uses this too.
+- `OGR::DataSource.open` can now take a block, yielding the data source, then
+  closing it afterwards.
+- Extracted `OGR::LayerMixins::Extensions#each_feature` from
+  `OGR::LayerMixins::Extensions#features` to provide an Enumerator. This lets
+  consumers utilize yielded `OGR::Feature`s as they're retrieved instead of
+  after the `features` Array has been built.
+  `OGR::LayerMixins::Extensions#features` now uses this too.
 
 ### Fixed
 
-- Cleanup `OGR::Feature`s that were a result of `OGR::Layer#next_feature`. According to GDAL docs,
-  these _must_ be cleaned up before the layer is.
+- Cleanup `OGR::Feature`s that were a result of `OGR::Layer#next_feature`.
+  According to GDAL docs, these _must_ be cleaned up before the layer is.
 
 #### GDAL
 
-- `GDAL::RasterBandMixins::AlgorithmMethods#fill_nodata!` was calling the old name of the C
-  function.
+- `GDAL::RasterBandMixins::AlgorithmMethods#fill_nodata!` was calling the old
+  name of the C function.
 - `GDAL::EnvironmentMethods#dump_open_datasets` now works.
 
 #### OGR
 
-- `OGR::Field#date=` was casting the passed value to a `Time` object, which in doing so was setting
-  the time zone. If a user passes in an object that doesn't have the TZ set, the method shouldn't be
-  setting it for them.
+- `OGR::Field#date=` was casting the passed value to a `Time` object, which in
+  doing so was setting the time zone. If a user passes in an object that doesn't
+  have the TZ set, the method shouldn't be setting it for them.
 - `OGR::Geometry#point_on_surface` now properly returns a geometry object.
 - `OGR::CoordinateTransform#transform` never worked. Fixed.
 - `OGR::GeometryMixins::Extensions#utm_zone` no longer creates invalid geometry.
 - `OGR::Feature#dump_readable` never worked. Fixed.
 - `OGR::Geometry#dump_readable` never worked. Fixed.
 - Added missing output_layer param to `OGR::LayerMixins::OGRLayerMethodMethods`.
-- `FFI::OGR::Core::WKBGeometryType` was using an INT32 instead of UINT32 and thus 25D geometry types
-  weren't completely accurate.
-- `OGR::LayerMixins::Extensions#geometry_from_extent` now builds an `OGR::Polygon` using the same
-  algorithm that `GDAL::DatasetMixins::Extensions#extent` uses. One could argue that there was also
-  a bug here in that `geometry_from_extent` used to return the convex hull of the extent, not the
-  extent itself.
+- `FFI::OGR::Core::WKBGeometryType` was using an INT32 instead of UINT32 and
+  thus 25D geometry types weren't completely accurate.
+- `OGR::LayerMixins::Extensions#geometry_from_extent` now builds an
+  `OGR::Polygon` using the same algorithm that
+  `GDAL::DatasetMixins::Extensions#extent` uses. One could argue that there was
+  also a bug here in that `geometry_from_extent` used to return the convex hull
+  of the extent, not the extent itself.
 
 ### Removed
 
-- Removed all `ObjectSpace.define_finalizer` calls that "cleaned up" C pointers for Ruby-wrapped
-  objects that had not yet been closed/destroyed. This was keeping those Ruby objects from getting
-  collected (?) and effectively causing lots of unnecessary memory use.
+- Removed all `ObjectSpace.define_finalizer` calls that "cleaned up" C pointers
+  for Ruby-wrapped objects that had not yet been closed/destroyed. This was
+  keeping those Ruby objects from getting collected (?) and effectively causing
+  lots of unnecessary memory use.
 
 ## [1.0.0.beta5] - 2015-06-16
 
 ### Added
 
-- Added `GDAL::RasterBand#raster_io` and refactored `GDAL::RasterBand#write_array` to use it.
+- Added `GDAL::RasterBand#raster_io` and refactored
+  `GDAL::RasterBand#write_array` to use it.
 
 ### Changed
 
-- `GDAL::RasterBandClassifier#equal_count_ranges` now returns `nil` if there aren't enough points
-  per group/class to return the requested number of breaks.
+- `GDAL::RasterBandClassifier#equal_count_ranges` now returns `nil` if there
+  aren't enough points per group/class to return the requested number of breaks.
 - Simplified NDVI (and related) methods in `GDAL::DatasetMixins::Extensions`.
-- NDVI and related methods in `GDAL::DatasetMixins::Extensions` now close the newly created dataset
-  instead of leaving it open. It's been far too easy to forget to close the dataset after creation,
-  leaving seemingly incorrect resulting datasets (since GDAL doesn't flush writes until the dataset
-  is closed).
-- NDVI methods in `GDAL::DatasetMixins::Extensions` no longer check for NaNs after doing the NDVI
-  calculations, thus speeding up the algorithm.
-- `GDAL::DatasetMixins::Extensions#remove_negatives_from` now uses an NArray mask to remove the
-  negative values instead of looping through each value.
-- `GDAL::DatasetMixins::Extensions` NDVI methods now default to NODATA of `-9999.0`.
+- NDVI and related methods in `GDAL::DatasetMixins::Extensions` now close the
+  newly created dataset instead of leaving it open. It's been far too easy to
+  forget to close the dataset after creation, leaving seemingly incorrect
+  resulting datasets (since GDAL doesn't flush writes until the dataset is
+  closed).
+- NDVI methods in `GDAL::DatasetMixins::Extensions` no longer check for NaNs
+  after doing the NDVI calculations, thus speeding up the algorithm.
+- `GDAL::DatasetMixins::Extensions#remove_negatives_from` now uses an NArray
+  mask to remove the negative values instead of looping through each value.
+- `GDAL::DatasetMixins::Extensions` NDVI methods now default to NODATA of
+  `-9999.0`.
 
 ## [1.0.0.beta4] - 2015-04-22
 
-Whoa there's lots of changes here... Many are outlined below, but there's really a ton more.
+Whoa there's lots of changes here... Many are outlined below, but there's really
+a ton more.
 
 ### Added
 
@@ -430,35 +481,36 @@ Whoa there's lots of changes here... Many are outlined below, but there's really
 
 ### Changed
 
-- Full refactor of FFI/C function wrapper. Closer mapping of Ruby functions within modules to the
-  C-header files where the functions actually reside.
-- Full redesign of the error handling mechanism; ffi-gdal now hooks in to GDAL's error handling,
-  thus errors raised from GDAL automagically get handed over as Ruby exceptions. (GDAL only; OGR
-  doesn't provide this.) This also entailed adding a bunch of new exceptions and renaming some old
-  ones.
+- Full refactor of FFI/C function wrapper. Closer mapping of Ruby functions
+  within modules to the C-header files where the functions actually reside.
+- Full redesign of the error handling mechanism; ffi-gdal now hooks in to GDAL's
+  error handling, thus errors raised from GDAL automagically get handed over as
+  Ruby exceptions. (GDAL only; OGR doesn't provide this.) This also entailed
+  adding a bunch of new exceptions and renaming some old ones.
 - Lots more `OGR` love. Much of this API has now been vetted.
 
 ### Fixed
 
-- Fixed some `GDAL::Dataset` extension methods (`extract_ndvi` and friends) that weren't properly
-  handling various data types.
+- Fixed some `GDAL::Dataset` extension methods (`extract_ndvi` and friends) that
+  weren't properly handling various data types.
 - Better handling of large files.
-- Fixed regular crashes when dealing with `OGR` Geometries and `SpatialReferences`.
+- Fixed regular crashes when dealing with `OGR` Geometries and
+  `SpatialReferences`.
 
 ## [1.0.0.beta3] - 2014-11-11
 
 ### Fixed
 
-- `ogr/exceptions` wasn't being required for `ext/error_symbols.rb`, thus any use of an OGR
-  exception was causing a `NameError`.
+- `ogr/exceptions` wasn't being required for `ext/error_symbols.rb`, thus any
+  use of an OGR exception was causing a `NameError`.
 
 ## [1.0.0.beta2] - 2014-10-23
 
 ### Added
 
 - Added more documentation
-- Uncommented `attach_function` calls that had been commented out due to lack of support in versions
-  I'd tested on. These get handled now on load.
+- Uncommented `attach_function` calls that had been commented out due to lack of
+  support in versions I'd tested on. These get handled now on load.
 
 ## [1.0.0.beta1] - 2014-10-23
 
@@ -467,19 +519,21 @@ Lots of changes, so just the highlights here...
 ### Added
 
 - Added C and Ruby wrapper for most of `OGR`.
-- Allow loading, even when C functions aren't defined in the version of `GDAL` that you're using.
+- Allow loading, even when C functions aren't defined in the version of `GDAL`
+  that you're using.
 - Added `#as_json`, `#to_json` to many classes.
 
 ### Changed
 
 - Better handling of `CPLErr` return values.
-- Split out additions to `GDAL/OGR` in `*_extensions.rb` modules. Methods contained in `Extensions`
-  modules don't directly wrap `GDAL`/`OGR` functions, but either provide new functionality or
-  attempt to make library usage more Rubyesque.
+- Split out additions to `GDAL/OGR` in `*_extensions.rb` modules. Methods
+  contained in `Extensions` modules don't directly wrap `GDAL`/`OGR` functions,
+  but either provide new functionality or attempt to make library usage more
+  Rubyesque.
 - Lots of cleanup of class internals.
 - `autoload` child `GDAL` and `OGR` Ruby classes.
-- Renamed files under `ffi/` that were derived from `GDAL`/`OGR` header files to include `_h` in the
-  name.
+- Renamed files under `ffi/` that were derived from `GDAL`/`OGR` header files to
+  include `_h` in the name.
 
 ## [0.0.4] - 2014-09-27
 
@@ -491,13 +545,14 @@ Lots of changes, so just the highlights here...
 
 ### Changed
 
-- The `approx_ok` param for `RasterBand#histogram` should default to `false` (preferring data
-  exactness over performance).
+- The `approx_ok` param for `RasterBand#histogram` should default to `false`
+  (preferring data exactness over performance).
 
 ### Fixed
 
 - Fixed URL silliness introduced in 0.0.2.
-- `Dataset#*_band` methods should return `nil` if the band with that color isn't found.
+- `Dataset#*_band` methods should return `nil` if the band with that color isn't
+  found.
 - `RasterBand#default_histogram` died if the band didn't have any values.
 - `RasterBand#histogram` wasn't returning totals.