-
Notifications
You must be signed in to change notification settings - Fork 25
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
Proj4 undefined when loading own geotiff #252
Comments
Thanks for reporting this bug. I'll look into it ASAP. |
Hi, @tammojan . There seems to be a few things going on. Here's the output when I run
GeoTIFF.io depends on georaster-layer-for-leaflet, which depends on georaster. Specifically, georaster looks for the GeographicTypeGeoKey or ProjectedCSTypeGeoKey in order to determine the projection. Running
Based on the projection information visible, it seems that you are using EPSG 436 (https://epsg.io/4326). Is it possible for you to set GeographicTypeGeoKey to 4326? If not, we will find another way to make this work for you :-) |
Here's GeoTIFF spec for reference: http://geotiff.maptools.org/spec/geotiff6.html |
Thanks for looking into this! I created the GeoTiff with rasterio, using the example from the docs, in particular using There's still a slight problem (the map now shows up meters off, and upside down), but I can fix that by looking at the projection more carefully. So this is not a geotiff.io bug, though maybe the error message could be slightly clearer. |
The updated geotiff is at here , the code that generates it is here. I'm not sure what I'm doing wrong, since the GeoTIFF shows up nicely in QGIS. Running gdalinfo on the updated geotiff yields
and
So there is still no reference to |
@tammojan , thanks for working with me and being so thorough! I'll write a work around to handle the case when someone generates a GeoTIFF with One first glance the GeoTIFF.io is flipping the geotiff because its dependency georaster assumes that the second value in pixel size is a negative number, which is more commonly seen.
Here's gdalinfo of Could you check something for me? Does the origin in On further research, it appears that your GeoTIFF is being created with a ModelTransformationTag In either case, the fix isn't too complicated but will require an update to http:/geotiff/georaster. I've created an issue on that repo at : GeoTIFF/georaster#47. Thank you very much for your patience and help discovering these bugs! |
Hi @DanielJDufour , thanks for the quick reply! To avoid confusion about up and down, here's a screenshot from QGIS that shows the correct overlay. |
The extents of the image are:
So (11.709118377901767,50.977990063336165) corresponds to the bottom left (not top left). |
Describe the bug
On the online version app.geotiff.io , I tried to load my own GeoTIFF file. It does not show up on the map, and the console reports:
To Reproduce
Expected behavior
A map shows up (somewhere in Germany)
Desktop (please complete the following information):
Other context
There may be missing metadata in the GeoTIFF file, though it loads fine in QGIS. If there is something missing, I'd like to learn that so that I can improve the software that writes it.
The text was updated successfully, but these errors were encountered: