-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
PDF: remove write support for GEO_ENCODING=OGC_BP #11048
base: master
Are you sure you want to change the base?
Conversation
for 3.11 Several reasons: - support for SRS has always been partial - and the actual trigger for this pull request: lately the company behind the OGC Best Practice encoding has behaved in a unfriendly way with respect to our community. No need to promote their techs further.
3d0c114
to
31f2f4e
Compare
Well, we'll need to remove that export options at least. I'm unsure how widely used it is. @andreasneumann do you know if this option is required for compliance? Perhaps you could check with the Swiss user group? |
I had some memories that PDF created with the OGC_BP couldn't be properly read with the T....Go toolbar due to it requiring them to be signed (it could open them, but wouldn't take into account the georeferenced info). But I could be wrong. |
The GDAL project highly values your contribution and would love to see this work merged! Unfortunately this PR has not had any activity in the last 28 days and is being automatically marked as "stale". If you think this pull request should be merged, please check
|
While we hate to see this happen, this PR has been automatically closed because it has not had any activity in the last 6 weeks. If this pull request should be reconsidered, please follow the guidelines in the previous comment and reopen this pull request. Or, if you have any further questions, just ask! We love to help, and if there's anything the GDAL project can do to help push this PR forward please let us know how we can assist. |
gentle ping @andreasneumann |
for 3.11
Several reasons:
CC @nyalldawson Will that be an issue for QGIS?