aboutsummaryrefslogtreecommitdiff
path: root/test
AgeCommit message (Collapse)Author
2018-12-07Merge remote-tracking branch 'rouault/gdalbarn'Even Rouault
2018-12-07Experimental C API: add proj_obj_query_geodetic_crs_from_datum() (for GDAL ↵Even Rouault
Idrisi driver)
2018-12-06Speed-up createBoundCRSToWGS84IfPossible()Even Rouault
2018-12-06projinfo: display deprecation infoEven Rouault
2018-12-06Add API to retrieve non-deprecated equivalent of an objectEven Rouault
2018-12-06Fix special handling of Azimuth parameter of KrovakEven Rouault
2018-12-06Fine tune axis denomination when exporting to WKT1_GDALEven Rouault
2018-12-06Coordinate operation search: add a authority_to_authority_preference table ↵Even Rouault
to restrict and prioritize searches
2018-12-06Merge remote-tracking branch 'rouault/gdalbarn'Even Rouault
2018-12-06Take into account supersession information to filter out irrelevant ↵Even Rouault
transformations
2018-12-06Merge remote-tracking branch 'rouault/gdalbarn'Even Rouault
2018-12-05experimental C API: add proj_obj_convert_conversion_to_other_method()Even Rouault
2018-12-05Allow ellipsoid flattening to be set to zeroKristian Evers
Issue raised in https://github.com/OSGeo/proj.4/issues/1191.
2018-12-04Add proj_obj_create_vertical_crs() and proj_obj_create_compound_crs()Even Rouault
2018-12-04WKT1 export of LOCAL_CS: add UNIT if explicitly setEven Rouault
2018-12-04export to WKT1 of geocentric CRS: do not emit a TOWGS84 node if the datum is ↵Even Rouault
WGS84
2018-12-04Improve management of 'deprecated' suffix in object namesEven Rouault
2018-12-04Improve recognition of WKT1 datum namesEven Rouault
2018-12-03Merge pull request #1189 from rouault/projinfo_improvementsEven Rouault
Projinfo improvements: output operation summary and add --area option
2018-12-03projinfo: add a --area option (refs #1188)Even Rouault
2018-12-03Merge pull request #1182 from rouault/plug_new_codeEven Rouault
Remove data/epsg, IGNF and esri.* files / support legacy +init=epsg:XXXX syntax
2018-12-03projinfo: output operation summary, even in non summary mode (refs #1188)Even Rouault
2018-12-03Export to ESRI WKT: make it use verbatim WKT definition from the database ↵Even Rouault
when possible
2018-12-03WKTParser: fix to avoid creation of empty nodesEven Rouault
2018-12-02identify: improve GeographicCRS identification when the CRS name has no matchEven Rouault
2018-12-02improve identify() for projected and bound CRSEven Rouault
2018-12-01Add testing of projinfo utilityEven Rouault
2018-12-01Fix PROJ_GRID_AVAILABILITY_IGNOREDEven Rouault
2018-12-01Rename test/old/ to test/cli/ to better reflect their natureEven Rouault
2018-12-01importFromWKT: deal with uncommon formulation of EPSG:3857Even Rouault
2018-12-01importFromWKT: morph GDAL_WKT1 datum names into their EPSG spellingEven Rouault
2018-11-30API: move all advanced PJ_OBJ creation functions in a dedicated ↵Even Rouault
proj_experimental.h header
2018-11-30C API: do not 'cache' PROJ context in PJ_OBJ objectsEven Rouault
We store the PJ_CONTEXT* in the PJ_OBJ objects, but this might cause issues in multi-threaded uses. For example, before this change, let's imagie: - a PJ_OBJ is created in thread A with a PJ_CONTEXT that is specific to this thread A - PJ_OBJ is transfered to another thread that operates on it. It might thus use the PJ_CONTEXT that was TLS(A) - in the meantime thread A does completely different things, but still operate on its PJ_CONTEXT. We might get a concurrent use of the PJ_CONTEXT despite working on different PJ_OBJ Another situation is when using constructor functions that take two PJ_OBJ. Up to now, we arbitrarily selected the context of one of the arguments to attach it to the new object. So better be explicit on which context is used. For reference, in those wrappers of the C++ API, the context is mostly used for two things: - reporting C++ exceptions as PROJ errors with the error handler attached to the PJ_CONTEXT - using the database handle that is associated with the PJ_CONTEXT.
2018-11-29importFromWKT v1: properly handle latitude_of_origin=0 for Mercator_1SPEven Rouault
2018-11-29proj_create_crs_to_crs(): rename arguments, update doc, and add a few test casesEven Rouault
2018-11-29C API extensions and renamingEven Rouault
- proj_obj_create_projected_XXXXX() are renamed to proj_obj_create_conversion_snake_case() and just instanciate a Conversion object - Advanced manipulation functions are moved to a dedicated section at bottom of proj.h - New C API needed for GDAL OGRSpatialReference
2018-11-29Preserve EPSG code when importFromWKT WKT1_GDAL of EPSG:3857Even Rouault
2018-11-29exportToWKT WKT1_GDAL: export axis by default for GeocentricCRSEven Rouault
2018-11-29importFromWKT: check we have a valid unit where we need oneEven Rouault
2018-11-29Redirect epsg:XXXX and IGNF:XXXX CRS expansions to the database, and remove ↵Even Rouault
the data/epsg and data/IGNF files
2018-11-29Add unit test for pj_tranform() now that cs2cs no longer use itEven Rouault
2018-11-29Reformat test .cpp filesEven Rouault
2018-11-29cs2cs: upgrade to use proj_create_crs_to_crs()Even Rouault
2018-11-26test/fuzzers/build_google_oss_fuzzers.sh: statically link against sqlite3Even Rouault
2018-11-26test/fuzzers/build_google_oss_fuzzers.sh: link against libsqlite3Even Rouault
2018-11-22Make proj_create_crs_to_crs() use proj_obj_create_operations() and use area ↵Even Rouault
of use argument, and make createFromUserInput() recognize init=epsg: / init=IGNF: in legacy mode, that is when proj_context_get_use_proj4_init_rules() is used
2018-11-22Fix transformation between geographic CRS that differ by axis order and unitsEven Rouault
2018-11-21Move 'builtins' test of src/gie.c to test/unit/gie_self_tests.cppEven Rouault
2018-11-21createFromUserInput("authname:code"): make it case insensitive regarding ↵Even Rouault
authname
2018-11-20Database: use official IGNF.xml registry to create content from the IGNF ↵Even Rouault
authority Up to now, we re-processed the data/IGNF PROJ.4 definition to ingest it into proj.db, but this file originally come from a processing of IGNF.xml ( http://librairies.ign.fr/geoportail/resources/IGNF.xml ) The end result is not strictly equivalent, as data/IGNF has some 'magic' to create towgs84 / nadgrids, since IGNF.xml doesn't necessary contain all transformations from its geodetic systems to WGS84. I've tried to re-add some of those missing transforms (null Helmert transforms), so it can be used for pivoting, but that might be incomplete.