Made changes to appropriate java files to fix raster download methods…#34
Open
bhickson wants to merge 5 commits intoOpenGeoportal:masterfrom
Open
Made changes to appropriate java files to fix raster download methods…#34bhickson wants to merge 5 commits intoOpenGeoportal:masterfrom
bhickson wants to merge 5 commits intoOpenGeoportal:masterfrom
Conversation
Create setSortableLayers function into searchResultsTable and inserted function into attachEvents
Add layerId as id value for each rowContainer (e.g. 'id = "arizona_censusBlocks_2015" ' ). Allows us to tie zIndex value to div position in previewedLayers when layer(s) are dragged around.
Change cursor on previewedLayers hover to let user know that layer position can be changed with drag and drop
Previewed layers sortable
…. Previously, the bounding box would be passed regardless of raster pixel alignment. This would cause the raster to be transformed to coincide with the bounding box. Changes made allow for the bounding box to be snapped to the nearest raster pixel edge so that a transformation will not take place. This was causing a particular issue with multi-band raster where 0 values in a pixels R,G,B values (i.e. 145,0,79) would be set to the whole pixel to "no-data" in transformation, resulting in pixel holes throughout the image.
Contributor
Author
There was a problem hiding this comment.
No longer need generateSize. The getCoverageRequest string is composed near the end of the file.
Contributor
|
Hi @bhickson , I merged your changes here into the branch https://github.com/OpenGeoportal/OGP2/tree/bhickson-wcsRequest_BBFix |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…. Previously, the bounding box would be passed regardless of raster pixel alignment. When geoserver would recieve the WcsGetCoverage request where either the bounding box mins and maxs divided pixels OR if resx&resy were specified instead of width&height, it would cause a JAI warp operation which was transforming the produced raster to correspond to the bounding box. Changes made allow for the bounding box to be snapped to the nearest raster pixel edge instead so that a transformation will not take place. As well as shifting the raster, this was causing a particular issue with multi-band raster where 0 values in a pixels R,G,B values (i.e. 145,0,79) would be set to the whole pixel to "no-data" in transformation, resulting in pixel holes throughout the image.
E.g.:
Previous request....
bbox=464037.9751723,3477809.4781196,470646.2581182,3485398.5767305&crs=EPSG:26912&format=geotiff&resx=1.0&resy=1.0
New request...
bbox=464037.0,3477809.0,470646.0,3485398.0&crs=EPSG:26912&format=geotiff&width=6609&height=7589