Note: Filling out this template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the
maintainer's discretion.
Description of the Change
Fixed bug where the format chosen for exporting images was always returning null, preventing the user from exporting any images except for elevations.
Added more file filters to the Swing FileChooser and added a hashmap for matching those extensions to mime types
Why Should This Be In Core?
Giving new developers and users an example of how to export georeferenced images from WWD will greatly help their efforts in creating specialized versions of WWD, or how to add this functionality to their current WWD products.
Benefits
Developers will be able to build off of this example and produce locally saved imagery.
Potential Drawbacks
If any of the WMS endpoints end up not supporting the mimetypes I added (like how arcGIS supports image/tiff but not image/tif) then those extensions would have to be removed from the added user options.
Applicable Issues
It would be great though if there was another example of how to make these export functions used the locally cached map tiles instead of requesting them repeatedly from a WMS endpoint. I know the elevations are exported by reading local data, but for some reason the Image capture functions don't seem to be able to read / access / or modify a local cache and instead it defaults to making new WMS requests.
Note: Filling out this template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainer's discretion.
Description of the Change
Why Should This Be In Core?
Giving new developers and users an example of how to export georeferenced images from WWD will greatly help their efforts in creating specialized versions of WWD, or how to add this functionality to their current WWD products.
Benefits
Developers will be able to build off of this example and produce locally saved imagery.
Potential Drawbacks
If any of the WMS endpoints end up not supporting the mimetypes I added (like how arcGIS supports image/tiff but not image/tif) then those extensions would have to be removed from the added user options.
Applicable Issues
It would be great though if there was another example of how to make these export functions used the locally cached map tiles instead of requesting them repeatedly from a WMS endpoint. I know the elevations are exported by reading local data, but for some reason the Image capture functions don't seem to be able to read / access / or modify a local cache and instead it defaults to making new WMS requests.