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.
This is a long overdue update which skips the 3.1 major release.
py-gdal is also udpated.
Besides what is noted in upstream NEWS, gdalserver has been withdrawn.
See NEWS in the source tarball; this pkgsrc update corresponds to 1452
lines.
= GDAL/OGR 3.2.0 Release Notes =
== In a nutshell... ==
* New GDAL drivers:
- ESRIC: ESRI bundle cache read-only driver (#2663)
- HEIF: read-only driver for HEIF/HEIC file. Requires libheif
- OGCAPI: tiles/maps/coverage raster/vector experimental driver
- TGA: read/only driver to read TGA image file format
* New OGR drivers:
- LVBAG: read-only support for Dutch LVBAG/Kadaster 2.0 vector format
* New utilities:
- gdal_create: to create/initialize a new raster file
* Other improvements:
- Multi-threaded overview computation (if GDAL_NUM_THREADS set)
- COG driver: TILING_SCHEME creation option
- OpenFileGDB driver: add support for using spatial indexes
- BAG driver: multiple improvements
- FITS driver: multiple improvements (MEF and binary table support)
- NITF driver: support for SNIP TREs
- OGRFieldDefn: support UNIQUE constraint
- OGRFieldDefn: support a AlternativeName (alias) property (#2729)
- Python bindings: move implementation of scripts (except gdal2tiles) in osgeo.utils package to be reusable
- Faster GTIFF Deflate compression/decompression through libdeflate (if using internal libtiff or libtiff > 4.1.0)
* Removed functionality:
- Python bindings: old-style "import gdal" is no longer available. Use "from osgeo import gdal" instead
- API_PROXY mechanism: likely never used for real usage.
- Removal of GDAL and OGR ArcSDE drivers
== Backward compatibility issues ==
See MIGRATION_GUIDE.txt
= GDAL/OGR 3.1.0 Release Notes =
== In a nutshell... ==
* Implement RFC 75: support for multidimensional arrays in MEM, VRT, netCDF, HDF4, HDF5 and GRIB drivers. Read/write for MEM and netCDF. Read/only for others. Add gdalmdiminfo and gdalmdimtranslate utilities.
* Implement RFC76: add capability of writing vector drivers in Python
* New GDAL drivers:
- COG: write-only, for Cloud Optimized GeoTIFF
- EXR: read/write driver, relying on OpenEXR library
- ISG: read-only, for geoid models of the International Service for the Geoid
- RDB: read-only, for RIEGL Database .mpx RDB 2 files (#1538) (needs proprietary SDK)
* New OGR drivers:
- FlatGeoBuf: read-support and creation (#1742)
- MapML: read/write driver for experimental web spec
* Improved drivers:
- OAPIF driver (renamed from WFS3): updated to OGC API - Features 1.0 core spec
- GTiff: improve performance of internal overview creation
- GTiff: GeoTIFF 1.1 support
- Shapefile driver: add read/creation/update support for .shz and .shp.zip
- netCDF vector: read/write support for CF-1.8 Encoded Geometries (#1287)
- VICAR: multiple improvements and write support (#1855)
- DDS: add read support
* Other improvements:
- gdalwarp: accept output drivers with only CreateCopy() capabilities
- gdal_viewshed: new utility for viewshed algorithm
* Remove GFT driver now that the online service no longer exists (#2050)
* New Sphinx-based documentation
* Multiple security related fixes (ossfuzz)
* Continued code linting (cppcheck, CoverityScan, etc.)
* Compatibility with GDAL 3.0:
- C and C++ API: backward compatible changes
- C ABI: backward compatible changes
- C++ ABI: modified
- Functional changes: see MIGRATION_GUIDE.TXT
This is an update from the 3.10 LTR to the newly-designated 3.16 LTR.
Besides hand-re-applying patches, and believing the new PLIST, the
only change is a new dependency on protobuf.
Upstream NEWS
# 3.16
This release brings a wealth of new options for 3D mapping, mesh
generation from other data types, additional spatial analysis tools,
symbology and user interface enhancements to name but a few! A host of
tools have been incorporated into the ever-expanding processing
framework, and the QGIS browser now supports advanced database
interaction functionality that was previously reserved for the DB
Manager plugin.
https://www.qgis.org/en/site/forusers/visualchangelog316/index.html
# 3.14
Some of the marquee features include vector tile support, huge
advances in mdal / mesh support, native support for temporal data in
WMS-T, PG Raster, vector providers, and mesh layers. Users focussed on
cartography and digitising haven’t been left out either, with many new
options for you!
https://www.qgis.org/en/site/forusers/visualchangelog314/index.html
# What's new in Version 3.12 'București'?
This release has following new features:
- User Interface: Deselecting tables when adding PostgreSQL data after add button is clicked.
- Symbology: Vector Trace Animation and Streamlines for Mesh Layer
- Rendering: Play/Stop Buttons for Mesh Layer Playback
- Rendering: On the Fly Resampling of Data Defined on Faces to Vertices (Mesh Layer)
- Rendering: Support for Mesh Reference Time
- 3D Features: 3D Mesh Layer Terrain Renderer
- 3D Features: Harmonize 3D map view widget with 2D ones to display the map theme drop-down menu
- Expressions: Search Tags for Functions
- Expressions: List Referenced Layer Values
- Expressions: New functions to check if a geometry is empty or null
- Expressions: Hash expressions
- Digitizing: Edit Invalid Attributes on Copy/Paste to Another Layer
- Digitizing: Snapping cache parallelization
- Data Management: DXF Export Improvements
- Forms and Widgets: Create geometric feature from the relation editor
- Forms and Widgets: Improve feature selection dialog
- Analysis Tools: Smooth Export of the Contours from Mesh Layer
- Analysis Tools: Support of Datasets Defined on Faces in QGIS Mesh Calculator
- Processing: Package new layers to existing GeoPackage
- Browser: Customization of the items shown in browser
- Data Providers: Changed WMTS layer collection icon
- Data Providers: Added Metadata URL property in the layer metadata tab for WMS / WMTS and WCS services
- Data Providers: Fetch and show dimensions metadata for a WMS layer metadata
- Data Providers: Added refresh action to OGC services entries
- Data Providers: 3d Stacked Meshes
- Data Providers: Oracle curve type edition support
- Programmability: Exposes shape digitizing methods to QgisInterface
- Notable Fixes: Bug fixes by Stephen Knox
https://www.qgis.org/en/site/forusers/visualchangelog312/index.html
