-
Notifications
You must be signed in to change notification settings - Fork 202
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
Avoid passing encoding creation option to format drivers that don't support it #504
Comments
I can't see any way to ask GDAL which creation options are supported by a driver/dataset/layer. Do we need to build our own list for the drivers we support? |
According to http://www.gdal.org/gdal_8h.html#aec318ffe797555656fe678558c576b23 Still, I think the immediate thing for me to do is to eliminate the encoding option in the GeoJSON case. |
Looks like MapInfo is the same. |
KML driver as well
|
Resolves #504 in a more general way than previously.
* Invalid creation options are filtered and ignored Resolves #504 in a more general way than previously. * Update change log
Done! |
See #468 (comment): the GeoJSON driver warns that ENCODING isn't supported.
@mattayes the warning is harmless but we can avoid it.
The text was updated successfully, but these errors were encountered: