-
Notifications
You must be signed in to change notification settings - Fork 5
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
Metwork 1.0 - Upgrade GDAL to the latest version #1230
Comments
I think, proj package must be upgrade to avoid error like this : |
I will try to do it but :
|
Thanks for your comments. Yes, I understand it's not so easy tu upgrade gdal ad its depencencies. Currently we use Metwork 1.0.x with Metgate SWIM. I understand the gdal upgrade will be in a Metwork version > 1.2. So we will have to upgrade the Metwork version. Is there major difference between Metwork 1.0, 1.1, 1.2 ? How to upgrade from Metwork 1.0 to 1.1, 1.2 ? Just change the yum repo or do we need to unistall Metwork 1.0 and install Metwork 1.1 or 1.2 |
There is no huge refactoring between Metwork 1.0 and Metwork 1.1 or Metwork 1.2, but many bug fixes, upgrades or new provided packages in mfext and addon_scientific mostly. Since last week you can find the complete changelogs of all releases in the master branch of each Metwork repository. |
GDAL has not been upgraded either in Metwork 2.0 released last month. Can you provide more details on your problem regarding PROJ, may be in another issue (I would like to close this one) ? I intend to upgrade at least to PROJ 7. |
For your information, the major change in Metword 2.0 is that it is built under rockylinux 8.5. So it can't be installed on centos 6 or 7. |
GDAL is now in 3.5.3 and PROJ in 9.0.1 in master branch and release 2.1. |
Is possible to upgrade GDAL version to the latest version, e.g. v 3.3.3 ?
Currently, GDAL version 3.0.2. This version doesn't handle
[nmi_i]
unit in GML. V 3.3.3 handles this unit : see OSGeo/gdal#3118.For example, create geometry from the following gml doesn't work with v 3.0.2 :
The geometry create with ogr.CreateGeometryFromGML() python function is not correct, uom="[nmi_i]" not recognized by GML Reader, and it assumes uom is deg in this case.
It works with v3.3.3.
The text was updated successfully, but these errors were encountered: