# version 0.9-8
* add `st_as_sf` method for terra's `SpatVector` class; #1567
* `distinct.sf` works by default on all variables, and keeps active geometry
afctive; #1613
* improve (fix?) polygonize/contour code; #1608
* `sf_proj_network()` reports whether PROJ uses network (CDN) grids, can switch
it on or off, and can set the CDN url.
* `st_write` returns obj, invisibly; #1597
* fix regression in n-ary `st_intersection()`, #1595, introduced at #1549
* `st_inscribed_circle` computes the maximum inscribed circle for polygons
(requires GEOS >= 3.9.0)
* allow to `st_cast` COMPOUNDCURVE, MULTISURFACE or CURVEPOLYGON to
GEOMETRYCOLLECTION (and back); #1573
* Fixed a bug in `st_as_grob()` when plotting a mix of MULTI and non-MULTI
geometries of the same base type
# version 0.9-7
* n-ary `st_intersection` skips failing geometries, rather than returning an
error; #1549
* use `s2_centroid` for geographical coordinates if `sf_use_s2()` is `TRUE`.
* `st_as_text` method for `crs` objects can return projjson (if GDAL >= 3.1.0
and PROJ > 6.2.0)
* `st_transform` no longer warns on conversions like `"+proj=ob_tran
+o_proj=longlat +o_lat_p=45 +o_lon_p=30"`
* `st_as_wkb` takes `srid` from `wkt` field of `crs` when `input` field doesn't
contain it; #1490
* `plot.sf` adds `key.pos=0` option to run the logic behind the key without
plotting it; #1487
* fix bug in `select.sf` when selected variables were renamed; #1483
* `st_as_sf.stars` with `merge = TRUE` now works if crs is `NA`; #1389
* add (dynamically loaded) `as_wkb` methods for `sf`, `sfc` and `sfg`, making
`st_as_s2()` unnecessary
* `st_as_s2` transforms non-longlat objects to EPSG:4326 first
# version 0.9-6
* `gdal_utils` print (GDAL-style) progress bar if `quiet = FALSE` (except for
`info` and `mdiminfo`)
* fix `CPL_gdal_warper` for multi bands; https://github.com/r-spatial/stars/issues/320
* `sf_proj_search_paths()` retrieves and sets the proj search path (if GDAL > 3.0.3)
* when loading sf, `sf_use_s2` is set to `FALSE` unless environment variable
`_SF_USE_S2` equals `true`
* resolve GDAL/PROJ version vulnerabilities in CRS-crs conversion; #1479
* `st_sample` gains an argument, `by_polygon`, to more clevery sample
`MULTIPOLYGON` geometries; #1480
* `st_sample` accepts non-integer sample sizes, with a (suppressable) warning
and handles values of sizes that would round to zero; #1480
* `gdal_utils` adds utils `mdiminfo` and `mdimtranslate` (requires GDAL >= 3.1)
* `st_union` gains an argument `is_coverage`, which, when set to `TRUE`, leads
to much faster unioning in case features form a coverage (polygons don't
overlap); #1462 by Don Baston
* fix `gdal_utils("translate")` locking input file; #1452
* `st_make_grid` no longer selects cells intersecting with `x`; #1447
* use `s2::s2_dwithin_matrix` in `st_is_within_distance`; #1367
This commit removes the python option, but keeps python -- what was
formerly included with the option is now simply always included. In
today's qgis world, python support is simply part of qgis and building
without it is close to unthinkable. python is tiny compared to qgis
or even qt.
The rationale for removal is that having a split PLIST, and two ways
to build is some maintenance headache, and I believe that zero people
want to build qgis without python. My guess is that no one has tried
in years.
No PKGREVISOIN++ as there is no change to the default build.
PDAL is Point Data Abstraction Library. It is a C/C++ open source library
and applications for translating and processing point cloud data. It is
not limited to LiDAR data, although the focus and impetus for many of
the tools in the library have their origins in LiDAR.
It's unlikely that this built ok with 2.7, and really unlikely anyone
was actually doing that. However, py-gdal is not python 3.x only, so be explicit.
(No revbump because default has been some form of python 3.x.)
Uptream NEWS:
* RFC 77 (https://gdal.org/development/rfc/rfc77_drop_python2_support.html): Drop Python 2 support in favor of Python 3.6 (#3142)
* RFC 78 (https://gdal.org/development/rfc/rfc78_gdal_utils_package.html): Add a gdal-utils Python package
* New driver:
- STACTA: raster driver to read Spatio-Temporal Asset Catalog Tiled Assets
* Add /vsiadls/ virtual file system for Azure Data Lake Storage Gen2
* Improved drivers: DIMAP, NITF
* Number of improvements in Python bindings
* Add automatic loading of configuration options from a file
* Add support for enumerated, constraint and glob field domains in MEM, FileGDB/OpenFileGDB and GeoPackage drivers
* Deprecation:
- Disable by default raster drivers DODS, JPEG2000, JPEGLS, MG4LIDAR, FUJIBAS, IDA, INGR, ZMAP and vector driver ARCGEN, ArcObjects, CLOUDANT, COUCHDB, DB2, DODS, FME, GEOMEDIA, GTM, INGRES, MONGODB, REC, WALK at runtime, unless the GDAL_ENABLE_DEPRECATED_DRIVER_{drivername} configuration option is set to YES. Those drivers are planned for removal in GDAL 3.5
- Perl bindings are deprecated. Removal planned for GDAL 3.5. Use Geo::GDAL::FFI instead
* Removal of BNA, AeronavFAA, HTF, OpenAir, SEGUKOOA, SEGY, SUA, XPlane, BPG, E00GRID, EPSILON, IGNFHeightASCIIGrid, NTV1 drivers. Moved to (unsupported) https://github.com/OSGeo/gdal-extra-drivers repository.
* Continued code linting (cppcheck, CoverityScan, etc.)
* Bump of shared lib major version
Now it should be more obvious when a package needs it as a dependency,
as it will fail loudly if it isn't declared as a tool.
While here, some duplicate dependencies on itstool were removed from the
MATE packages
## 1.6.0 - 2021-04-29
* This release includes several improvements to the CMake build. In
particular:
* C99 support is now properly enabled, fixing builds on older `gcc`
versions. Pull request by Jan Vcelak. GitHub #257.
* `CMAKE_SHARED_LIBRARY_PREFIX` and `CMAKE_STATIC_LIBRARY_PREFIX` are
no longer explicitly set and now use the default values for the platform.
Pull request by Jan Vcelak. GitHub #258.
* `target_include_directories` now works as expected. Pull request by Jan
Vcelak. GitHub #259.
* DLLs are now installed on Windows when `libmaxminddb` is built as a
shared library. Pull request by Jan Vcelak. GitHub #261.
* When built as a dynamic library on Windows, all symbols are now exported.
Pull request by Jan Vcelak. GitHub #262.
Following a report of build of gdal linking against ODBC, force off
ODBC support so that even if it the lib leaks through buildlink3 it
will not be used. In theory this could be an option similar to pgsql
and mysql support, and that is left to someone who wants it, if such a
person actually exists. For now, this is unconditionally the half of
the option that enforces not looking for ODBC.
No PKGREVISION, because the build should not be changing.
Update HOMEPAGE
Change p5-Test-Number-Delta to TEST_DEPENDS
Upstream changes:
1.15 2021-01-23
- Provide set_angle_unit() as an alternative to the too generically
named method set_units(). The name set_angle_unit() corresponds
nicely to the existing method set_distance_unit().
- Add accessors get_angle_unit(), get_distance_unit(), get_ellipsoid(),
get_equatorial_radius(), get_polar_radius(), get_flattening(), and
get_eccentricity(), get_longitude_symmetric(), and
get_bearing_symmetric(). These are necessary for subclassing.
- Correct the version numbering in Changes (this file) and add missing entry
for version 1.11. Format CHANGES according to CPAN::Changes::Spec.
- Rename the too generically property "units" to "angle_unit", and
"distance_units" to "distance_unit".
- Rename the following internal object properties:
"latitude" -> "latitude_symmetric" (only used internally)
"longitude" -> "longitude_symmetric"
"bearing" -> "bearing_symmetric"
This makes them more descriptive, and they now match the methods
set_latitude_symmetric() and set_bearing_symmetric(). The old object
property names without the "_symmtric" suffix are still supported.
- Improve documentation and fix typos in the POD. Add more information to the
SYNOPSIS. Update BUGS and SUPPORT sections. Update AUTHOR and COPYRIGHT
information.
This is now simply the pdf corresponding to Proj 8. That doesn't
match the proj that is in pkgsrc, but it's vastly more useful than the
older docs, whose download location is now broken.
Upstream changes:
1.3.0:
This release introduces the new "flex" output. It allows a more flexible
definition of output tables and columns. It also adds a second stage of
processing which makes it possible to get information from relations to
their members, allowing, for instance, to render tags from bicycle route
relations on their member ways. The "flex" output is configured through
Lua scripts.
The flex output is currently still marked as experimental, because it is new
and we want to collect feedback from the community before finalizing the API.
But it already works well and users are encouraged to try it out. Some new
features are only or will only be available in the flex output and we expect
that it will replace the other outputs in the long term.
Some features have been marked as deprecated:
The "multi" output will be removed in a future version of osm2pgsql. If you
are using the multi output, switch to the flex output now and tell us if
you have any problems.
When the input file uses negative OSM object IDs a warning is now generated.
Negative IDs never worked correctly for all use cases. Future versions of
osm2pgsql will not allow negative IDs at all. Use "osmium renumber"
to get rid of the negative IDs.
Input files that are not ordered generate a warning. Future versions of
osm2pgsql will not work any more with unordered files. If you have unordered
files use "osmium sort" to order them.
Further changes:
The multi output now looks for lua script relative to the style.json file.
This is a breaking change. Users might have to change the file names of
their lua scripts in the style files.
Use the fmt library for formatting strings now instead of a mixture of
boost::format and hand-written mechanisms. A version of fmt is included
in the contrib directory.
Make PROJ library optional. If the proj library cannot be found by cmake,
do not offer the option to use arbitrary projections. Only WGS84 and
WebMercator are supported then.
Don't use ST_GeoHash for ordering tables by geometry on Postgis >= 2.4.
Instead use the default ordering which works better now.
Fix: Always print correct relations count and more correct count per seconds
when showing processing stats.
Fix: If a function run in the thread pool throws an exception, this exception
was never "collected", it was silently ignored. This meant that some errors,
especially in communication with the database, were not detected correctly.
The dependency management, the part of the code which tracks which changes
in the OSM data trigger which changes in the outputs, was reorganized
making in much cleaner and removing the last remnants of code written to
support "old style" multipolygons.
Tests have been moved to the Catch framework, extended and the regression
tests have been reorganised, so they can run independently of each other.
A lot of code was cleaned up, modernized, made more robust, and sometimes
removed.
1.2.2:
This release only updates the bundled version of libosmium. The new
version 2.15.6 fixes an issue where complicated multipolygons make
osm2pgsql hang.
Packaging changes:
- Change to gtk3
- Drop workaround for lack of NAN on NetBSD 5
- Drop workaround for XOPEN_SOURCE as upstream no lnoger defines it
Viking 1.9 (2021-03-20)
New features since 1.8
* GPX 1.1 Support for most common Extensions (inc. Heart Rate, Power, Temperature & Cadence)
* GTK3
** Pinch Zoom support on Touchpads/Touchscreens (not GTK2 build)
* Select Tool is now the default with more intuitive behaviour to enable moving the map
* [OpenTopoMap](https://opentopomap.org) is the new Map Default
* Online Search in Left Hand Pane
* Track Statistics in Left Hand Pane
* [OSRM](http://project-osrm.org) Routing Support
* Log diagnostic Window
* DEM Colour options
* DEM Server enhanced support (NASA Earthdata login and alternative DEM server configuration)
* Ruler uses Great Circle drawing and distance.
* Single key Shortcuts support
* Improved Track Area Coverage (faster drawing, option to limit years of coverage)
* Monthly Statistics Analysis
* Native KML Parser enabling support for more KML features
* More KML export options
* Ability to convert Tracks/Routes to Waypoints and vice versa.
* Ability to 'Rotate' Routes/Tracks, i.e. to shift the start/end point of circular routes.
* Ability to Reset Preferences and Layer Defaults
* Ability to Reset Layers back to the Layer Default.
* Enable Filtering on some List Displays (hence a basic internal search).
* Support more GPX 1.0 Waypoint fields - the less commonally encountered ones.
