Upstream says that using sqlite3 will become somewhere between normal
and the standard approach. Because sqlite3 is small and typically
already isntalled on systems where one would want to run gama, just
depend on it and don't bother to make it an option.
It would be fine with me to make it a default-on option, but I don't
think that's worth the complexity.
XXX The comment in the code is wrong and using std::isnan is actually
XXX the portable approach. DragonFly and other GCC users likely need the
XXX same change
GNU Gama is a project dedicated to adjustment of geodetic networks. It
is intended for use with traditional geodetic surveyings which are
still used and needed in special measurements (e.g., underground or
high precision engineering measurements) where the Global Positioning
System (GPS) cannot be used.
Adjustment in local Cartesian coordinate systems is fully supported by
a command-line program gama-local that adjusts geodetic (free)
networks of observed distances, directions, angles, height
differences, 3D vectors and observed coordinates (coordinates with
given variance-covariance matrix). Adjustment in global coordinate
systems is supported only partly as a gama-g3 program.
Viking 1.2.1 (2011-06-16)
Fixes since 1.2
* Support proper MAC OS file locations.
* Fix incorrect track property line marker positioning when the track has gaps.
* Fix track property point marker drawing error - sometimes draws dot marker too low.
Viking 1.2 (2011-05-24)
New features since 1.1
* Remove unecessary treeview item selection.
* Add zoom level 0.5 to map layer
* [DOC] Add links to access Viking's source code
* Rename file to prevent any case-insensitive issues.
* Add getting the users confirmation when deleting (emptying) data from the GPS layer.
* Enable keypad delete to remove layers in the layers panel.
* Enable deleting multiple tracks or waypoints within a layer by selecting them from a list.
* Add getting the users confirmation when deleting an individual track or waypoint.
* Add the ability to delete all waypoints or tracks in the layer.
* Add getting the users confirmation when deleting a layer.
* Start a new 'Tracks' treeview menu, similar to the 'new' Waypoints treeview menu.
* Add operations on waypoints into the 'new' Waypoints treeview menu.
* Add new graph type Speed/Distance in the track properties window.
* Add new graph type Elevation/Time in the track properties window.
* Add new graph type Distance/Time in the track properties window.
* Improve Track Properties speed/time drawing to display in nice human friendly whole number scaled units.
* Improve Track Properties elevation drawing to display in nice human friendly whole number scaled units.
* On the Track Properties Window draw an always updating indicator of where the readings are taken from.
* Enable controls of drawing DEM data and GPS speeds on the Track Properties Window.
* Add keyboard accelerators for the Track Properties Window.
* Add ability to resize the Track Properties window.
* On the Track Properties Window, also show the elevation or speed for the current track position as indicated by the mouse pointer.
* Add support for kml files.
* Add ... where necessary to track & waypoint menu entries.
* Enable Open Waypoint Image via right click menu entry.
* Use ability to select a waypoint given the thumbnail image size.
* Add ability to open the trackpoint edit dialog via the viewport right click menu when a trackpoint is selected.
* Add ability to move selected trackpoint or waypoint by the mouse within the select tool.
* Add a new select tool at the window level to enable/disbale item selection of the a track or a waypoint.
* Enable to unselect treeview item
* Add Select Request layer interface and use within the track/waypoint layer to select an item.
* Add internal track right click menu variable.
* Tidy up track/waypoint sublayer callbacks to only use the layers panel if it available.
* Add viewport to sublayer add menu items callback.
* Make the highlight colour configurable and use as appropriate for the selected track/waypoint drawing.
* Add track and waypoint highlight for the selected layer or individual item.
* Add the storage and retrieval of any kind of track or waypoint selected item (either an individual item, list (i.e. a sublayer) or layer) at the window level.
* Add viewport property to control the display of the track / waypoint item highlight.
* Add backup support for launching URLs with Mac OS based browsers.
* Add backup support for launching URLs with Google Chrome based browsers.
* Add support for Bing maps
* Add support for dynamic copyright
* Add map's logo support
* Add support for reference documentation
* Generate a trackwaypoint layer update on the finish creatiing of the thumbnails so the images are shown.
* Enable the tree view panel to be more usefully resized smaller than the text names.
* Windows: Open help pdf file when when clicked on Help->help
* [DOC] Split By Number of Points
* Add Track->Split by Number of Points (as per SF#2847587 request).
* Add a new dialog to return positive number.
* SF#2844872: Suggest name for the new track when splitting the track via the trackpoint edit dialog.
Fixes since 1.1
* Better safety checking to prevent crash due to null variable reference in use of the current trackpoint.
* Fix: Reduce GObject cast
* Fix etag handling
* Fix: generate doc/reference/Makefile when needed
* Fix Track -> Split by Timestamp such that newly created tracks are ordered correctly.
* Fix sensitivity of the track properties window split marker to be disabled when the track marker is not drawn.
* Fix crashing due to incorrect usage of libcurl - SF#3206628.
* Fix non-void function should return a value.
* Fix reference documentation generation - some systems need explicit mention of libz.
* Fix displaying of 'Waypoints' treeview menu.
* Fix vik_aggregate_layer_get_all_layers_of_type for track/waypoint layer types, since these may also be stored under GPS layers.
* Improve previous fix: background calling code should control return value
* Fix: background calling code should control return value
* Fix: enforce background feature
* Fix compiler warnings from gcc 4.5.4
* SF#3178554: Fix Sun Studio build
* gtk_object_sink has been deprecated since gtk version 2.10, use g_object_ref_sink() instead.
- New things:
- CAPI: GEOSBufferWithParams (allows single sided buffers)
- CAPI: GEOSOffsetCurve deprecates GEOSSingleSidedBuffer
- CAPI: GEOSUnaryUnion deprecates GEOSCascadedUnion
- CAPI: GEOSisValidDetail: tell state, reason & location apart. allows
passing flags.
- CAPI: GEOSContext_setNoticeHandler_r, GEOSContext_setErrorHandler_r
- CAPI: GEOSGeom_createEmptyPoint, GEOSGeom_createEmptyLineString
GEOSGeom_createEmptyPolygon, GEOSGeom_createEmptyCollection
- CAPI: GEOSGeom_extractUniquePoints
- CAPI: GEOSGetGeometryN support for single geometries
- CAPI: GEOSPolygonize_full to return all informations computed by
the polygonizer
- CAPI: GEOSOrientationIndex
- CAPI: GEOSSharedPaths to find shared paths and their orientation
- CAPI: GEOSSnap
- CAPI: GEOSRelatePatternMatch
- CAPI: GEOSCovers, GEOSCoveredBy
- CAPI: GEOSRelateBoundaryNodeRule
- PHP: new PHP5 bindings based on CAPI
- Semantic C++ API changes:
- Geometry inheritance chain changed to introduce Puntal, Lineal
and Polygonal classes (virtual inheritance introduced)
- Polygonizer::getInvalidRingLines retains ownership of vector elements
- Geometry::isWithinDistance method is now const
- Polygonizer::getCutEdges returns by const ref
- Polygonizer::getDangles returns by const ref
- Empty LinearRings are closed by definition
- Bug fixes / improvements
- Fixed Geometry.distance() and DistanceOp to return 0.0 for empty inputs
- Invalid compound geometries reported as valid
- Return up to 15 digits of precision from GEOSisValidReason_t
- CAPI: do not leak contexts when using the non-reentrant interface
- Fix duplicated dangles returned by Polygonizer
- Fix SnapIfNeededOverlayOp to throw the originating exception
- Fixed LineMerger to skip lines with only a single unique coordinate
- Fix NodedSegmentString to handle zero-length line segments correctly
(via safeOctant)
- Fixed buffer OffsetCurveSetBuilder to handle "flat" rings correctly
- Added illegal state check in LineSegment::pointAlongOffset()
- Improved performance of RectangleIntersects by always using
segment-scanning and refining SegmentIntersectionTester
- Reduce memory use in PreparedGeometry predicates
- Fix infinite loop in RobustDeterminant with nan/inf input
* When getting data via the GPS layer automatically set the view to see it, unless the realtime tracking mode is on.
* On opening GPX files automatically view all the data.
* Add copyright and license properties for NASA BlueMarble data.
* Add background thread loading of DEM files.
* Add support for the TMS interface provided by SPOTMaps
* Add license related properties
* Add copyright property
* Improve key binding for Mercator Mode -> ctrl+m
* Add OSM WMS Server
* Add support for WMS-C
* Add support for more standard TMS
* Add LatLon projection
* Add a perl script to auto generate basic Viking .vik files for directories containing images.
* Mon Mar 21 2011 Eric S. Raymond <esr@snark.thyrsus.com> - 2.96~dev
Bumped maximum channel count to 32 to accommodate GPS+GLONASS devices.
API version bumped to 5, redesign finished (changes are documented
in the Client HOWTO). cgps now handles resize signals. Code can now
link with uClibc for embedded use. Various bugs in the C++ binding
have been fixed. gpxlogger can now daemonize and write to a specified
log file. A gpsd client can now set any locale it likes, and JSON
will still be parsed using the C locale matching the daemon's. Clients
are no longer required to define a gpsd_report() hook. gpsd no longer
emits probe strings to unidentified USB devices at startup.
JSON timestamps in TPV and SKY are now ISO8601 rather than seconds since
the Unix epoch; the library handles the older style backward-compatibly.
GPGST sentences are now parsed for noise statistics when a device emits them.
AIS and RTCM2 JSON dumps have device fields. JSON reports now include 50bps
subframe data if the device allows access to it. gpsdecode can now dump NMEA
GPS binary, and subframe data to JSON. The RTCM2 code now understands and
analyzes RTCM2.3 messages 13, 14, and 31, and has been checked against another
analyzer. The ancient Sager dump format for RTCM2 is abolished in favor of
a JSON profile.
pst-geo is a set of PSTricks related packages for various cartographic
projections of the terrestrial sphere. The package pst-map2d provides
conventional projections such as Mercator, Lambert, cylindrical, etc.
The package pst-map3d treats representation in three dimensions of the
terrestrial sphere. Packages pst-map2dII and pst-map3dII allow use of
the CIA World DataBank II. Various parameters of the packages allow for
choice of the level of the detail and the layouts possible (cities,
borders, rivers etc). Substantial data files are provided, in an
(internally) compressed format. Decompression happens on-the-fly as a
document using the data is displayed, printed or converted to PDF
format. A Perl script is provided for the user to do the decompression,
if the need should arise.
The changes are fully described at
http://trac.osgeo.org/gdal/wiki/Release/1.8.0-News
However, the following are the highlights.
In a nutshell:
* New GDAL drivers : GTX, HF2, JPEGLS, JP2OpenJPEG, JPIPKAK,
KMLSUPEROVERLAY, LOS/LAS, MG4Lidar, NTv2, OZI, PDF, RASDAMAN,
XYZ
* New OGR drivers : AeronavFAA, ArcObjects, GPSBabel, HTF, LIBKML,
MSSQLSpatial, NAS, OpenAir, PDS, PGDump, SOSI, SUA, WFS
* Significantly improved OGR drivers : DXF, GML
* New implemented RFCs:
o RFC 7: Use VSILFILE for VSI*L Functions
o RFC 24: Progressive data support in GDAL
o RFC 28: OGR SQL Generalized Expressions
o RFC 29: OGR Set Ignored Fields
o RFC 30: Unicode Filenames
o RFC 33: GTIFF - Corrected !PixelIsPoint Interpretation
* New utility : gdallocationinfo
Backward compatibility issues:
* MITAB driver: use "," for the OGR Feature Style id: parameter
delimiter, not "." as per the spec. Known impacted application:
MapServer?
* RFC 33 changes the way PixelIsPoint? is handled for GeoTIFF
* GML driver: write valid <gml:MultiGeometry> element instead of
the non-conformant <gml:GeometryCollection>. For backward
compatibility, recognize both syntax for the reading part
