This is a bug fix release.
New gama-local adjustment XML output definition
gama-local-adjustment.xsd version 1.02.
New XML tag <not-applicable/> was added to the adjustment ouput
format for cases with zero degrees of freedom, where the standard
deviation test is not applicable (previously there were only two
tags <passed/> and <failed/>). Old XML output files are formally
complient with the new XSD version 1.02
packaging changes:
- switch to github for distfile
- switch from configure to qmake
- depend on libusb1 and zlib (and add pkg-config as a tool)
- drop patches to configure
- add patches to fix portability issues in qmake support
upstream changes (No NEWS provided, but skimming git log):
- drop autoconf
- retire some formats
- Update standards to c++17, Qt >= 5.12, MSVC >= 2017
- lots of bugfixes and minor improvements
This is a Python module for reading MaxMind DB files. The module includes both
a pure Python reader and an optional C extension.
MaxMind DB is a binary file format that stores data indexed by IP address
subnets (IPv4 or IPv6).
The package changed with the addition of its libepoll-shim dependency.
Otherwise, we can get:
ERROR: libepoll-shim>=0.0.20210418 is not installed; can't buildlink files.
Changes in release 2.21
- bugfixes
Changes in release 2.20 (2022-06-30)
- The new algorithm ICGS (iterated classical Gram-Schmidt) in the
class AdjGSO replaced the former algorithm MGS (modified
Gram-Schmidt), which was implemented with column pivoting as a
template class GSO. The template class GSO is meant only as a tool
for testing purposes. Both initial scaling and pivoting with
euclidean norms are not suitable for practical computations.
The old legacy code with MGS used in the AdjGSO class is still
available with conditional compilation directive statements if the
name GNU_GAMA_GSO_LEGACY_CODE is defined.
Changes in release 2.19 (2022-04-26)
- fixed a bug in HTML output of adjustment results for GNSS vectors
in incosistent coordinates systems.
- added new test to GNU Gama Test Suite.
The smartos bulk build reported a failure due to not resolving
sqrt(5). Add a patch which is part of a change upstream just merged
to deal with this: change 5 to 5.0.
qlandkartegt does not build in any bulk builds I can find, and is
discontinued upstream (in favor of qmapshack:
https://github.com/Maproom/qmapshack/wiki
in case anyone wants to package that)
Unclear at this time if upstream have changed the tarball or if the checksums
were incorrect, but this definitely correlates with what they are currently
distributing, as well as matches their published md5 checksums.
## Summary
* [RFC 84](https://gdal.org/development/rfc/rfc84_cmake.html):
Addition of a CMake build system, which deprecates the existing
autoconf/automake and nmake build systems, that will be removed
in GDAL 3.6.0. Users are encouraged to adopt the new CMake build system.
Documentation of the CMake build system is at
https://gdal.org/build_hints.html.
* Add GDT_Int64 and GDT_UInt64 data types and handle them in MEM, GTiff, netCDF and Zarr drivers
* Add read/write OGR Parquet (Apache Parquet) and 'Arrow' (Apache Arrow IPC File/Feather or stream) drivers. Only in CMake builds
* Add OGR HANA database driver. Only in autoconf & cmake builds
* Removed drivers: RDA, JPEG2000 (Jasper-based), CharLS, MG4 LIDAR, FujiBAS, IDA, INGR, ARCGEN, ArcObjects, CouchDB, Cloudant, DB2, FME, Geomedia, MDB (Java Jackess based), GTM, Ingres, MongoDB (old one. MongoDBv3 is the one to use now), REC, Walk, GMT raster, DODS raster and vector
* GDAL and OGR GRASS drivers moved to https://github.com/OSGeo/gdal-grass repository
* Tiger: remove deprecated write side of the driver (#4216)
* Remove deprecated SWIG Perl bindings
* Code linting and security fixes
* Bump of shared lib major version
## Removed files
* Remove deprecated testepsg utility (#3993)
Upstream NEWS since 1.2.10:
* Minor improvements (see ChangeLog for details)
* contrib/shpgeo.h/.c: Remove PROJ.4 dependency and functionality,
causing removal of SHPProject(), SHPSetProjection() and SHPFreeProjection()
* contrib/shpproj.c: removed
* bump shlib version
* convert to autoconf/automake
Version 1.0-6 23/10/2021
Fixed a bug that kept deldir() from working when "x" is a
point pattern.
Version 1.0-5 10/10/2021
Changed the protocol for "digging out" x and y, and
"digging out" z. The rule now is: if the specified argument
is found (located in the global environment, or given explicitly)
then *use* it! Only if it is *not* found elsewhere should it be
sought in the "x" argument. (This change was implemented after
Duncan Murdoch convinced me to see the error of my previous ways.)
Adjusted/corrected the processing of generic lists, as the x
argument, in deldir()
Re-wrote the discussion of the argument processing protocol in
deldir.Rd, so as to make it properly reflect the current behaviour
of the function. It is also hoped that the clarity of the
discussion has been improved.
Fixed various glitches and typos in the code and the help files.
Version 1.0-4 06/10/2021
Fixed more bugs in deldir() w.r.t. argument processing, again
pointed out to me by Duncan Murdoch.
Fixed a bug in triang.list(); it crashed if there were not
any actual triangles in the "triangulation"!
Made an adjustment to plot.triang.list() (added an argument to
specify a colour for the enclosing rectangle.
Version 1.0-3 06/10/2021
Fixed bug in deldir() (more explicitly in digOutz()) that
was pointed out to me by Duncan Murdoch.
Version 1.0-2 05/10/2021
Adjusted plot.deldir() so that it no longer insists that cmpnt_lty
be numeric, but also allows (as it should) the text strings "solid",
"dashed", "dotted", "dotdash", "longdash", and "twodash".
Version 1.0-1 30/09/2021
Modified deldir() so that if argument "x" is a data frame it is
*NOT* required to have columns named "x" and "y". If there is no
column named "x", the x-coordinates are taken to be the *first*
column named neither "y" nor "z". Likewise if there is no column
named "y", the y-coordinates are taken to be the *first* column
that is named neither "x" nor "z" and is not equal to the column
previously selected to be the x-coordinates.
Also modified deldir() so that the "x" argument is allowed to be
a matrix. The same convention that was used when "x" is a data
frame is applied.
This modification was made in response to an observation made by
Jakob Bossek and makes use of a suggestion from Duncan Murdoch.
Version 1.0-0 27/09/2021
Removed/eliminated all traces of the (basically useless) facility
for incorporating dummy points into the triangulation/tessellation.
This facility was a historical artefact that had hung around much
too long.
Made an adjustment to plot.tile.list(); it no longer throws an
error if the border argument is of length greater than 1; it now
simply uses the first entry.
29/09/2021
Ran the *.Rd files through ispell and found and corrected an
embarrassing number of errors. Did not increment the version
number.
Version 0.2-13 26/09/2021
Made some adjustments to the syntax of deldir() to accommodate
problems encountered with finding the "z" argument.
Changed the position of "z" in the argument list (to follow "x"
and "y").
Got rid of the message being issued on the first call, and the
suppressMessage argument.
Version 0.2-12 28/05/2021
Adjusted the application of "\dontrun{...}" in the help files,
eliminating its unnecessary application in some instances, and
replacinng it by "\donttest{...}" in one instance.
Version 0.2-11 12/05/2021
Changed the terminology in the help and code comments so as to
refer to the entries of the "z" argument as "tags" and not
as "weights". The latter term is misleading.
Adjusted divchain() so as not to insist that the "z" argument
be a factor. It may now be a factor or a vector of any mode.
If is not a factor then it is coerced into one.
Added a "tags" component to the list returned by lawSummary().
(This was instigated by an enquiry from Art Stock.)
Version 0.2-10 09/02/2021
Added the cvt() (Centroidal Voronoi Tiles) function at the
request of Michaél Aupetit.
Amended deldir() so that the returned object has attributes
"round" (TRUE if argument "round" was TRUE) and "digits"
(equal to the value of argument "digits" if "round" is TRUE,
equal to NA otherwise.)
Made some adjustments to the help for deldir() and plot.tile.list().
Changed the name of Vol.Tri.Points to volTriPoints, so as to make
it more consistent with my usual naming conventions.
Added the "\version" macro.
10/02/2021
Made some adjustments to the help for cvt().
16/02/2021
Submitted to CRAN
Version 0.2-9 16/01/2021
Fixed (???) a bug in doClip() revealed by reverse-dependent package
visualFields. My logic (using almost.match()) was completely out
to luntch. Got rid of almost.match() and introduced a new function
findNewInOld() which I *think* does things right.
Adjusted tile.list() so that when it clipps tiles it checks for
the availability of the polyclip package (and throws an error if
this package is not available).
Adjusted the help for plot.tile.list(), doing the same
re-arrangement of plotting colours in one of the examples, as is
used in the help for tilePerim(). The re-arrangement serves to
produce better contrasts between contiguous tiles.
# wk 0.6.0
* Fixed `wk_affine_rescale()` to apply the translate and scale
operations in the correct order (#94).
* Add `wk_handle_slice()` and `wk_chunk_map_feature()` to support
a chunk + apply workflow when working with large vectors (#101, #107).
* C and R code was rewritten to avoid materializing ALTREP vectors
(#103, #109).
* Added a `wk_crs_proj_definition()` generic for foreign CRS objects
(#110, #112).
* Added `wk_crs_longlat()` helper to help promote authority-compliant
CRS choices (#112).
* Added `wk_is_geodesic()`, `wk_set_geodesic()`, and argument `geodesic`
in `wkt()` and `wkb()` as a flag for objects whose edges must
be interpolated along a spherical/ellipsoidal trajectory (#112).
* Added `sf::st_geometry()` and `sf::st_sfc()` methods for wk geometry
vectors for better integration with sf (#113, #114).
* Refactored well-known text parser to be more reusable and faster
(#115, #104).
* Minor performance enhancement for `is.na()` and `validate_wk_wkb()`
when called on a very long `wkb()` vector (#117).
* Fixed issue with `validate_wk_wkb()` and `validate_wk_wkt()`, which failed
for most valid objects (#119).
* Added `wk_envelope()` and `wk_envelope_handler()` to compute feature-wise
bounding boxes (#120, #122).
* Fixed headers and tests to pass on big endian systems (#105, #122).
* Incorporated the geodesic attribute into vctrs methods, data frame
columns, and bbox/envelope calculation (#124, #125).
* Fix `as_xy()` for nested data frames and geodesic objects (#126, #128).
* Remove deprecated `wkb_problems()`, `wkt_problems()`, `wkb_format()`,
and `wkt_format()` (#129).
* `wk_plot()` is now an S3 generic (#130).
3.24: 2022-04-22
NTRIP 2.0 now works. But still only plain HTML, not RTP, etc.
Remove ntrip option and NTRIP_ENABLE. Always build.
Remove passthrough option and PASSTHROUGH_ENABLE. Always build.
Remove nmea0183 option and NMEA0183_ENABLE. Always build.
Remove netfeed option and NETFEED_ENABLE. Always build.
gpsd will retry ntrip:// and tcp:// connections
cgps can expand to show more sats. Added --rtk option.
maidenhead() checks for input errors.
Better SHM logs.
PPS and TOFF JSON now include shm used, and real precision.
Add initial, untested, TSIPv1 support
split debug messages into different syslog() levels.
New ppscheck options, and can use /dev/ppsX devices.
First try at TSIPv1 protocol decodes.
Decode Quectel $PQVERNO for firmware version
Decode Skytrak PX1172RH_DS messages.
* Changes in release 2.18 (2022-04-09)
New conversion class K2gkf (lib/krumm) with accompanying program
krumm2gama-local and the testing suite for converting input data
format used in the text book "Geodetic Network Adjustment Examples" by
Friedhelm Krumm, Geodätisches Institut Universität Stuttgart, 2020.
Not all input data in Krumm Format can be converted to GNU Gama,
i.e. to the adjustment program gama-local input XML:
* scale factor is not implemented in gama-local adjustment
* gama-local does not enable fixing only x coordinate (or y
coordinate) for 2D free network to remove singularity. This kind
of regularization has very little practical meaning. Technically
it would be possible to enable this feature in gama-local, but it
is questionable if the outcome would not enable more confusion
than possible outcome. Adustment should not be dependent on the
coordinate system used.
* gama-local does not deduce that an azimuth to the unknown point
P can be combined with some angle pointing to the P to create a
new feigned azimuth. This is an interesting feature which may
be implemented in some future version, namely in the gama-local
stage of computing approximate coordinates.
* nonlinear conditions are not implemented in gama-local
* BLH coordinates are not supported in gama-local
