Skip to content
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

Unable to write KMZ to Cloud Storage #10313

Closed
jeff-bradley opened this issue Jun 26, 2024 · 0 comments · Fixed by #10318
Closed

Unable to write KMZ to Cloud Storage #10313

jeff-bradley opened this issue Jun 26, 2024 · 0 comments · Fixed by #10318
Assignees

Comments

@jeff-bradley
Copy link

What is the bug?

When trying to write a KMZ to Google Cloud storage I get this
ERROR 6: Seek not supported on writable /vsigs/ files

Steps to reproduce the issue

I have no issue with writing KML's but KMZ wont work. I have tried

ogr2ogr -f LIBKML "/vsigs/PROJECT/kml/kml_output/cities.kmz" --config CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE YES PG:"host=127.0.0.1 port=5435 user=user dbname=dbname password=password" --config GS_ACCESS_KEY_ID REMOVED --config GS_SECRET_ACCESS_KEY REMOVED -sql "SELECT * EXCLUDE(tab_style, insert_date), 'LABEL(w:0);SYMBOL(id:\""https://maps.google.com/mapfiles/kml/shapes/placemark_circle.png\"",s:1)' AS OGR_STYLE HIDDEN FROM cities " -dialect OGRSQL -mapFieldType DateTime=String

I would have thought the CPL_VSIL_USE_TEMP_FILE_FOR_RANDOM_WRITE YES would have fixed it like this issue #3604 but no change after trying all different GDAL_HTTP_VERSION

Versions and provenance

Windows 11 and tried on Ubuntu 20 WSL
GDAL 3.10

Additional context

#10138 (comment)

@rouault rouault self-assigned this Jun 26, 2024
rouault added a commit to rouault/gdal that referenced this issue Jun 26, 2024
rouault added a commit to rouault/gdal that referenced this issue Jun 26, 2024
@jeff-bradley jeff-bradley changed the title Unable to write KMZ to GCS Unable to write KMZ to Cloud Storage Jun 27, 2024
rouault added a commit that referenced this issue Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants