-
Notifications
You must be signed in to change notification settings - Fork 27
-
Notifications
You must be signed in to change notification settings - Fork 27
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
TypeError: in method 'SpatialReference_ImportFromEPSG', argument 2 of type 'int' #30
Comments
@rebkwok - is any maintainer able to fix this soon? Is there any WIP/PR to address it? The gdal2mbtiles utility is not compatible with gdal 3.x yet. OK versions in a docker image with conda/pip packages installed on Ubuntu 18.04:
Failure versions on a laptop VM running Ubuntu 18.04 with conda/pip packages installed:
|
@darrenleeweber Not sure when we will get to addressing this particular issue. PRs accepted. |
@damon-rand - I'm not likely to work on this until it's essential to upgrade to a new version of GDAL and even then I'm not likely to work on it, as I have no experience with developing this project. If the contributors who develop this project have abandoned it, that would be good to know (and also why it is abandoned). |
@darrenleeweber Nothing has been abandoned. We welcome and merge community contributions and our own. We just have other, more pressing, priorities than this one. |
I suggest this issue is marked as a bug when using GDAL 3.x and the priority to fix bugs should be high enough for core project developers to attend to it. |
So there is a bug with the Spatial Reference not being overwritten via the parameters or returning a correct Projection due to hardcoded logic which results in the issue @ryanjkelly is experiencing, we'll see if it can be corrected when possible, though community contributions are welcome. |
Been looking at this today aswell. going back bit earlier, when a Dataset is instantiated (helpers.py, line 193), attempts at calling the method GetSpatialReference() raises an error if the epsg is not recognised by method sr.AutoIdentifyEPSG() (gdal.py, line 458). This is true for the lambert canonical projection on the .tif above.
|
This issue is related/duplicates #28 Our team has bumped into this bug again, so now it's a blocker and I have to focus on a solution, either tracking down the bug with a quick hack-fix or finding a set of versions that work or looking closer at the CRS in our GeoTIFFs. Using masterFirst, simple question - master has a few commits since the
overriding the CRS with an EPSGReplacing the CRS (WKT) in the GeoTIFF profile with an EPSG code is a possible work around, if the CRS exactly matches an EPSG code (not always possible). But, bumped into another bug that's not specific to this issue (maybe there's another issue on this):
|
I'm trying to convert the TIFFs from the FAA's VFR Raster Charts page and I'm getting this error:
Here is the output from
gdalinfo -noct test.tif
:I'm using:
The text was updated successfully, but these errors were encountered: