-
Notifications
You must be signed in to change notification settings - Fork 802
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Backport 9.5] Database: ingest deprecated ESRI names to be able to better import old WKT ESRI #4285
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Backport 9.5] affine.rst: Fixed second s21 that should say s22
…target CRS that have the same originating authority Fixes https://lists.osgeo.org/pipermail/proj/2024-September/011531.html i.e. ``` projinfo -s EPSG:4269 -t EPSG:6318 --3d --spatial-test intersects ``` The fix consists in making sure that we recognize that the 3d-promoted object EPSG:4269 (NAD83(86)) is still linked to EPSG, and thus discard ESRI 3D objects in findsOpsInRegistryWithIntermediate() Fixes a "regression" of OSGeo#4244 (one could argue which of the results is the best, given that NAD83(86) as a 3D geographic CRS has no solid foundation)
[Backport 9.5] findsOpsInRegistryWithIntermediate(): restrict to using known source/target CRS that have the same originating authority
[Backport 9.5] Database: update to EPSG v11.017
…sformations as time-dependent, only time-dependent ones...
[Backport 9.5] isTimeDependent(): do not mark 'static' Coordinate Frame helmert transformations as time-dependent, ...
…documentation]' clang-19 -Wdocumentation is super pedantic and requires an explanation for why we throw exceptions. You're so demanding clang-19! We are kind enough to mention we throw... Doxygen doesn't even require us to justify the circumstances in which we have to do that. Oh well, let's please you to get peace back...
[Backport 9.5] Fix clang-19 'warning: empty paragraph passed to '@throw' command [-Wdocumentation]'
[Backport 9.5] Omit trailing blank line in `proj_create_crs_to_crs` portion of C quickstart
[Backport 9.5] WKT importer: fix nullptr dereference on invalid VERTCS[]
…recated by sphinx-rtd-theme 3.0.0
[Backport 9.5] Doc: use 'version_selector' instead of 'display_version' which is deprecated by sphinx-rtd-theme 3.0.0
It is show as the title of the proj.org, which sends a wrong message since this is in fact a proper released version.
Remove "-dev" from release version in Sphinx config
…roj=geogoffset +dh=0
[Backport 9.5] Database: update to EPSG v11.019
Current proj.db build time is typically 50 to 60 seconds (and up to 7.5 hours on arm64 cross-compilation with full emulation!). Most of it is due to running consistency checks. Those checks actually only need to run once each time when we update the content of the database. When skipping them, the build time is cut to 3 seconds or so. So in data/CMakeLists.txt, let keep track of an expected md5sum resulting from the concatenation of the data/sql/*.sql files. When building proj.db, we check if the got and expected md5sum match. If they do build proj.db by inserting the consistency check triggers after having inserted data record. If there's a mismatch, do a one time build with the triggers inserted before the data records, check that proj.db builds fine with that, and if so, emit a CMake error message indicating to the user that they must update the PROJ_DB_SQL_EXPECTED_MD5 variable in data/CMakeLists.txt with the provided value. Next runs will go through the fast build path, until content is updated again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of PR #4282