| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-10-25 | Fix issues spotted by cppcheck | Even Rouault | |
| 2020-10-25 | Fix typos spotted by scripts/fix_typos.sh | Even Rouault | |
| 2020-10-23 | PROJStringFormatter::getUsedGridNames(): recognize +file= parameter of ↵ | Even Rouault | |
| operation +proj=tinshift | |||
| 2020-10-23 | Add logic to handle interpolationCRS in PROJBasedOperation and ↵ | Even Rouault | |
| ConcatenatedOperation | |||
| 2020-10-23 | AuthorityFactory::createCoordinateOperation(): correctly compute accuracy of ↵ | Even Rouault | |
| concatenated operation when there is a conversion step | |||
| 2020-10-23 | WKT1_ESRI export: try to export Geographic3D and Projected3D CRS when we can ↵ | Even Rouault | |
| find a corresponding ellipsoidal vertical datum | |||
| 2020-10-23 | Database: import ESRI VERTCS that uses a (geodetic) datum to express ↵ | Even Rouault | |
| ellipsoidal height | |||
| 2020-10-23 | WKT1_ESRI export: generate VERTCS[...,DATUM[...,SPHEROID[]] syntax when ↵ | Even Rouault | |
| ellipsoidal height is found | |||
| 2020-10-22 | WKT1_ESRI export: export CompoundCRS as PROJCS[...],VERTCS[...] or ↵ | Even Rouault | |
| GEOGCS[...],VERTCS[...] | |||
| 2020-10-22 | WKT parser: accept ESRI VERTCS[...,DATUM[...,SPHEROID[]] syntax to express ↵ | Even Rouault | |
| ellipsoidal heights | |||
| 2020-10-22 | WKT parser: accept implicit compoundCRS from ESRI WKT, like ↵ | Even Rouault | |
| "PROJCS[...],VERTCS[...]" | |||
| 2020-10-22 | WKTParser::createFromWKT(): minor adjustement for DATUM[],PRIMEM[] constructs | Even Rouault | |
| The WKT parser on the second part was called with "RIMEM[...]" (leading P skipped), which has no visible consequence, as we didn't care about the actual value of the keyword due to how we used it. But this is better fixing that. Only applies to recent master changes. | |||
| 2020-10-20 | VerticalCRS: morph CRS and datum name using ESRI aliases on import from / ↵ | Even Rouault | |
| export to WKT1:ESRI | |||
| 2020-10-20 | Improve identification of compound CRS from ESRI WKT1, and for compound CRS ↵ | Even Rouault | |
| whose result is not in the DB but whose horiz and vertical parts are known | |||
| 2020-10-20 | Orthographic projection: do not add f=0 to PROJ string if the ellipsoid is a ↵ | Even Rouault | |
| sphere (fixes GDAL PDS4 tests) | |||
| 2020-10-18 | Merge pull request #2381 from rouault/fix_1453 | Even Rouault | |
| Add multi-line PROJ string export capability, and use it by default in projinfo (unless --single-line is specified) (fixes #1543) | |||
| 2020-10-17 | CompoundCRS with ellipsoidal height: make sure the vertical axis has ↵ | Even Rouault | |
| 'ellipsoid height' as name and 'h' as abbreviation | |||
| 2020-10-16 | Add multi-line PROJ string export capability, and use it by default in ↵ | Even Rouault | |
| projinfo (unless --single-line is specified) (fixes #1543) | |||
| 2020-10-16 | Merge pull request #2370 from rouault/epsg10 | Even Rouault | |
| Update to EPSG 10.003 and make code base robust to dealing with WKT CRS with DatumEnsemble | |||
| 2020-10-11 | C API: add proj_dynamic_datum_get_frame_reference_epoch() | Even Rouault | |
| 2020-10-11 | Database query: add ↵ | Even Rouault | |
| AuthorityFactory::ObjectType::DYNAMIC_GEODETIC_REFERENCE_FRAME and DYNAMIC_VERTICAL_REFERENCE_FRAME, and make corresponding C API work | |||
| 2020-10-11 | Database: add a frame_reference_epoch column in vertical_datum to be able to ↵ | Even Rouault | |
| handle dynamic vertical datums, and instanciate them properly from database | |||
| 2020-10-10 | WKT2:2019 import/export: handle DATUM (at top level object) with PRIMEM | Even Rouault | |
| This is a peculiarity of the WKT grammar. Despite ISO 19111 saying that the prime meridian is a component of the datum, in WKT, they are placed at the same level, for backward compatibility with earlier WKT versions. So handle exporting and importing that. The fix is only for situation where DATUM is the top level object (was working fine otherwise), which is a uncommon use case. And to limit the amount of issue, on export emit the prime meridian only if it is not Greenwich. | |||
| 2020-10-08 | promoteTo3D(): add a remark with the original CRS identifier (fixes #2368) | Even Rouault | |
| ``` $ projinfo EPSG:32631 --3d WKT2:2019 string: PROJCRS["WGS 84 / UTM zone 31N", [ ...snip ] REMARK["Promoted to 3D from EPSG:32631"]] ``` | |||
| 2020-10-08 | Make GeographicCRS::is2DPartOf3D() work with DatumEnsemble | Even Rouault | |
| 2020-10-08 | Add C API to work with datum ensemble | Even Rouault | |
| Add: - proj_crs_get_datum_ensemble() - proj_crs_get_datum_forced() - proj_datum_ensemble_get_member_count() - proj_datum_ensemble_get_accuracy() - proj_datum_ensemble_get_member() Make proj_create_geographic_crs_from_datum() and proj_create_geocentric_crs_from_datum() accept a datum ensemble. | |||
| 2020-10-08 | createGeodeticCRS(): more DatumEnsemble compatibility in the case when ↵ | Even Rouault | |
| creating from text_definition | |||
| 2020-10-08 | Make createOperations() work with DatumEnsemble | Even Rouault | |
| 2020-10-08 | Make CRS identification work with CRS with DatumEnsemble | Even Rouault | |
| 2020-10-08 | Add DatumEnsemble::asDatum() and use it in exportToWkt() | Even Rouault | |
| to allow exporting DatumEnsemble to WKT < 2019. | |||
| 2020-10-08 | Add a AuthorityFactory::createDatumEnsemble() method, and make it inherit ↵ | Even Rouault | |
| from ObjectUsage as mandated by ISO 19111:2019 | |||
| 2020-10-08 | Database: add aliases for 'old' names of WGS84 and ETRS89 datums, and remove ↵ | Even Rouault | |
| one hack | |||
| 2020-10-08 | getCRSInfoList(): make it use area description | Even Rouault | |
| 2020-10-08 | Database: use extended description for extent/area of use, as done by ↵ | Even Rouault | |
| epsg.org WKT export | |||
| 2020-10-06 | Database: instanciate DynamicGeodeticReferenceFrame (things like ITRFxxx, ↵ | Even Rouault | |
| WGS 84 (Gxxxx), etc.) when possible | |||
| 2020-10-06 | Database: "minimal" update to EPSG v10.003 | Even Rouault | |
| Content mostly unchanged since v9.9 This update is "minimal" in that it mostly reflects the removal of the 'area' table, replaced now by 'extent', 'scope' and 'usage' Other new aspects of EPSG v10 are left aside. | |||
| 2020-10-05 | proj_crs_create_bound_crs_to_WGS84(): make it work on ↵ | Even Rouault | |
| verticalCRS/compoundCRS such as EPSG:4326+5773 and EPSG:4326+3855 | |||
| 2020-10-02 | createOperations(): avoid elimination of ballpark transformation that can ↵ | Even Rouault | |
| help for NAD83->WGS84->NAD83(2011) hops | |||
| 2020-10-02 | createOperations(): when combining transformations, reject those with a ↵ | Even Rouault | |
| non-intersecting area of validity | |||
| 2020-10-02 | CoordinateOperation: fix issue with ballpark flag not being copied with ↵ | Even Rouault | |
| shallowClone() which affected result sorting | |||
| 2020-09-26 | Implement ellipsoidal formulation of +proj=ortho (fixes #397) | Even Rouault | |
| - Map ESRI 'Local' to +proj=ortho when Scale_Factor = 1 and Azimuth = 0 - Map ESRI 'Orthographic' to a PROJ WKT2 'Orthographic (Spherical)' which maps to +proj=ortho +f=0 to froce spherical evaluation | |||
| 2020-09-17 | createOperations(): tune sorting of transformations so that the ones with ↵ | Even Rouault | |
| greater 'version numbers' are prefered over other ones, when all other comparison criteria are equal. Helps with Amersfoort RD New to EPSG:4326 | |||
| 2020-09-17 | Adjust createBoundCRSToWGS84IfPossible() and operation filtering (for POSGAR ↵ | Even Rouault | |
| 2007 to WGS84 issues) (fixes #2356) - We make createBoundCRSToWGS84IfPossible() more restrictive. If there are more than one Helmert transformation from the CRS to WGS 84 covering the area of use of the CRS, we do not create a BoundCRS / +towgs84 - In createOperations() filtering, we are less aggressive in discarding operations that have the same area of use but worse accuracy. We do it only if they involve more transformation steps. We now get: ``` $ projinfo EPSG:5340 -o PROJ PROJ.4 string: +proj=longlat +ellps=GRS80 +no_defs +type=crs $ projinfo -s EPSG:5340 -t EPSG:4326 --spatial-test intersects --summary Candidate operations found: 2 EPSG:9264, POSGAR 2007 to WGS 84 (2), 0.5 m, Argentina EPSG:5351, POSGAR 2007 to WGS 84 (1), 1.0 m, Argentina ``` | |||
| 2020-09-10 | Merge pull request #2351 from rouault/update_to_epsg_9_9 | Even Rouault | |
| Database: update to EPSG 9.9 | |||
| 2020-09-09 | Map EPSG:1083 'Geog3D to Geog2D+Vertical (AUSGeoid v2)' method to ↵ | Even Rouault | |
| +proj=vgridshift | |||
| 2020-09-04 | Fix compiling warnings when using GCC 4.8.x | Alexander Saprykin | |
| 2020-09-04 | DOC: Fix reference to proj_get_codes_from_database in ↵ | Alan D. Snow | |
| proj_get_crs_info_list_from_database docstring (#2345) | |||
| 2020-08-26 | proj_create_vertical_crs_ex(): add a ACCURACY option to provide an explicit ↵ | Even Rouault | |
| accuracy, or derive it from the grid name if it is known | |||
| 2020-08-21 | createObjectsFromName(): add back case insensitivity when comparing names | Even Rouault | |
| Fixes #2332 Didn't affect released versions | |||
| 2020-08-19 | Code reformatting | Even Rouault | |
