diff options
48 files changed, 100 insertions, 99 deletions
diff --git a/docs/source/apps/projsync.rst b/docs/source/apps/projsync.rst index 9756e0c4..d79bd87b 100644 --- a/docs/source/apps/projsync.rst +++ b/docs/source/apps/projsync.rst @@ -110,7 +110,7 @@ The following control parameters can appear in any order: .. option:: --dry-run - Simulate the behaviour of the tool without downloading resource files. + Simulate the behavior of the tool without downloading resource files. .. option:: --list-files diff --git a/docs/source/community/rfc/rfc-2.rst b/docs/source/community/rfc/rfc-2.rst index df6f742d..4cea339d 100644 --- a/docs/source/community/rfc/rfc-2.rst +++ b/docs/source/community/rfc/rfc-2.rst @@ -405,7 +405,7 @@ be combined together. - `alias_names`: list possible alias for the `name` field of object table - `link_from_deprecated_to_non_deprecated`: to handle the link between old ESRI to new ESRI/EPSG codes -- Commmon: +- Common: - `unit_of_measure`: table with UnitOfMeasure definitions. - `area`: table with area-of-use (bounding boxes) applicable to CRS and coordinate operations. diff --git a/docs/source/community/rfc/rfc-3.rst b/docs/source/community/rfc/rfc-3.rst index d3e3d14c..ae4bff95 100644 --- a/docs/source/community/rfc/rfc-3.rst +++ b/docs/source/community/rfc/rfc-3.rst @@ -120,7 +120,7 @@ development, but it is allowed in case future development of PROJ warrants an update. Changes in minimum version requirements are allowed to happen with minor version releases of PROJ. -At the time of writing the minimum version requried for SQLite it 3.7 which was +At the time of writing the minimum version required for SQLite it 3.7 which was released in 2010. CMake currently is required to be at least at version 2.8.3 which was also released in 2010. diff --git a/docs/source/community/rfc/rfc-4.rst b/docs/source/community/rfc/rfc-4.rst index 88abbe9e..0819c6f1 100644 --- a/docs/source/community/rfc/rfc-4.rst +++ b/docs/source/community/rfc/rfc-4.rst @@ -70,7 +70,7 @@ Summary of work planned by this RFC implemented. The use of grids locally available will of course still be available, and will -be the default behaviour. +be the default behavior. Network access to grids ------------------------------------------------------------------------------- @@ -220,7 +220,7 @@ The preliminary C API for the above is: To make network access efficient, PROJ will internally have a in-memory cache of file ranges to only issue network requests by chunks of 16 KB or multiple of them, to limit the number of HTTP GET requests and minimize latency caused by network -access. This is very similar to the behaviour of the GDAL +access. This is very similar to the behavior of the GDAL `/vsicurl/ <https://gdal.org/user/virtual_file_systems.html#vsicurl-http-https-ftp-files-random-access>`_ I/O layer. The plan is to mostly copy GDAL's vsicurl implementation inside PROJ, with needed adjustmeents and proper namespacing of it. @@ -495,7 +495,7 @@ Several formats exist depending on the ad-hoc needs and ideas of the original data producer. It would be appropriate to converge on a common format able to address the different use cases. -- Not tiled. Tiling is a nice to have propery for cloud-friendly access to +- Not tiled. Tiling is a nice to have property for cloud-friendly access to large files. - No support for compression - The NTv2 structures is roughly: header of main grid, data of main grid, @@ -511,13 +511,13 @@ Discussion on choice of format We have been made recently aware of other initiatives from the industry to come with a common format to store geodetic adjustment data. Some discussions have happen recently within the OGC CRS Working group. Past efforts include the -Esri's proposed Geodetic data Grid eXchange Format, GGXF, briefly mentionned at +Esri's proposed Geodetic data Grid eXchange Format, GGXF, briefly mentioned at page 86 of https://iag.dgfi.tum.de/fileadmin/IAG-docs/Travaux2015/01_Travaux_Template_Comm_1_tvd.pdf and page 66 of ftp://ftp.iaspei.org/pub/meetings/2010-2019/2015-Prague/IAG-Geodesy.pdf The current trend of those works would be to use a netCDF / HDF5 container. -So, for the sake of completness, we list hereafter a few potential candidate +So, for the sake of completeness, we list hereafter a few potential candidate formats and their pros and cons. TIFF/GeoTIFF @@ -610,7 +610,7 @@ Weak points: metadata <http://cfconventions.org/>`_ but there is nothing really handy in them for simple georeferencing with the coordinate of the upper-left pixel and the resolution. The practice is - to write explict lon and lat variables with all values taken by the grid. + to write explicit lon and lat variables with all values taken by the grid. GDAL has for many years supported a simpler syntax, using a GeoTransform attribute. @@ -652,7 +652,7 @@ Weak points: is more complex than netCDF v3, and likely more than TIFF. We do not have in-depth expertise of it to assess its cloud-friendliness. -* The ones mentionned for netCDF v3 regarding georeferencing and security apply. +* The ones mentioned for netCDF v3 regarding georeferencing and security apply. GeoPackage @@ -719,7 +719,7 @@ Build requirements The minimum libtiff version will be 4.0 (RHEL 7 ships with libtiff 4.0.3). To be able to read grids stored on the CDN, libtiff will need to build against -zlib to have DEFLATE and LZW suport, which is met by all known binary distributions +zlib to have DEFLATE and LZW support, which is met by all known binary distributions of libtiff. The libtiff dependency can be disabled at build time, but this must be diff --git a/docs/source/community/rfc/rfc-5.rst b/docs/source/community/rfc/rfc-5.rst index 99fec5f7..6e9bf5b7 100644 --- a/docs/source/community/rfc/rfc-5.rst +++ b/docs/source/community/rfc/rfc-5.rst @@ -96,7 +96,7 @@ Backward compatibility This change is considered to be *mostly* backward compatible. There might be impacts for software using :cpp:func:`proj_coordoperation_get_grid_used` and assuming that the url returned is one of the proj-datumgrid-xxx files at -https://download.osgeo.org. As mentionned in +https://download.osgeo.org. As mentioned in https://lists.osgeo.org/pipermail/proj/2020-January/009274.html , this assumption was not completely bullet-proof either. There will be impacts on software checking the value of PROJ pipeline strings diff --git a/docs/source/development/reference/functions.rst b/docs/source/development/reference/functions.rst index 960ed57e..d5611c9a 100644 --- a/docs/source/development/reference/functions.rst +++ b/docs/source/development/reference/functions.rst @@ -276,7 +276,7 @@ Coordinate transformation .. note:: Even though he coordinate components are named :c:data:`x`, :c:data:`y`, :c:data:`z` and :c:data:`t`, axis ordering of the to and from CRS - is respected. Transformations exhibit the same behaviour + is respected. Transformations exhibit the same behavior as if they were gathered in a :c:type:`PJ_COORD` struct. diff --git a/docs/source/faq.rst b/docs/source/faq.rst index cd545036..5a6763bc 100644 --- a/docs/source/faq.rst +++ b/docs/source/faq.rst @@ -188,6 +188,6 @@ was no longer aligned with the version number. As a consequence, it was decided to decouple the name from the version number and once again simply call the software PROJ. -Use of name PROJ.4 is now strictly reserved for describing legacy behaviour +Use of name PROJ.4 is now strictly reserved for describing legacy behavior of the software, e.g. "PROJ.4 strings" as seen in :program:`projinfo` output. diff --git a/docs/source/install.rst b/docs/source/install.rst index f6ca0d5d..dd57d22c 100644 --- a/docs/source/install.rst +++ b/docs/source/install.rst @@ -212,7 +212,7 @@ Autotools configure options Most POSIX systems may not require any options to ``./configure`` if all PROJ requirements are met, installed into common directories, and a -"default" behaviour is desired. +"default" behavior is desired. Some influential environment variables are used by ``./configure``, with no expected defaults: diff --git a/docs/source/news.rst b/docs/source/news.rst index c54232ef..3e135cba 100644 --- a/docs/source/news.rst +++ b/docs/source/news.rst @@ -167,7 +167,7 @@ Bug fixes The major feature in PROJ 7 is significantly improved handling of gridded models. This was implemented in :ref:`RFC4`. The main features of the RFC4 work is that PROJ now implements a new grid format, -Geodetic TIFF grids, for exchaning gridded transformation models. In addition +Geodetic TIFF grids, for exchanging gridded transformation models. In addition to the new grid format, PROJ can now also access grids online using a data store in the cloud. @@ -530,7 +530,7 @@ Bug Fixes * Do not include :envvar:`PROJ_LIB` in ``proj_info().searchpath`` when context search path is set (`#1498 <https://github.com/OSGeo/PROJ/issues/1498>`_) -* Use correct delimeter for the current platform when parsing +* Use correct delimiter for the current platform when parsing PROJ_LIB (`#1497 <https://github.com/OSGeo/PROJ/issues/1497>`_) * Do not confuse 'ID74' CRS with WKT2 ID[] node (`#1506 <https://github.com/OSGeo/PROJ/issues/1506>`_) @@ -691,15 +691,15 @@ UPDATES * Removed :c:func:`proj_geocentric_latitude` from `proj.h` API (`#1170 <https://github.com/OSGeo/proj.4/issues/1170>`_) -* Changed behaviour of :program:`proj`: Now only allow initialization of +* Changed behavior of :program:`proj`: Now only allow initialization of projections (`#1162 <https://github.com/OSGeo/proj.4/issues/1162>`_) -* Changed behaviour of :ref:`tmerc <tmerc>`: Now defaults to the Extended +* Changed behavior of :ref:`tmerc <tmerc>`: Now defaults to the Extended Transverse Mercator algorithm (``etmerc``). Old implementation available by adding ``+approx`` (`#404 <https://github.com/OSGeo/proj.4/issues/404>`_) -* Chaged behaviour: Default ellipsoid now set to GRS80 (was WGS84) (`#1210 <https://github.com/OSGeo/proj.4/issues/1210>`_) +* Chaged behavior: Default ellipsoid now set to GRS80 (was WGS84) (`#1210 <https://github.com/OSGeo/proj.4/issues/1210>`_) * Allow multiple directories in :envvar:`PROJ_LIB` environment variable (`#1281 <https://github.com/OSGeo/proj.4/issues/1281>`_) diff --git a/docs/source/operations/operations_computation.rst b/docs/source/operations/operations_computation.rst index 2836b75c..f1453257 100644 --- a/docs/source/operations/operations_computation.rst +++ b/docs/source/operations/operations_computation.rst @@ -135,7 +135,7 @@ performed in the order they are listed below: ballpark vertical transformation (occurs when there is a geoid model). 3. if both operations evaluate identically with respect to the above criterion, consider as more relevant an operation that does not include a synthetic - ballpark horizontal tranformation. + ballpark horizontal transformation. 4. consider as more relevant an operation that refers to shift grids that are locally available. 5. consider as more relevant an operation that refers to grids that are available in one of the proj-datumgrid packages, but not necessarily locally available @@ -149,7 +149,7 @@ performed in the order they are listed below: 10. in case of same accuracy, consider as more relevant an operation that does not use grids (operations that use only parameters will be faster) 11. consider as more relevant an operation that involves less transformation steps -12. and for completness, if two operations are comparable given all the above criteria, +12. and for completeness, if two operations are comparable given all the above criteria, consider as more relevant the one which has the shorter name, and if they have the same length, consider as more relevant the one whose name comes first in lexicographic order (obviously completely arbitrary, but a sorting @@ -403,7 +403,7 @@ following results for the AGD84 to GDA2020 coordinate operations lookup: +step +proj=axisswap +order=2,1 One can see that the selected intermediate CRS that has been used is GDA94. -This is a completely novel behaviour of PROJ 6 as opposed to the logic of PROJ.4 +This is a completely novel behavior of PROJ 6 as opposed to the logic of PROJ.4 where datum transformations implied using EPSG:4326 / WGS 84 has the mandatory datum hub. PROJ 6 no longer hardcodes it as the mandatory datum hub, and relies on the database to find the appropriate hub(s). @@ -468,7 +468,7 @@ techniques, we would only find one non-ballpark operation taking the route: This is not bad, but the global validity area of use is "Australia - onshore and EEZ", whereas GDA94 has a larger area of use. -There is another road that can be taken by going throug GDA2020 instead of ITRF2008. +There is another road that can be taken by going through GDA2020 instead of ITRF2008. The GDA94 to GDA2020 transformations operate on the respective geographic CRS, whereas GDA2020 to WGS 84 (G1762) operate on the geocentric CRS. Consequently, GDA2020 cannot be identifier as a hub by a "simple" self-join SQL request on @@ -508,7 +508,7 @@ particular case. Such transformations are done in 2 steps: This is implemented by the ``createOperationsDerivedTo`` method -For the symetric case, source CRS to a derived CRS, the above algorithm is applied +For the symmetric case, source CRS to a derived CRS, the above algorithm is applied by switching the source and target CRS, and then inverting the resulting operation(s). This is mostly a matter of avoiding to write very similar code twice. This logic is also applied to all below cases when considering the transformation between 2 different @@ -659,7 +659,7 @@ CompoundCRS to CompoundCRS There is some similarity with the previous paragraph. We first research the vertical transformations between the two vertical CRS. -1. If there is such a tranformation, be it direct, or if both vertical CRS +1. If there is such a transformation, be it direct, or if both vertical CRS relate to a common intermediate CRS. If it has a registered interpolation geographic CRS, then it is used. Otherwise we fallback to the geographic CRS of the source CRS. diff --git a/docs/source/operations/transformations/helmert.rst b/docs/source/operations/transformations/helmert.rst index 51784bdb..34acc332 100644 --- a/docs/source/operations/transformations/helmert.rst +++ b/docs/source/operations/transformations/helmert.rst @@ -33,7 +33,7 @@ kinematic transformations from global reference frames to local static frames. All of the parameters described in the table above are marked as optional. This is true as long as at least one parameter is defined in the setup of the transformation. -The behaviour of the transformation depends on which parameters are used in the setup. +The behavior of the transformation depends on which parameters are used in the setup. For instance, if a rate of change parameter is specified a kinematic version of the transformation is used. diff --git a/docs/source/operations/transformations/molodensky.rst b/docs/source/operations/transformations/molodensky.rst index 347165c8..df0b00a2 100644 --- a/docs/source/operations/transformations/molodensky.rst +++ b/docs/source/operations/transformations/molodensky.rst @@ -10,7 +10,7 @@ The Molodensky transformation resembles a :ref:`Helmert` with zero rotations and a scale of unity, but converts directly from geodetic coordinates to geodetic coordinates, without the intermediate shifts to and from cartesian geocentric coordinates, associated with the Helmert transformation. -The Molodensky transformation is simple to implement and to parameterize, requiring +The Molodensky transformation is simple to implement and to parametrize, requiring only the 3 shifts between the input and output frame, and the corresponding differences between the semimajor axes and flattening parameters of the reference ellipsoids. Due to its algorithmic simplicity, it was popular prior to the diff --git a/docs/source/resource_files.rst b/docs/source/resource_files.rst index cef22f84..ab8b149c 100644 --- a/docs/source/resource_files.rst +++ b/docs/source/resource_files.rst @@ -23,7 +23,7 @@ PROJ will attempt to locate its resource files - database, transformation grids or init-files - from several directories. The following paths are checked in order: -- For resource files that have an explict relative or absolute path, +- For resource files that have an explicit relative or absolute path, the directory specified in the filename. - Path resolved by the callback function set with diff --git a/docs/source/specifications/geodetictiffgrids.rst b/docs/source/specifications/geodetictiffgrids.rst index 479d6ca9..861e8b82 100644 --- a/docs/source/specifications/geodetictiffgrids.rst +++ b/docs/source/specifications/geodetictiffgrids.rst @@ -90,7 +90,7 @@ is an easy way to inspect such grid files: half-pixel shift regarding to the coordinates stored in the original grid file. On the reading side, PROJ will accept both conventions (for equivalent georeferencing, the value of the origin in a PixelIsArea convention is shifted by a half-pixel - towards the upper-left direction). Unspecified behaviour if this GeoKey is absent. + towards the upper-left direction). Unspecified behavior if this GeoKey is absent. - Files hosted on the CDN will be tiled, presumably with 256x256 tiles (small grids that are smaller than 256x256 will use a single strip). On the reading @@ -601,9 +601,9 @@ will be followed by: .. note:: TIFF has another mechanism to link IFDs, the SubIFD tag. This potentially - enables to define a hiearchy of IFDs (similar to HDF5 groups). There is no + enables to define a hierarchy of IFDs (similar to HDF5 groups). There is no support for that in most TIFF-using software, notably GDAL, and no compelling - need to have a nested hiearchy, so "flat" organization with the standard IFD chaining + need to have a nested hierarchy, so "flat" organization with the standard IFD chaining mechanism is adopted. Examples of multi-grid dataset diff --git a/docs/source/specifications/projjson.rst b/docs/source/specifications/projjson.rst index 6bcce585..3484fce9 100644 --- a/docs/source/specifications/projjson.rst +++ b/docs/source/specifications/projjson.rst @@ -75,7 +75,7 @@ Examples GeographicCRS +++++++++++++ -The following invokation +The following invocation :: @@ -132,7 +132,7 @@ will output: ProjectedCRS ++++++++++++ -The following invokation +The following invocation :: diff --git a/docs/source/usage/differences.rst b/docs/source/usage/differences.rst index 2a262232..11bab0b5 100644 --- a/docs/source/usage/differences.rst +++ b/docs/source/usage/differences.rst @@ -4,10 +4,10 @@ Known differences between versions ================================================================================ -Once in a while, a new version of PROJ causes changes in the existing behaviour. +Once in a while, a new version of PROJ causes changes in the existing behavior. In this section we track deliberate changes to PROJ that break from previous -behaviour. Most times that will be caused by a bug fix. Unfortunately, some bugs -have existed for so long that their faulty behaviour is relied upon by software +behavior. Most times that will be caused by a bug fix. Unfortunately, some bugs +have existed for so long that their faulty behavior is relied upon by software that uses PROJ. Behavioural changes caused by new bugs are not tracked here, as they should be @@ -57,7 +57,7 @@ rotation of the circle larger than :math:`\lambda=-70^{\circ}` and hence should return the same output for both. Adding the ``+over`` flag to the projection definition provides -the old behaviour. +the old behavior. Version 6.0.0 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ diff --git a/docs/source/usage/environmentvars.rst b/docs/source/usage/environmentvars.rst index 31a74e9a..e519a80b 100644 --- a/docs/source/usage/environmentvars.rst +++ b/docs/source/usage/environmentvars.rst @@ -48,7 +48,7 @@ done by setting the variable with no content:: Starting with PROJ version 6.1.0, the paths set by :func:`proj_context_set_search_paths` will have priority over the - :envvar:`PROJ_LIB` to allow for mutliple versions of PROJ + :envvar:`PROJ_LIB` to allow for multiple versions of PROJ resource files on your system without conflicting. .. envvar:: PROJ_DEBUG diff --git a/docs/source/usage/network.rst b/docs/source/usage/network.rst index 1b42d0aa..98461c69 100644 --- a/docs/source/usage/network.rst +++ b/docs/source/usage/network.rst @@ -43,7 +43,7 @@ Authorizing network access can be done in multiple ways: Instead of using the `libcurl` implementation, an application using the PROJ API can supply its own network implementation through C function callbacks with :cpp:func:`proj_context_set_network_callbacks`. Enabling network use - must still be done with one of the above mentionned method. + must still be done with one of the above mentioned method. Setting endpoint ---------------- diff --git a/docs/source/usage/projections.rst b/docs/source/usage/projections.rst index 8f1ccd50..464451c9 100644 --- a/docs/source/usage/projections.rst +++ b/docs/source/usage/projections.rst @@ -46,7 +46,7 @@ name for a unit (ie. ``us-ft``). Alternatively the translation to meters can be specified with the ``+to_meter`` keyword (ie. 0.304800609601219 for US feet). The ``-lu`` argument to ``cs2cs`` or ``proj`` can be used to list symbolic unit names. The default unit for projected coordinates is the meter. -A few special projections deviate from this behaviour, most notably the +A few special projections deviate from this behavior, most notably the latlong pseudo-projection that returns degrees. Vertical (Z) units can be specified using the ``+vunits`` keyword with a diff --git a/docs/source/usage/transformation.rst b/docs/source/usage/transformation.rst index a11992cf..1db63a21 100644 --- a/docs/source/usage/transformation.rst +++ b/docs/source/usage/transformation.rst @@ -150,7 +150,7 @@ PROJ 4.x/5.x paradigm ============ ============================================================== .. warning:: - This section documents the behaviour of PROJ 4.x and 5.x. In PROJ 6.x, + This section documents the behavior of PROJ 4.x and 5.x. In PROJ 6.x, :program:`cs2cs` has been reworked to use :c:func:`proj_create_crs_to_crs` internally, with *late binding* capabilities, and thus is no longer constrained to using WGS84 as a pivot (also called as *early binding* method). diff --git a/include/proj/internal/lru_cache.hpp b/include/proj/internal/lru_cache.hpp index 2f2c8bd9..b7aff6b9 100644 --- a/include/proj/internal/lru_cache.hpp +++ b/include/proj/internal/lru_cache.hpp @@ -206,7 +206,7 @@ class Cache { } private: - // Dissallow copying. + // Disallow copying. Cache(const Cache&) = delete; Cache& operator=(const Cache&) = delete; diff --git a/include/proj/util.hpp b/include/proj/util.hpp index 5c6eb329..84c93366 100644 --- a/include/proj/util.hpp +++ b/include/proj/util.hpp @@ -306,7 +306,7 @@ struct BaseObjectNNPtr : public util::nn<BaseObjectPtr> { using BaseObjectNNPtr = util::nn<BaseObjectPtr>; #endif -/** \brief Class that can be derived from, to emulate Java's Object behaviour. +/** \brief Class that can be derived from, to emulate Java's Object behavior. */ class PROJ_GCC_DLL BaseObject { public: diff --git a/scripts/fix_typos.sh b/scripts/fix_typos.sh index d094f0f3..152ba550 100755 --- a/scripts/fix_typos.sh +++ b/scripts/fix_typos.sh @@ -32,22 +32,22 @@ if ! test -d fix_typos; then # Get our fork of codespell that adds --words-white-list and full filename support for -S option mkdir fix_typos - cd fix_typos - git clone https://github.com/rouault/codespell - cd codespell - git checkout gdal_improvements - cd .. - # Aggregate base dictionary + QGIS one + Debian Lintian one - curl https://raw.githubusercontent.com/qgis/QGIS/master/scripts/spelling.dat | sed "s/:/->/" | grep -v "colour->" | grep -v "colours->" > qgis.txt - curl https://anonscm.debian.org/cgit/lintian/lintian.git/plain/data/spelling/corrections| grep "||" | grep -v "#" | sed "s/||/->/" > debian.txt - cat codespell/data/dictionary.txt qgis.txt debian.txt | awk 'NF' > gdal_dict.txt - echo "difered->deferred" >> gdal_dict.txt - echo "differed->deferred" >> gdal_dict.txt - cd .. + (cd fix_typos + git clone https://github.com/rouault/codespell + (cd codespell && git checkout gdal_improvements) + # Aggregate base dictionary + QGIS one + Debian Lintian one + curl https://raw.githubusercontent.com/qgis/QGIS/master/scripts/spell_check/spelling.dat | sed "s/:/->/" | grep -v "colour->" | grep -v "colours->" > qgis.txt + curl https://salsa.debian.org/lintian/lintian/-/raw/master/data/spelling/corrections | grep "||" | grep -v "#" | sed "s/||/->/" > debian.txt + cat codespell/data/dictionary.txt qgis.txt debian.txt | awk 'NF' > gdal_dict.txt + echo "difered->deferred" >> gdal_dict.txt + echo "differed->deferred" >> gdal_dict.txt + grep -v 404 < gdal_dict.txt > gdal_dict.txt.tmp + mv gdal_dict.txt.tmp gdal_dict.txt + ) fi EXCLUDED_FILES="*configure,config.status,config.sub,*/autom4te.cache/*,libtool,aclocal.m4,depcomp,ltmain.sh,*.pdf,./m4/*,./fix_typos/*,./docs/build/*,./src/*generated*,./test/googletest/*,./include/proj/internal/nlohmann/json.hpp,*.before_reformat" -WORDS_WHITE_LIST="metres,als,lsat,twon,ang,PJD_ERR_LSAT_NOT_IN_RANGE,COLOR_GRAT,interm" +WORDS_WHITE_LIST="metres,als,lsat,twon,ang,PJD_ERR_LSAT_NOT_IN_RANGE,COLOR_GRAT,interm,Interm,Cartesian,cartesian,CARTESIAN,kilometre,centimetre,millimetre,millimetres,Australia" python3 fix_typos/codespell/codespell.py -w -i 3 -q 2 -S $EXCLUDED_FILES \ -x scripts/typos_whitelist.txt --words-white-list=$WORDS_WHITE_LIST \ diff --git a/scripts/typos_whitelist.txt b/scripts/typos_whitelist.txt index 1dcd03dd..462d22da 100644 --- a/scripts/typos_whitelist.txt +++ b/scripts/typos_whitelist.txt @@ -1,2 +1,3 @@ $EXE +units=us-ft +init=${INIT_FILE}:404 -E -f '%.3f' >>${OUT} <<EOF (`#404 <https://github.com/OSGeo/proj.4/issues/404>`_) +{"CPM", "a=6375738.7", "rf=334.29", "Comm. des Poids et Mesures 1799"}, diff --git a/src/4D_api.cpp b/src/4D_api.cpp index 069093f2..2b00011d 100644 --- a/src/4D_api.cpp +++ b/src/4D_api.cpp @@ -605,7 +605,7 @@ static int cs2cs_emulation_setup (PJ *P) { /************************************************************************************** If any cs2cs style modifiers are given (axis=..., towgs84=..., ) create the 4D API equivalent operations, so the preparation and finalization steps in the pj_inv/pj_fwd -invocators can emulate the behaviour of pj_transform and the cs2cs app. +invocators can emulate the behavior of pj_transform and the cs2cs app. Returns 1 on success, 0 on failure **************************************************************************************/ diff --git a/src/apps/cs2cs.cpp b/src/apps/cs2cs.cpp index c99e16e0..58c164c9 100644 --- a/src/apps/cs2cs.cpp +++ b/src/apps/cs2cs.cpp @@ -117,10 +117,10 @@ static void process(FILE *fid) /* To avoid breaking existing tests, we read what is a possible t */ /* component of the input and rewind the s-pointer so that the final */ - /* output has consistent behaviour, with or without t values. */ + /* output has consistent behavior, with or without t values. */ /* This is a bit of a hack, in most cases 4D coordinates will be */ /* written to STDOUT (except when using -E) but the output format */ - /* speficied with -f is not respected for the t component, rather it */ + /* specified with -f is not respected for the t component, rather it */ /* is forward verbatim from the input. */ char *before_time = s; double t = strtod(s, &s); diff --git a/src/ell_set.cpp b/src/ell_set.cpp index 434ae76d..ddd507ac 100644 --- a/src/ell_set.cpp +++ b/src/ell_set.cpp @@ -70,7 +70,7 @@ int pj_ellipsoid (PJ *P) { are are taken into account as modifiers for the built in ellipsoid definition. While this may seem strange, it is in accordance with historical PROJ - behaviour. It can e.g. be used to define coordinates on the ellipsoid + behavior. It can e.g. be used to define coordinates on the ellipsoid scaled to unit semimajor axis by specifying "+ellps=xxx +a=1" ****************************************************************************************/ diff --git a/src/geodesic.h b/src/geodesic.h index e2265c89..b21e6c8c 100644 --- a/src/geodesic.h +++ b/src/geodesic.h @@ -476,7 +476,7 @@ extern "C" { /** * Initialize a geod_geodesicline object in terms of the direct geodesic - * problem spacified in terms of either distance or arc length. + * problem specified in terms of either distance or arc length. * * @param[out] l a pointer to the object to be initialized. * @param[in] g a pointer to the geod_geodesic object specifying the diff --git a/src/grids.cpp b/src/grids.cpp index 9dc1723e..067d3d45 100644 --- a/src/grids.cpp +++ b/src/grids.cpp @@ -1118,7 +1118,7 @@ insertIntoHierarchy(PJ_CONTEXT *ctx, std::unique_ptr<GridType> &&grid, const auto &extent = grid->extentAndRes(); // If we have one or both of grid_name and parent_grid_name, try to use - // the names to recreate the hiearchy + // the names to recreate the hierarchy if (!gridName.empty()) { if (mapGrids.find(gridName) != mapGrids.end()) { pj_log(ctx, PJ_LOG_DEBUG_MAJOR, "Several grids called %s found!", diff --git a/src/internal.cpp b/src/internal.cpp index b4b7a683..91994077 100644 --- a/src/internal.cpp +++ b/src/internal.cpp @@ -475,7 +475,7 @@ void proj_context_log_debug (PJ_CONTEXT *ctx, const char *fmt, ...) { /*****************************************************************************/ void proj_log_trace (PJ *P, const char *fmt, ...) { /****************************************************************************** - For reporting embarrasingly detailed debugging information. + For reporting embarrassingly detailed debugging information. ******************************************************************************/ va_list args; va_start( args, fmt ); diff --git a/src/iso19111/c_api.cpp b/src/iso19111/c_api.cpp index 6b726f34..200ac454 100644 --- a/src/iso19111/c_api.cpp +++ b/src/iso19111/c_api.cpp @@ -1,7 +1,7 @@ /****************************************************************************** * * Project: PROJ - * Purpose: C API wraper of C++ API + * Purpose: C API wrapper of C++ API * Author: Even Rouault <even dot rouault at spatialys dot com> * ****************************************************************************** @@ -1354,7 +1354,7 @@ const char *proj_get_id_code(const PJ *obj, int index) { * supported options are: * <ul> * <li>MULTILINE=YES/NO. Defaults to YES, except for WKT1_ESRI</li> - * <li>INDENTATION_WIDTH=number. Defauls to 4 (when multiline output is + * <li>INDENTATION_WIDTH=number. Defaults to 4 (when multiline output is * on).</li> * <li>OUTPUT_AXIS=AUTO/YES/NO. In AUTO mode, axis will be output for WKT2 * variants, for WKT1_GDAL for ProjectedCRS with easting/northing ordering @@ -1524,7 +1524,7 @@ const char *proj_as_proj_string(PJ_CONTEXT *ctx, const PJ *obj, * supported options are: * <ul> * <li>MULTILINE=YES/NO. Defaults to YES</li> - * <li>INDENTATION_WIDTH=number. Defauls to 2 (when multiline output is + * <li>INDENTATION_WIDTH=number. Defaults to 2 (when multiline output is * on).</li> * <li>SCHEMA=string. URL to PROJJSON schema. Can be set to empty string to * disable it.</li> @@ -3198,7 +3198,7 @@ PJ *proj_create_vertical_crs(PJ_CONTEXT *ctx, const char *crs_name, * use. * It should be used by at most one thread at a time. * - * This is an extented (_ex) version of proj_create_vertical_crs() that adds + * This is an extended (_ex) version of proj_create_vertical_crs() that adds * the capability of defining a geoid model. * * @param ctx PROJ context, or NULL for default context @@ -7434,7 +7434,7 @@ void proj_operation_factory_context_set_use_proj_alternative_grid_names( * step. * * By default, with the IF_NO_DIRECT_TRANSFORMATION stratgey, all potential - * C candidates will be used if there is no direct tranformation. + * C candidates will be used if there is no direct transformation. * * @param ctx PROJ context, or NULL for default context * @param factory_ctx Operation factory context. must not be NULL diff --git a/src/iso19111/common.cpp b/src/iso19111/common.cpp index b5e393b3..0eb40f12 100644 --- a/src/iso19111/common.cpp +++ b/src/iso19111/common.cpp @@ -422,7 +422,7 @@ bool Measure::operator==(const Measure &other) PROJ_PURE_DEFN { /** \brief Returns whether an object is equivalent to another one. * @param other other object to compare to - * @param criterion comparaison criterion. + * @param criterion comparison criterion. * @param maxRelativeError Maximum relative error allowed. * @return true if objects are equivalent. */ diff --git a/src/iso19111/coordinateoperation.cpp b/src/iso19111/coordinateoperation.cpp index ec515cd7..0f5e4c4d 100644 --- a/src/iso19111/coordinateoperation.cpp +++ b/src/iso19111/coordinateoperation.cpp @@ -4684,7 +4684,7 @@ ConversionNNPtr Conversion::createEqualEarth( * 0.</li> * </ul> * - * For completness, PROJ adds the falseEasting and falseNorthing parameter, + * For completeness, PROJ adds the falseEasting and falseNorthing parameter, * which are not described in EPSG. They should usually be set to 0. * * @param properties See \ref general_properties of the conversion. If the name @@ -4717,7 +4717,7 @@ ConversionNNPtr Conversion::createVerticalPerspective( /** \brief Instantiate a conversion based on the Pole Rotation method, using * the conventions of the GRIB 1 and GRIB 2 data formats. * - * Those are mentionned in the Note 2 of + * Those are mentioned in the Note 2 of * https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_temp3-1.shtml * * Several conventions for the pole rotation method exists. @@ -10739,7 +10739,7 @@ CoordinateOperationContext::getGridAvailabilityUse() const { * step. * * By default, with the IF_NO_DIRECT_TRANSFORMATION stratgey, all potential - * C candidates will be used if there is no direct tranformation. + * C candidates will be used if there is no direct transformation. */ void CoordinateOperationContext::setAllowUseIntermediateCRS( IntermediateCRSUse use) { @@ -12110,7 +12110,7 @@ CoordinateOperationFactory::Private::findsOpsInRegistryWithIntermediate( // If doing GeogCRS --> GeogCRS, only use GeogCRS as // intermediate CRS - // Avoid weird behaviour when doing NAD83 -> NAD83(2011) + // Avoid weird behavior when doing NAD83 -> NAD83(2011) // that would go through NAVD88 otherwise. if (context.context->getIntermediateCRS().empty() && dynamic_cast<const crs::GeographicCRS *>(sourceCRS.get()) && diff --git a/src/iso19111/io.cpp b/src/iso19111/io.cpp index a255b959..97f741be 100644 --- a/src/iso19111/io.cpp +++ b/src/iso19111/io.cpp @@ -179,7 +179,7 @@ struct WKTFormatter::Private { * * A formatter can be used only once (its internal state is mutated) * - * Its default behaviour can be adjusted with the different setters. + * Its default behavior can be adjusted with the different setters. * * @param convention WKT flavor. Defaults to Convention::WKT2 * @param dbContext Database context, to allow queries in it if needed. @@ -201,7 +201,7 @@ WKTFormatterNNPtr WKTFormatter::create(Convention convention, * * A formatter can be used only once (its internal state is mutated) * - * Its default behaviour can be adjusted with the different setters. + * Its default behavior can be adjusted with the different setters. * * @param other source formatter. * @return new formatter. @@ -6631,7 +6631,7 @@ PROJStringFormatter::~PROJStringFormatter() = default; * * A formatter can be used only once (its internal state is mutated) * - * Its default behaviour can be adjusted with the different setters. + * Its default behavior can be adjusted with the different setters. * * @param conventionIn PROJ string flavor. Defaults to Convention::PROJ_5 * @param dbContext Database context (can help to find alternative grid names). diff --git a/src/iso19111/metadata.cpp b/src/iso19111/metadata.cpp index 8f2601e0..fc788a30 100644 --- a/src/iso19111/metadata.cpp +++ b/src/iso19111/metadata.cpp @@ -777,7 +777,7 @@ bool Extent::_isEquivalentTo(const util::IComparable *other, /** \brief Returns whether this extent contains the other one. * - * Behaviour only well specified if each sub-extent category as at most + * Behavior only well specified if each sub-extent category as at most * one element. */ bool Extent::contains(const ExtentNNPtr &other) const { @@ -802,7 +802,7 @@ bool Extent::contains(const ExtentNNPtr &other) const { /** \brief Returns whether this extent intersects the other one. * - * Behaviour only well specified if each sub-extent category as at most + * Behavior only well specified if each sub-extent category as at most * one element. */ bool Extent::intersects(const ExtentNNPtr &other) const { @@ -829,7 +829,7 @@ bool Extent::intersects(const ExtentNNPtr &other) const { /** \brief Returns the intersection of this extent with another one. * - * Behaviour only well specified if there is one single GeographicExtent + * Behavior only well specified if there is one single GeographicExtent * in each object. * Returns nullptr otherwise. */ diff --git a/src/iso19111/util.cpp b/src/iso19111/util.cpp index 2a6178e2..21d45e44 100644 --- a/src/iso19111/util.cpp +++ b/src/iso19111/util.cpp @@ -686,7 +686,7 @@ IComparable::~IComparable() = default; /** \brief Returns whether an object is equivalent to another one. * @param other other object to compare to - * @param criterion comparaison criterion. + * @param criterion comparison criterion. * @param dbContext Database context, or nullptr. * @return true if objects are equivalent. */ diff --git a/src/malloc.cpp b/src/malloc.cpp index 10ab2fad..c8de6630 100644 --- a/src/malloc.cpp +++ b/src/malloc.cpp @@ -216,7 +216,7 @@ PJ *pj_default_destructor (PJ *P, int errlev) { /* Destructor */ /* Even if P==0, we set the errlev on pj_error and the default context */ /* Note that both, in the multithreaded case, may then contain undefined */ - /* values. This is expected behaviour. For MT have one ctx per thread */ + /* values. This is expected behavior. For MT have one ctx per thread */ if (0!=errlev) pj_ctx_set_errno (pj_get_ctx(P), errlev); diff --git a/src/networkfilemanager.cpp b/src/networkfilemanager.cpp index 30229fea..4d6f425c 100644 --- a/src/networkfilemanager.cpp +++ b/src/networkfilemanager.cpp @@ -2180,7 +2180,7 @@ void proj_grid_cache_clear(PJ_CONTEXT *ctx) { * use the "downloaded_file_properties" table of its grid cache database. * Consequently files manually placed in the user-writable * directory without using this function would be considered as - * non-existing/obsolete and would be unconditionnaly downloaded again. + * non-existing/obsolete and would be unconditionally downloaded again. * * This function can only be used if networking is enabled, and either * the default curl network API or a custom one have been installed. @@ -2309,7 +2309,7 @@ int proj_is_download_needed(PJ_CONTEXT *ctx, const char *url_or_filename, * use the "downloaded_file_properties" table of its grid cache database. * Consequently files manually placed in the user-writable * directory without using this function would be considered as - * non-existing/obsolete and would be unconditionnaly downloaded again. + * non-existing/obsolete and would be unconditionally downloaded again. * * This function can only be used if networking is enabled, and either * the default curl network API or a custom one have been installed. diff --git a/src/projections/isea.cpp b/src/projections/isea.cpp index 1ebbeebb..dd1d48ff 100644 --- a/src/projections/isea.cpp +++ b/src/projections/isea.cpp @@ -322,7 +322,7 @@ static int isea_snyder_forward(struct isea_geo * ll, struct isea_pt * out) /* * spherical distance from center of polygon face to any of its - * vertexes on the globe + * vertices on the globe */ double g; diff --git a/src/projections/ocea.cpp b/src/projections/ocea.cpp index 4fc5391d..de9838cb 100644 --- a/src/projections/ocea.cpp +++ b/src/projections/ocea.cpp @@ -65,12 +65,12 @@ PJ *PROJECTION(ocea) { /*Define Pole of oblique transformation from 1 point & 1 azimuth*/ // ERO: I've added M_PI so that the alpha is the angle from point 1 to point 2 // from the North in a clockwise direction - // (to be consistent with omerc behaviour) + // (to be consistent with omerc behavior) alpha = M_PI + pj_param(P->ctx, P->params, "ralpha").f; lonz = pj_param(P->ctx, P->params, "rlonc").f; /*Equation 9-8 page 80 (http://pubs.usgs.gov/pp/1395/report.pdf)*/ // Actually slightliy modified to use atan2(), as it is suggested by - // Snyder for equation 9-1, but this is not mentionned here + // Snyder for equation 9-1, but this is not mentioned here lam_p = atan2(-cos(alpha) , -sin(P->phi0) * sin(alpha)) + lonz; /*Equation 9-7 page 80 (http://pubs.usgs.gov/pp/1395/report.pdf)*/ phi_p = asin(cos(P->phi0) * sin(alpha)); diff --git a/src/projections/tmerc.cpp b/src/projections/tmerc.cpp index 1e5fc1a8..3a58fc02 100644 --- a/src/projections/tmerc.cpp +++ b/src/projections/tmerc.cpp @@ -286,7 +286,7 @@ static PJ *setup_approx(PJ *P) { // /*****************************************************************************/ -/* Helper functios for "exact" transverse mercator */ +/* Helper functions for "exact" transverse mercator */ inline static double gatg(const double *p1, int len_p1, double B, double cos_2B, double sin_2B) { double h = 0, h1, h2 = 0; @@ -750,7 +750,7 @@ PJ *PROJECTION(etmerc) { /* UTM uses the Poder/Engsager implementation for the underlying projection */ -/* UNLESS +approx is set in which case the Evenden/Snyder implemenation is used. */ +/* UNLESS +approx is set in which case the Evenden/Snyder implementation is used. */ PJ *PROJECTION(utm) { long zone; if (P->es == 0.0) { diff --git a/src/strtod.cpp b/src/strtod.cpp index d45e62db..4311caea 100644 --- a/src/strtod.cpp +++ b/src/strtod.cpp @@ -46,7 +46,7 @@ * Converts ASCII string to floating point number. * * This function converts the initial portion of the string pointed to - * by nptr to double floating point representation. The behaviour is the + * by nptr to double floating point representation. The behavior is the * same as * * pj_strtod(nptr, (char **)NULL); diff --git a/src/transformations/vgridshift.cpp b/src/transformations/vgridshift.cpp index 6ee8a6b0..3d9f046a 100644 --- a/src/transformations/vgridshift.cpp +++ b/src/transformations/vgridshift.cpp @@ -46,7 +46,7 @@ struct vgridshiftData { static void deal_with_vertcon_gtx_hack(PJ *P) { struct vgridshiftData *Q = (struct vgridshiftData *) P->opaque; - // The .gtx VERTCON files stored millimetres, but the .tif files + // The .gtx VERTCON files stored millimeters, but the .tif files // are in metres. if( Q->forward_multiplier != 0.001 ) { return; diff --git a/test/cli/testvarious b/test/cli/testvarious index 6d773c4c..6a77729e 100755 --- a/test/cli/testvarious +++ b/test/cli/testvarious @@ -959,7 +959,7 @@ echo "Test EPSG:4896 to EPSG:7930" >> ${OUT} # compatibility, the t-component is not written to STDOUT as part of the # coordinate data, but rather as part of the string that follows the xyz # components. This is only seen by users when the -E option is used. Which -# means that this test also experience that behaviour. +# means that this test also experience that behavior. $EXE -f %.4f EPSG:4896 EPSG:7930 -E >> ${OUT} <<EOF 3496737.2679 743254.4507 5264462.9620 2019.0 3496737.2679 743254.4507 5264462.9620 2029.0 diff --git a/test/fuzzers/README.TXT b/test/fuzzers/README.TXT index a43e089f..3482e5cd 100644 --- a/test/fuzzers/README.TXT +++ b/test/fuzzers/README.TXT @@ -1,4 +1,4 @@ -This directory contain fuzzer main funtions and scripts for the +This directory contain fuzzer main functions and scripts for the Google OSS Fuzz project: https://github.com/google/oss-fuzz/ The main build scripts are in: diff --git a/test/gie/more_builtins.gie b/test/gie/more_builtins.gie index 3847c87e..610c6c3f 100644 --- a/test/gie/more_builtins.gie +++ b/test/gie/more_builtins.gie @@ -429,7 +429,7 @@ expect failure errno invalid_arg operation proj=helmert rx=1 convention=1 expect failure errno invalid_arg -# towgs84 in helmert context should alwas be position_vector +# towgs84 in helmert context should always be position_vector operation proj=helmert towgs84=1,2,3,4,5,6,7 convention=coordinate_frame expect failure errno invalid_arg diff --git a/test/unit/test_c_api.cpp b/test/unit/test_c_api.cpp index e56fb39c..e0473d4f 100644 --- a/test/unit/test_c_api.cpp +++ b/test/unit/test_c_api.cpp @@ -1497,7 +1497,7 @@ TEST_F(CApi, proj_create_operations_with_pivot) { // There is no direct transformations between both - // Default behaviour: allow any pivot + // Default behavior: allow any pivot { auto ctxt = proj_create_operation_factory_context(m_ctxt, nullptr); ASSERT_NE(ctxt, nullptr); @@ -1621,7 +1621,7 @@ TEST_F(CApi, proj_create_operations_allow_ballpark_transformations) { proj_operation_factory_context_set_grid_availability_use( m_ctxt, ctxt, PROJ_GRID_AVAILABILITY_IGNORED); - // Default: allowed implictly + // Default: allowed implicitly { auto res = proj_create_operations(m_ctxt, source_crs, target_crs, ctxt); ASSERT_NE(res, nullptr); @@ -4350,7 +4350,7 @@ TEST_F( // In this particular case, PROJ computes a transformation from NAD83(2011) // (EPSG:6318) to WGS84 (EPSG:4979) for the initial horizontal adjustment // before the geoidgrids application. There are 6 candidate transformations - // for that in subzones of the US and one last no-op tranformation flagged + // for that in subzones of the US and one last no-op transformation flagged // as ballpark. That one used to be eliminated because by // proj_create_crs_to_crs() because there were non Ballpark transformations // available. This resulted thus in an error when transforming outside of diff --git a/test/unit/test_operation.cpp b/test/unit/test_operation.cpp index a655aff0..9b339525 100644 --- a/test/unit/test_operation.cpp +++ b/test/unit/test_operation.cpp @@ -2904,7 +2904,7 @@ TEST(operation, wkt1_import_mercator_variant_A) { // --------------------------------------------------------------------------- TEST(operation, wkt1_import_mercator_variant_A_that_is_variant_B) { - // Adresses https://trac.osgeo.org/gdal/ticket/3026 + // Addresses https://trac.osgeo.org/gdal/ticket/3026 auto wkt = "PROJCS[\"test\",\n" " GEOGCS[\"WGS 84\",\n" " DATUM[\"WGS 1984\",\n" @@ -4648,7 +4648,7 @@ TEST(operation, geogCRS_to_geogCRS_context_NAD27_to_WGS84_G1762) { // --------------------------------------------------------------------------- TEST(operation, geogCRS_to_geogCRS_context_WGS84_G1674_to_WGS84_G1762) { - // Check that particular behaviour with WGS 84 (Gxxx) related to + // Check that particular behavior with WGS 84 (Gxxx) related to // 'geodetic_datum_preferred_hub' table and custom no-op transformations // between WGS 84 and WGS 84 (Gxxx) doesn't affect direct transformations // to those realizations. |