-
Notifications
You must be signed in to change notification settings - Fork 0
/
NEWS
1819 lines (1392 loc) · 74.2 KB
/
NEWS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
A reverse chronological list of changes to GeographicLib
For more information, see
https://geographiclib.sourceforge.io/
The current version of the library is 1.51
Changes between 1.51 (released 2020-11-22) and 1.50.1 versions:
* C++11 compiler required for C++ library. As a consequence:
+ The workaround implementations for C++11 routines (Math::hypot,
Math::expm1, Math::log1p, Math::asinh, Math::atanh,
Math::copysign, Math::cbrt, Math::remainder, Math::remquo,
Math::round, Math::lround, Math::fma, Math::isfinite, and
Math::isnan) are now deprecated. Just use the versions in the
std:: namespace instead.
+ SphericalEngine class, fix the namespace for using streamoff.
+ Some templated functions, e.g., Math::degree(), now have default
template parameters, T = Math::real.
* C99 compiler required for C library.
* Reduce memory footprint in Java implementation.
* New form of Utility::ParseLine to allow the syntax "KEY = VAL".
* Add International Geomagnetic Reference Field (13th generation),
igrf13, which approximates the main magnetic field of the earth for
the period 1900-2025.
* More symbols allowed with DMS decoding in C++, JS, and cgi-bin
packages; see DMS::Decode.
* Fix bug in cgi-bin argument processing which causes "+" to be
misinterpreted.
* Required minium version of CMake is now 3.7.0 (released
2016-11-11). This is to work around a bug in find_package for
cmake 3.4 and 3.5.
Changes between 1.50.1 (released 2019-12-13) and 1.50 versions:
* Add the World Magnetic Model 2020, wmm2020, covering the period
2020-2025. This is now the model returned by
MagneticModel::DefaultMagneticName and is default magnetic model
for MagneticField (replacing wmm2015v2 which is only valid thru
the end of 2019).
* Include float instantiations of those templated Math functions
which migrated to Math.cpp in version 1.50.
* WARNING: The next version of GeographicLib will require a C++11
compliant compiler. This means that the minimum version of Visual
Studio will be Visual Studio 12 2013. (This repeats the warning
given with version 1.50. It didn't apply to this version because
this is a minor update.)
Changes between 1.50 (released 2019-09-24) and 1.49 versions:
* BUG fixes:
+ Java + JavaScript implementations of PolygonArea::TestEdge
counted the pole encirclings wrong.
+ Fix typo in JavaScript implementation which affected unsigned
areas.
+ Adding edges to a polygon counted pole encirclings inconsistent
with the way the adding point counted them. This might have
caused an incorrect result if a polygon vertex had longitude =
0. This affected all implementations except Fortran and
MATLAB).
+ GARS::Forward: fix BUG in handling of longitude = +/-180d.
+ Fix bug in Rhumb class and RhumbSolve(1) utiity which caused
incorrect area to be reported if an endpoint is at a pole.
Thanks to Natalia Sabourova for reporting this.
+ Fix bug in MATLAB routine mgrs_inv which resulted in incorrect
results for UPS zones with prec = -1.
+ In geodreckon.m geoddistance.m, suppress (innocuous) "warning:
division by zero" messages from Octave.
+ In python implementation, work around problems caused by
sin(inf) and fmod(inf) raising exceptions.
+ Geoid class, fix the use of streamoff.
* The PolygonArea class, the Planimeter utility, and their equivalents
in C, Fortran, MATLAB, Java, JavaScript, Python, and Maxima can now
handle arbitrarily complex polygons. In the case of
self-intersecting polygons the area is accumulated "algebraically",
e.g., the areas of the 2 loops in a figure-8 polygon will partially
cancel.
* Changes in gravity and magnetic model handling
+ SphericalEngine::coeff::readcoeffs takes new optional argument
truncate.
+ The constructors for GravityModel and MagneticModel allow the
maximum degree and order to be specified. The array of
coefficients will then be truncated if necessary.
+ GravityModel::Degree(), GravityModel::Order(),
MagneticModel::Degree(), MagneticModel::Order() return the
maximum degree and order of all the components of a GravityModel
or MagneticModel.
+ Gravity and MagneticField utilities accept -N and -M options to
to allow the maximum degree and order to be specified.
* The GeodSolve allows fractional distances to be entered as fractions
(with the -F flag).
* MajorRadius() methods are now called EquatorialRadius() for the C++,
Java, and .NET libraries. "Equatorial" is more descriptive in the
case of prolate ellipsoids. MajorRadius() is retained for backward
compatibility for C++ and Java but is deprecated.
* Minimum version updates:
+ CMake = 3.1.0, released 2014-12-15.
+ Minimum g++ version = 4.8.0, released 2013-03-22.
+ Visual Studio 10 2010 (haven't been able to check Visual Studio
2008 for a long time).
+ WARNING: The next version of GeographicLib will require a C++11
compliant compiler. This means that the minimum version of
Visual Studio will be Visual Studio 12 2013.
+ Minimum boost version = 1.64 needed for GEOGRAPHICLIB_PRECISION
= 4.
+ Java = 1.6; this allows the removal of epsilon, min, hypot,
log1p, copysign, cbrt from GeoMath.
* CMake updates:
+ Fine tune Visual Studio compatibility check in
find_package(GeographicLib); this allows GeographicLib compiled
with Visual Studio 14 2015 to be used with a project compiled
with Visual Studio 15 2017 and 16 2019.
+ Suppress warnings with dotnet build.
+ Change CMake target names and add an interface library (thanks
to Matthew Woehlke).
+ Remove pre-3.1.0 cruft and update the documentation to remove
the need to call include_dirctories.
+ Add _d suffix to example and test programs.
+ Changer installation path for binary installer to the Windows
default.
+ Add support for Intel compiler (for C++, C, Fortran). This
entails supplying the -fp-model precise flag to prevent the
compiler from incorrectly simplying (a + b) + c and 0.0 + x.
* Add version 2 of the World Magnetic Model 2015, wmm2015v2. This is
now the default magnetic model for MagneticField (replacing wmm2015
which is now deprecated). Coming in 2019-12: the wmm2020 model.
* The -f flag in the scripts geographiclib-get-geoids,
geographiclib-get-gravity, and geographiclib-get-magnetic, allows
you to load new models (not yet in the set defined by "all"). This
is in addition to its original role of allowing you to overwrite
existing models.
* Changes in math function support:
+ Move some of the functionality from Math.hpp to Math.cpp to make
compilation of package which depend on GeographicLib less
sensitive to the current compiler environment.
+ Add Math::remainder, Math::remquo, Math::round, and
Math::lround. Also add implementations of remainder, remquo to
C implementation.
+ Math::cbrt, Math::atanh, and Math::asinh now preserve the sign
of -0. (Also: C, Java, JavaScript, Python, MATLAB. Not
necessary: Fortran because sign is a built-in function.)
+ JavaScript: fall back to Math.hypot, Math.cbrt, Math.log1p,
Math.atanh if they are available.
* When parsing DMS strings ignore various non-breaking spaces (C++ and
JavaScript).
* Improve code coverage in the tests of geodesic algorithms (C++, C,
Java, JavaScript, Python, MATLAB, Fortran).
* Old deprecated NormalGravity::NormalGravity constructor removed.
* Additions to the documentation:
+ add documentation links to ge{distance,reckon}.m;
+ clarify which solution is returned for Geocentric::Reverse.
Changes between 1.49 (released 2017-10-05) and 1.48 versions:
* Add the Enhanced Magnetic Model 2017, emm2017. This is valid for
2000 thru the end of 2021.
* Avoid potential problems with the order of initializations in DMS,
GARS, Geohash, Georef, MGRS, OSGB, SphericalEngine; this only would
have been an issue if GeographicLib objects were instantiated
globally. Now no GeographicLib initialization code should be run
prior to the entry of main().
* To support the previous fix, add an overload, Utility::lookup(const
char* s, char c).
* NearestNeighbor::Search throws an error if pts is the wrong size
(instead of merely returning no results).
* Use complex arithmetic for Clenshaw sums in TransverseMercator and
tranmerc_{fwd,inv}.m.
* Changes in cmake support:
+ fix compiler flags for GEOGRAPHICLIB_PRECISION = 4;
+ add CONVERT_WARNINGS_TO_ERRORS option (default OFF), if ON then
compiler warnings are treated as errors.
* Fix warnings about implicit conversions of doubles to bools in C++,
C, and JavaScript packages.
* Binary installers for Windows now use Visual Studio 14 2015.
Changes between 1.48 (released 2017-04-09) and 1.47 versions:
* The "official" URL for GeographicLib is now
https://geographiclib.sourceforge.io (instead of
http://geographiclib.sourceforge.net).
* The default range for longitude and azimuth is now (-180d, 180d],
instead of [-180d, 180d). This was already the case for the C++
library; now the change has been made to the other implementations
(C, Fortran, Java, JavaScript, Python, MATLAB, and Maxima).
* Changes to NearestNeighbor:
+ fix BUG in reading a NearestNeighbor object from a stream which
sometimes incorrectly caused a "Bad index" exception to be thrown;
+ add operator<<, operator>>, swap,
std::swap(NearestNeighbor&, NearestNeighbor&);
* Additions to the documentation:
+ add documentation on finding nearest neighbors;
+ normal gravity documentation is now on its own page and now has an
illustrative figure;
+ document the truncation error in the series for auxiliary
latitudes.
* Fix BUGS in MATLAB function geodreckon with mixed scalar and array
arguments.
* Workaround bug in math.fmod for Python 2.7 on 32-bit Windows
machines.
* Changes in cmake support:
+ add USE_BOOST_FOR_EXAMPLES option (default OFF), if ON search for
Boost libraries for building examples;
+ add APPLE_MULTIPLE_ARCHITECTURES option (default OFF), if ON build
for both i386 and x86_64 on Mac OS X systems;
+ don't add flag for C++11 for g++ 6.0 (since it's not needed).
* Fix compiler warnings with Visual Studio 2017 and for the C library.
Changes between 1.47 (released 2017-02-15) and 1.46 versions:
* Add NearestNeighbor class.
* Improve accuracy of area calculation (fixing a flaw introduced in
version 1.46); fix applied in Geodesic, GeodesicExact, and the
implementations in C, Fortran, Java, JavaScript, Python, MATLAB, and
Maxima.
* Generalize NormalGravity to allow oblate and prolate ellipsoids. As
a consequence a new form of constructor has been introduced and the
old form is now deprecated (and because the signatures of the two
constructors are similar, the compiler will warn about the use of
the old one).
* Changes in Math class:
+ Math::sincosd, Math::sind, Math::cosd only return -0 for the case
sin(-0);
+ Math::atan2d and Math::AngNormalize return results in (-180deg,
180deg]; this may affect the longitudes and azimuth returned by
several other functions.
* Add Utility::trim() and Utility::val<T>(); Utility::num<T>() is now
DEPRECATED.
* Changes in cmake support:
+ remove support of PACKAGE_PATH and INSTALL_PATH in cmake
configuration;
+ fix to FindGeographicLib.cmake to make it work on Debian systems;
+ use $<TARGET_PDB_FILE:tgt> (cmake version >= 3.1);
+ use NAMESPACE for exported targets;
+ geographiclib-config.cmake exports GEOGRAPHICLIB_DATA,
GEOGRAPHICLIB_PRECISION, and GeographicLib_HIGHPREC_LIBRARIES.
* Add pkg-config support for cmake and autoconf builds.
* Minor fixes:
+ fix the order of declarations in C library, incorporating the
patches in version 1.46.1;
+ fix the packaging of the python library, incorporating the patches
in version 1.46.3;
+ restrict junit dependency in the Java package to testing scope
(thanks to Mick Killianey);
+ various behind-the-scenes fixes to EllipticFunction;
+ fix documentation and default install location for Windows binary
installers;
+ fix clang compiler warnings in GeodesicExactC4 and
TransverseMercator.
Changes between 1.46 (released 2016-02-15) and 1.45 versions:
* The following BUGS have been fixed:
+ the -w flag to Planimeter(1) was being ignored;
+ in the Java package, the wrong longitude was being returned with
direct geodesic calculation with a negative distance when starting
point was at a pole (this bug was introduced in version 1.44);
+ in the JavaScript package, PolygonArea.TestEdge contained a
misspelling of a variable name and other typos (problem found by
threepointone).
* INCOMPATIBLE CHANGES:
+ make the -w flag (to swap the default order of latitude and
longitude) a toggle for all utility programs;
+ the -a option to GeodSolve(1) now toggles (instead of sets) arc
mode;
+ swap order coslon and sinlon arguments in CircularEngine class.
* Remove deprecated functionality:
+ remove gradient calculation from the Geoid class and GeoidEval(1)
(this was inaccurate and of dubious utility);
+ remove reciprocal flattening functions, InverseFlattening in many
classes and Constants::WGS84_r(); stop treating flattening > 1 as
the reciprocal flattening in constructors;
+ remove DMS::Decode(string), DMS::DecodeFraction,
EllipticFunction:m, EllipticFunction:m1, Math::extradigits,
Math::AngNormalize2, PolygonArea::TestCompute;
+ stop treating LONG_NOWRAP as an alias for LONG_UNROLL in Geodesic
(and related classes) and Rhumb;
+ stop treating full/schmidt as aliases for FULL/SCHMIDT in
SphericalEngine (and related classes);
+ remove qmake project file src/GeographicLib.pro because QtCreator
can handle cmake projects now;
+ remove deprecated Visual Studio 2005 project and solution files.
* Changes to GeodesicLine and GeodesicLineExact classes; these changes
(1) simplify the process of computing waypoints on a geodesic given
two endpoints and (2) allow a GeodesicLine to be defined which is
consistent with the solution of the inverse problem (in particular
Geodesic::InverseLine the specification of south-going lines which
pass the poles in a westerly direction by setting sin alpha_1 = -0):
+ the class stores the distance s13 and arc length a13 to a
reference point 3; by default these quantities are NaNs;
+ GeodesicLine::SetDistance (and GeodesicLine::SetArc) specify the
distance (and arc length) to point 3;
+ GeodesicLine::Distance (and GeodesicLine::Arc) return the distance
(and arc length) to point 3;
+ new methods Geodesic::InverseLine and Geodesic::DirectLine return
a GeodesicLine with the reference point 3 defined as point 2 of
the corresponding geodesic calculation;
+ these changes are also included in the C, Java, JavaScript, and
Python packages.
* Other changes to the geodesic routines:
+ more accurate solution of the inverse problem when longitude
difference is close to 180deg (also in C, Fortran, Java,
JavaScript, Python, MATLAB, and Maxima packages);
+ more accurate calculation of lon2 in the inverse calculation with
LONG_UNROLL (also in Java, JavaScript, Python packages).
* Changes to GeodSolve(1) utility:
+ the -I and -D options now specify geodesic line calculation via
the standard inverse or direct geodesic problems;
+ rename -l flag to -L to parallel the new -I and -D flags (-l is is
retained for backward compatibility but is deprecated), and
similarly for RhumbSolve(1);
+ the -F flag (in conjunction with the -I or -D flags) specifies
that distances read on standard input are fractions of s13 or a13;
+ the -a option now toggles arc mode (noted above);
+ the -w option now toggles longitude first mode (noted above).
* Changes to Math class:
+ Math::copysign added;
+ add overloaded version of Math::AngDiff which returns the error in
the difference. This allows a more accurate treatment of inverse
geodesic problem when lon12 is close to 180deg;
+ Math::AngRound now converts tiny negative numbers to -0 (instead
of +0), however -0 is still converted to +0.
* Add -S and -T options to GeoConvert(1).
* Add Sphinx documentation for Python package.
* Samples of wrapping the C++ library, so it's accessible in other
languages, are given in wrapper/C, wrapper/python, and
wrapper/matlab.
* Binary installers for Windows now use Visual Studio 12 2013.
* Remove top-level pom.xml from release (it was specific to SRI).
* A reminder: because of the JavaScript changes introduced in version
1.45, you should remove the following installation directories from
your system:
+ Windows: ${CMAKE_INSTALL_PREFIX}/doc/scripts
+ Others: ${CMAKE_INSTALL_PREFIX}/share/doc/GeographicLib/scripts
Changes between 1.45 (released 2015-09-30) and 1.44 versions:
* Fix BUG in solution of inverse geodesic caused by misbehavior of
some versions of Visual Studio on Windows (fmod(-0.0, 360.0) returns
+0.0 instead of -0.0) and Octave (sind(-0.0) returns +0.0 instead of
-0.0). These bugs were exposed because max(-0.0, +0.0) returns -0.0
for some languages.
* Geodesic::Inverse now correctly returns NaNs if one of the latitudes
is a NaN.
* Changes to JavaScript package:
+ thanks to help from Yurij Mikhalevich, it is a now a node package
that can be installed with npm;
+ make install now installs the node package in
lib/node_modules/geographiclib;
+ add unit tests using mocha;
+ add documentation via JSDoc;
+ fix bug Geodesic.GenInverse (this bug, introduced in version 1.44,
resulted in the wrong azimuth being reported for points at the
pole).
* Changes to Java package:
+ add implementation of ellipsoidal Gnomonic projection (courtesy of
Sebastian Mattheis);
+ add unit tests using JUnit;
+ Math.toRadians and Math.toDegrees are used instead of
GeoMath.degree (which is now removed), as a result...
+ Java version 1.2 (released 1998-12) or later is now required.
* Changes to Python package:
+ add unit tests using the unittest framework;
+ fixed bug in normalization of the area.
* Changes to MATLAB package:
+ fix array size mismatch in geoddistance by avoiding calls to
subfunctions with zero-length arrays;
+ fix tranmerc_{fwd,inv} so that they work with arrays and mixed
array/scalar arguments;
+ work around Octave problem which causes mgrs_fwd to return garbage
with prec = 10 or 11;
+ add geographiclib_test.m to run a test suite.
* Behavior of substituting 1/f for f if f > 1 is now deprecated. This
behavior has been removed from the JavaScript, C, and Python
implementations (it was never documented). Maxima, MATLAB, and
Fortran implementations never included this behavior.
* Other changes:
+ fix bug, introduced in version 1.42, in the C++ implementation to
the computation of area which causes NaNs to be returned in the
case of a sphere;
+ fixed bug, introduced in version 1.44, in the detection of C++11
math functions in configure.ac;
+ throw error on non-convergence in Gnomonic::Reverse if
GEOGRAPHICLIB_PRECISION > 3;
+ add geod_polygon_clear to C library;
+ turn illegal latitudes into NaNs for Fortran library;
+ add test suites for the C and Fortran libraries.
Changes between 1.44 (released 2015-08-14) and 1.43 versions:
* Various changes to improve accuracy, e.g., by minimizing round-off
errors:
+ Add Math::sincosd, Math::sind, Math::cosd which take their
arguments in degrees. These functions do exact range reduction
and thus they obey exactly the elementary properties of the
trigonometric functions, e.g., sin 9d = cos 81d
= - sin 123456789d.
+ Math::AngNormalize now works for any angles, instead of angles in
the range [-540d, 540d); the function Math::AngNormalize2 is now
deprecated.
+ This means that there is now no restriction on longitudes and
azimuths; any values can be used.
+ Improve the accuracy of Math::atan2d.
+ DMS::Decode avoids unnecessary round-off errors; thus 7:33:36 and
7.56 result in identical values. DMS::Encode rounds ties to even.
These changes have also been made to DMS.js.
+ More accurate rounding in MGRS::Reverse and mgrs_inv.m; this
change only makes a difference at sub-meter precisions.
+ With MGRS::Forward and mgrs_fwd.m, ensure that digits in lower
precision results match those at higher precision; as a result,
strings of trailing 9s are less likely to be generated. This
change only makes a difference at sub-meter precisions.
+ Replace the series for A2 in the Geodesic class with one with
smaller truncation errors.
+ Geodesic::Inverse sets s12 to zero for coincident points at pole
(instead of returning a tiny quantity).
+ Math::LatFix returns its argument if it is in [-90d, 90d]; if not,
it returns NaN.
+ Using Math::LatFix, routines which don't check their arguments now
interpret a latitude outside the legal range of [-90d, 90d] as a
NaN; such routines will return NaNs instead of finite but
incorrect results; caution: code that (dangerously) relied on the
"reasonable" results being returned for values of the latitude
outside the allowed range will now malfunction.
* All the utility programs accept the -w option to swap the
latitude-longitude order on input and output (and where appropriate
on the command-line arguments). CartConvert now accepts the -p
option to set the precision; now all of the utilities except
GeoidEval accept -p.
* Add classes for GARS, the Global Area Reference System, and for
Georef, the World Geographic Reference System.
* Changes to DMS::Decode and DMS.js:
+ tighten up the rules:
o 30:70.0 and 30:60 are illegal (minutes and second must be
strictly less than 60), however
o 30:60.0 and 30:60. are legal (floating point 60 is OK, since it
might have been generated by rounding 59.99...);
+ generalize a+b concept, introduced in version 1.42, to any number
of pieces; thus 8+0:40-0:0:10 is interpreted as 8:39:50.
* Documentation fixes:
+ update man pages to refer to GeoConvert(1) on handling of
geographic coordinates;
+ document limitations of the series used for TransverseMercator;
+ hide the documentation of the computation of the gradient of the
geoid height (now deprecated) in the Geoid class;
+ warn about the possible misinterpretation of 7.0E+1 by
DMS::Decode;
+ swaplatlong optional argument of DMS::DecodeLatLon and various
functions in the GeoCoords class is now called longfirst;
+ require Doxygen 1.8.7 or later.
* More systematic treatment of version numbers:
+ Python: __init__.py defines __version__ and __version_info__;
+ JavaScript:
o Math.js defines Constants.version and Constants.version_string;
o version number included as comment in packed script
geographiclib.js;
o geod-calc.html and geod-google.html report the version number;
o https://geographiclib.sourceforge.io/scripts/ gives access to
earlier versions of geographiclib.js as geographiclib-m.nn.js;
+ Fortran: add geover subroutine to return version numbers;
+ Maxima: geodesic.mac defines geod_version;
+ CGI scripts: these report the version numbers of the utilities.
* BUG FIXES:
+ NormalGravity now works properly for a sphere (omega = f = J2 =
0), instead of returning NaNs (problem found by htallon);
+ CassiniSoldner::Forward and cassini_fwd.m now returns the correct
azimuth for points at the pole.
* MATLAB-specific fixes:
+ mgrs_fwd now treats treats prec > 11 as prec = 11;
+ illegal letter combinations are now correctly detected by
mgrs_inv;
+ fixed bug where mgrs_inv returned the wrong results for prec = 0
strings and center = 0;
+ mgrs_inv now decodes prec = 11 strings properly;
+ routines now return array results with the right shape;
+ routines now properly handle mixed scalar and array arguments.
* Add Accumulator<T>::operator*=(T y).
* Geohash uses "invalid" instead of "nan" when the latitude or
longitude is a nan.
Changes between 1.43 (released 2015-05-23) and 1.42 versions:
* Add the Enhanced Magnetic Model 2015, emm2015. This is valid for
2000 thru the end of 2019. This required some changes in the
MagneticModel and MagneticCircle classes; so this model cannot be
used with versions of GeographicLib prior to 1.43.
* Fix BLUNDER in PolarStereographic constructor introduced in version
1.42. This affected UTMUPS conversions for UPS which could be
incorrect by up to 0.5 km.
* Changes in the LONG_NOWRAP option (added in version 1.39) in the
Geodesic and GeodesicLine classes:
+ The option is now called LONG_UNROLL (a less negative sounding
term); the original name, LONG_NOWRAP, is retained for backwards
compatibility.
+ There were two bad BUGS in the implementation of this capability:
(a) it gave incorrect results for west-going geodesics; (b) the
option was ignored if used directly via the GeodesicLine class.
The first bug affected the implementations in all languages. The
second affected the implementation in C++ (GeodesicLine and
GeodesicLineExact), JavaScript, Java, C, Python. These bugs have
now been FIXED.
+ The GeodSolve utility now accepts a -u option, which turns on the
LONG_UNROLL treatment. With this option lon1 is reported as
entered and lon2 is given such that lon2 - lon1 indicates how
often and in what sense the geodesic has encircled the earth.
(This option also affects the value of longitude reported when an
inverse calculation is run with the -f option.)
+ The inverse calculation with the JavaScript and python libraries
similarly sets lon1 and lon2 in output dictionary respecting the
LONG_UNROLL flag.
+ The online version of GeodSolve now offers an option to unroll the
longitude.
+ To support these changes DMS::DecodeLatLon no longer reduces the
longitude to the range [-180deg, 180deg) and Math::AngRound now
coverts -0 to +0.
* Add Math::polyval (also to C, Java, JavaScript, Fortran, python
versions of the library; this is a built-in function for
MATLAB/Octave). This evaluates a polynomial using Horner's method.
The Maxima-generated code fragments for the evaluation of series in
the Geodesic, TransverseMercator, and Rhumb classes and MATLAB
routines for great ellipses have been replaced by Maxima-generated
arrays of polynomial coefficients which are used as input to
Math::polyval.
* Add MGRS::Check() to verify that a, f, k_UTM, and k_UPS are
consistent with the assumptions in the UTMUPS and MGRS classes.
This is invoked with GeoConvert --version. (This function was added
to document and check the assumptions used in the UTMUPS and MGRS
classes in case they are extended to deal with ellipsoids other than
WS84.)
* MATLAB function mgrs_inv now takes an optional center argument and
strips white space from both beginning and end of the string.
* Minor internal changes:
+ GeodSolve sets the geodesic mask so that unnecessary calculations
are avoided;
+ some routines have migrated into a math class for for python,
Java, JavaScript libraries.
* A reminder: because of changes in the installation directories for
non-Windows systems introduced in version 1.42, you should remove
the following directories from your system:
+ ${CMAKE_INSTALL_PREFIX}/share/cmake/GeographicLib*
+ ${CMAKE_INSTALL_PREFIX}/libexec/GeographicLib/matlab
Changes between 1.42 (released 2015-04-28) and 1.41 versions:
* DMS::Decode allows a single addition or subtraction operation, e.g.,
70W+0:0:15. This affects the GeoCoords class and the utilities
(which use the DMS class for reading coordinates).
* Add Math::norm, Math::AngRound, Math::tand, Math::atan2d,
Math::eatanhe, Math::taupf, Math::tauf, Math::fma and remove
duplicated (but private) functionality from other classes.
* On non-Windows systems, the cmake config-style find_package files
are now installed under ${CMAKE_INSTALL_PREFIX}/lib${LIB_SUFFIX}
instead of ${CMAKE_INSTALL_PREFIX}/share, because the files are
architecture-specific. This change will let 32-bit and 64-bit
versions coexist on the same machine (in lib and lib64). You should
remove the versions in the old "share" location.
* MATLAB changes:
+ provide native MATLAB implementations for compiled interface
functions;
+ the compiled MATLAB interface is now deprecated and so the
MATLAB_COMPILER option in the cmake build has been removed;
+ reorganize directories, so that
o matlab/geographiclib contains the native matlab code;
o matlab/geographiclib-legacy contains wrapper functions to mimic
the previous compiled functionality;
+ the installed MATLAB code mirrors this layout, but the parent
installation directory on non-Windows systems is
${CMAKE_INSTALL_PREFIX}/share (instead of
${CMAKE_INSTALL_PREFIX}/libexec), because the files are now
architecture independent;
+ matlab/geographiclib is now packaged and distributed as MATLAB
File Exchange package 50605 (this supersedes three earlier MATLAB
packages);
+ point fix for geodarea.m to correct bug in area of polygons which
encircle a pole multiple times (released as version 1.41.1 of
MATLAB File Exchange package 39108, 2014-04-22).
* artifactId for Java package changed from GeographicLib to
GeographicLib-Java and the package is now deployed to Maven Central
(thanks to Chris Bennight for help on this).
* Fix autoconf mismatch of version numbers (which were inconsistent in
versions 1.40 and 1.41).
* Mark the computation of the gradient of the geoid height in the
Geoid class and the <a href="GeoidEval.1.html">GeoidEval</a> utility
as deprecated.
* Work around the boost-quadmath bug with setprecision(0).
* Deprecate use of Visual Studio 2005 "-vc8" project files in the
windows directory.
Changes between 1.41 (released 2015-03-09) and 1.40 versions:
* Fix bug in Rhumb::Inverse (with exact = true) and related functions
which causes the wrong distance to be reported if one of the end
points is at a pole. Thanks to Thomas Murray for reporting this.
* Add International Geomagnetic Reference Field (12th generation),
which approximates the main magnetic field of the earth for the
period 1900-2020.
* Split information about Jacobi's conformal projection to a separate
section and include more material.
Changes between 1.40 (released 2014-12-18) and 1.39 versions:
* Add the World Magnetic Model 2015, wmm2015. This is now the default
magnetic model for MagneticField (replacing wmm2010 which is valid
thru the end of 2014).
* Geodesic::Inverse didn't return NaN if one of the longitudes was a
NaN (bug introduced in version 1.25). Fixed in the C++, Java,
JavaScript, C, Fortran, and Python implementations of the geodesic
routines. This bug was not present in the Matlab version.
* Fix bug in Utility::readarray and Utility::writearray which caused
an exception in debug mode with zero-sized arrays.
* Fix BLUNDER in OSGB::GridReference (found by kalderami) where the
wrong result was returned if the easting or northing was negative.
* OSGB::GridReference now returns "INVALID" if either coordinate is
NaN. Similarly a grid reference starting with "IN" results in NaNs
for the coordinates.
* Default constructor for GeoCoords corresponds to an undefined
position (latitude and longitude = NaN), instead of the north pole.
* Add an online version of RhumbSolve at
https://geographiclib.sourceforge.io/cgi-bin/RhumbSolve.
* Additions to the documentation:
+ documentation on Jacobi's conformal projection;
+ a page on Auxiliary latitudes (actually, this was added in
version 1.39);
+ document the use of two single quotes to stand for a double quote
in DMS (this feature was introduced in version 1.13).
* The Matlab function, geographiclibinterface, which compiles the
wrapper routines for Matlab now works with Matlab 2014b on a Mac.
Changes between 1.39 (released 2014-11-11) and 1.38 versions:
* GeographicLib usually normalizes longitudes to the range [-180deg,
180deg). However, when solving the direct geodesic and rhumb line
problems, it is sometimes necessary to know how many lines the line
encircled the earth by returning the longitude "unwrapped". So the
following changes have been made:
+ add a LONG_NOWRAP flag to mask enums for the outmask arguments for
Geodesic, GeodesicLine, Rhumb, and RhumbLine;
+ similar changes have been made to the Python, Javascript, and
Java implementations of the geodesic routines;
+ for the C, Fortran, and Matlab implementations the arcmode
argument to the routines was generalized to allow a combination of
ARCMODE and LONG_NOWRAP bits;
+ the Maxima version now returns the longitude unwrapped.
These changes were necessary to fix the PolygonAreaT::AddEdge (see
the next item).
* Changes in area calculations:
+ fix BUG in PolygonAreaT::AddEdge (also in C, Java, Javascript, and
Python implementations) which sometimes causes the wrong area to
be returned if the edge spanned more than 180deg;
+ add area calculation to the Rhumb and RhumbLine classes and the
RhumbSolve utility;
+ add PolygonAreaRhumb typedef for PolygonAreaT<Rhumb>;
+ add -R option to Planimeter to use PolygonAreaRhumb (and -G option
for the default geodesic polygon);
+ fix BLUNDER in area calculation in Matlab routine geodreckon;
+ add area calculation to Matlab/Octave routines for great ellipses.
* Fix bad BUG in Geohash::Reverse; this was introduced in version 1.37
and affected all platforms where unsigned longs are 32-bits. Thanks
to Christian Csar for reporting and diagnosing this.
* Binary installers for Windows are now built with Visual Studio 11
2012 (instead of Visual Studio 10 2010). Compiled Matlab support
still with version 2013a (64-bit).
* Update GeographicLib.pro for builds with qmake to include all the
source files.
* Cmake updates:
+ include cross-compiling checks in cmake config file;
+ improve the way unsuitable versions are reported;
+ include_directories (${GeographicLib_INCLUDE_DIRS}) is no longer
necessary with cmake 2.8.11 or later.
* legacy/Fortran now includes drop-in replacements for the geodesic
utilities from the NGS.
* geographiclib-get-{geoids,gravity,magnetic} with no arguments now
print the usage instead of loading the minimal sets.
* Utility::date(const std::string&, int&, int&, int&) and hence the
MagneticField utility accepts the string "now" as a legal time
(meaning today).
Changes between 1.38 (released 2014-10-02) and 1.37 versions:
* On MacOSX, the installed package is relocatable (for cmake version
2.8.12 and later).
* On Mac OSX, GeographicLib can be installed using homebrew.
* In cmake builds under Windows, set the output directories so that
binaries and shared libraries are together.
* Accept the minus sign as a synonym for - in DMS.{cpp,js}.
* The cmake configuration file geographiclib-depends.cmake has been
renamed to geographiclib-targets.cmake.
* Matlab/Octave routines for great ellipses added.
* Provide man pages for geographiclib-get-{geoids,gravity,magnetic}.
Changes between 1.37 (released 2014-08-08) and 1.36 versions:
* Add support for high precision arithmetic.
* INCOMPATIBLE CHANGE: the static instantiations of various classes
for the WGS84 ellipsoid have been changed to a "construct on first
use idiom". This avoids a lot of wasteful initialization before the
user's code starts. Unfortunately it means that existing source
code that relies on any of the following static variables will need
to be changed to a function call:
+ AlbersEqualArea::AzimuthalEqualAreaNorth
+ AlbersEqualArea::AzimuthalEqualAreaSouth
+ AlbersEqualArea::CylindricalEqualArea
+ Ellipsoid::WGS84
+ Geocentric::WGS84
+ Geodesic::WGS84
+ GeodesicExact::WGS84
+ LambertConformalConic::Mercator
+ NormalGravity::GRS80
+ NormalGravity::WGS84
+ PolarStereographic::UPS
+ TransverseMercator::UTM
+ TransverseMercatorExact::UTM
Thus, occurrences of, for example,
const Geodesic& geod = Geodesic::WGS84; // version 1.36 and earlier
need to be changed to
const Geodesic& geod = Geodesic::WGS84(); // version 1.37 and later
(note the parentheses!); alternatively use
// works with all versions
const Geodesic geod(Constants::WGS84_a(), Constants::WGS84_a());
* Incompatible change: the environment variables
{GEOID,GRAVITY,MAGNETIC}_{NAME,PATH} are now prefixed with
GEOGRAPHICLIB_.
* Incompatible change for Windows XP: retire the Windows XP common
data path. If you're still using Windows XP, then you might have to
move the folder C:\Documents and Settings\All Users\Application
Data\GeographicLib to C:\ProgramData\GeographicLib.
* All macro names affecting the compilation now start with
GEOGRAPHICLIB_; this applies to GEOID_DEFAULT_NAME,
GRAVITY_DEFAULT_NAME, MAGNETIC_DEFAULT_NAME, PGM_PIXEL_WIDTH,
HAVE_LONG_DOUBLE, STATIC_ASSERT, WORDS_BIGENDIAN.
* Changes to PolygonArea:
+ introduce PolygonAreaT which takes a geodesic class as a
parameter;
+ PolygonArea and PolygonAreaExact are typedef'ed to
PolygonAreaT<Geodesic> and PolygonAreaT<GeodesicExact>;
+ add -E option to Planimeter to use PolygonAreaExact;
+ add -Q option to Planimeter to calculate the area on the authalic
sphere.
* Add -p option to Planimeter, ConicProj, GeodesicProj,
TransverseMercatorProj.
* Add Rhumb and RhumbLine classes and the RhumbSolve utility.
* Minor changes to NormalGravity:
+ add J2ToFlattening and FlatteningToJ2;
+ use Newton's method to determine f from J2;
+ in constructor, allow omega = 0 (i.e., treat the spherical case).
* Add grs80 GravityModel.
* Make geographiclib-get-{geoids,gravity,magnetic} scripts work on
MacOS.
* Minor changes:
+ simplify cross-platform support for C++11 mathematical functions;
+ change way area coefficients are given in GeodesicExact to improve
compile times;
+ enable searching the online documentation;
+ add macros GEOGRAPHICLIB_VERSION and GEOGRAPHICLIB_VERSION_NUM;
+ add solution and project files for Visual Studio Express 2010.
Changes between 1.36 (released 2014-05-13) and 1.35 versions:
* Changes to comply with NGA's prohibition of the use of the
upper-case letters N/S to designate the hemisphere when displaying
UTM/UPS coordinates:
+ UTMUPS::DecodeZone allows north/south as hemisphere designators
(in addition to n/s);
+ UTMUPS::EncodeZone now encodes the hemisphere in lower case (to
distinguish this use from a grid zone designator);
+ UTMUPS::EncodeZone takes an optional parameter abbrev to
indicate whether to use n/s or north/south as the hemisphere
designator;
+ GeoCoords::UTMUPSRepresentation and AltUTMUPSRepresentation
similarly accept the abbrev parameter;
+ GeoConvert uses the flags -a and -l to govern whether UTM/UPS
output uses n/s (the -a flag) or north/south (the -l flag) to
denote the hemisphere;
+ Fixed a bug what allowed +3N to be accepted as an alternation
UTM zone designation (instead of 3N).
WARNING: The use of lower case n/s for the hemisphere might cause
compatibility problems. However DecodeZone has always accepted
either case; so the issue will only arise with other software
reading the zone information. To avoid possible misinterpretation
of the zone designator, consider calling EncodeZone with abbrev =
false and GeoConvert with -l, so that north/south are used to
denote the hemisphere.
* MGRS::Forward with prec = -1 will produce a grid zone designation.
Similarly MGRS::Reverse will decode a grid zone designation (and
return prec = -1).
* Stop using the throw() declaration specification which is
deprecated in C++11.
* Add missing std:: qualifications to copy in LocalCartesion and
Geocentric headers (bug found by Clemens).
Changes between 1.35 (released 2014-03-13) and 1.34 versions:
* Fix blunder in UTMUPS::EncodeEPSG (found by Ben Adler).
* Matlab wrapper routines geodesic{direct,inverse,line} switch to
"exact" routes if |f| > 0.02.
* GeodSolve.cgi allows ellipsoid to be set (and uses the -E option
for GeodSolve).
* Set title in HTML versions of man pages for the utility programs.
* Changes in cmake support:
+ add _d to names of executables in debug mode of Visual Studio;
+ add support for Android (cmake-only), thanks to Pullan Yu;
+ check CPACK version numbers supplied on command line;
+ configured version of project-config.cmake.in is
project-config.cmake (instead of geographiclib-config.cmake), to
prevent find_package incorrectly using this file;
+ fix tests with multi-line output;
+ this release includes a file, pom.xml, which is used by an
experimental build system (based on maven) at SRI.
Changes between 1.34 (released 2013-12-11) and 1.33 versions:
* Many changes in cmake support:
+ minimum version of cmake needed increased to 2.8.4 (which was
released in 2011-02);
+ allow building both shared and static librarys with
-D GEOGRAPHICLIB_LIB_TYPE=BOTH;
+ both shared and static libraries (Release plus Debug) included in
binary installer;
+ find_package uses COMPONENTS and GeographicLib_USE_STATIC_LIBS to
select the library to use;
+ find_package version checking allows nmake and Visual Studio
generators to interoperate on Windows;
+ find_package (GeographicLib ...) requires that GeographicLib be
capitalized correctly;
+ on Unix/Linux, don't include the version number in directory for
the cmake configuration files;
+ defaults for GEOGRAPHICLIB_DOCUMENTATION and
BUILD_NETGEOGRAPHICLIB are now OFF;
+ the GEOGRAPHICLIB_EXAMPLES configuration parameter is no longer
used; cmake always configures to build the examples, but they are
not built by default (instead build targets: exampleprograms and
netexamples);
+ matlab-all target renamed to matlabinterface;
+ the configuration parameters PACKAGE_PATH and INSTALL_PATH are
now deprecated (use CMAKE_INSTALL_PREFIX instead);
+ on Linux, the installed package is relocatable;
+ on MacOSX, the installed utilities can find the shared library.
* Use a more precise value for OSGB::CentralScale().
* Add Arc routines to python interface.
* The Geod utility has been removed; the same functionality lives on
with GeodSolve (introduced in version 1.30).
Changes between 1.33 (released 2013-10-08) and 1.32 versions:
* Add NETGeographic .NET wrapper library (courtesy of Scott Heiman).
* Make inspector functions in GeographicLib::Ellipsoid const.
* Add Accumulator.cpp to instantiate GeographicLib::Accumulator.
* Defer some of the initialization of GeographicLib::OSGB to when it
is first called.
* Fix bug in autoconf builds under MacOS.
Changes between 1.32 (released 2013-07-12) and 1.31 versions:
* Generalize C interface for polygon areas to allow vertices to be
specified incrementally.
* Fix way flags for C++11 support are determined.
Changes between 1.31 (released 2013-07-01) and 1.30 versions:
* Changes breaking binary compatibility (source compatibility is
maintained):
+ overloaded versions of DMS::Encode,
EllipticFunction::EllipticFunction, and
GeoCoords::DMSRepresentation, have been eliminated by the use of