Opened 11 years ago
Closed 5 years ago
#5206 closed enhancement (wontfix)
KMLSuperOverlay bounding box variant <gx:LatLonQuad> not supported
Reported by: | cgodkin | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | closed_because_of_github_migration |
Component: | default | Version: | 1.10.0 |
Severity: | normal | Keywords: | KMLSuperOverlay gx:LatLonQuad |
Cc: |
Description
The function KmlSuperOverlayGetBoundingBox() doesn't deal with <gx:LatLonQuad>. I don't see a simple way to suggest a patch to this function to support it since it would appear to need some sort of warping on the fly because the gx:LatLonQuad is not necessarily a rectangle.
Attached will be an example of a dataset with this sort of bounding box.
Attachments (1)
Change History (3)
by , 11 years ago
Attachment: | s523_DTM.kmz added |
---|
comment:1 by , 10 years ago
GDAL 2.0-dev gives this:
ogrinfo -al -so s523_dtm.kmz ERROR 1: ERROR Parseing kml Style: No id INFO: Open of `s523_dtm.kmz' using driver `LIBKML' successful. Layer name: 0 Geometry: Unknown (any) Feature Count: 1 Extent: (-86.051901, 41.065544) - (-86.046436, 41.069912)
I do not know if the meaning of "doesn't deal with" was that GDAL can't read the bounding box at all or that GDAL reports wrong bounding box. If it was the first one, now GDAL obviously can read the bounding box and ticket can be closed as solved. It the latter (wrong bounding box) it would be nice to know the correct bounding box.
comment:2 by , 5 years ago
Milestone: | → closed_because_of_github_migration |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.
KMLSuperOverlay example with gx:LatLonQuad bounds