Re: [GRASS-user] Rotating raster maps
On Wed, 18 Jul 2018, Markus Neteler wrote: Yes: https://grass.osgeo.org/grass74/manuals/addons/#i -> i.rotate Markus, Thanks. It's been a very long time since I worked with remotely acquired imagery. Much appreciated, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Rotating raster maps
On Wed, 18 Jul 2018, Daniel Victoria wrote: But are those tif images? Or GeoTiff? Because, if those are geotiffs, with correct georeferencing, I believe rotating will mess things up. Daniel, Probably GeoTIFF. If rotating is not the solution is there another way to patch them together without thin wedges? Regards, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r,in.gdal error when importing a jpeg2000 image
>Can you point me to where the differences are between importing >and linkin https://grass.osgeo.org/grass75/manuals/r.external.html Anything missing in the manual? - best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r,in.gdal error when importing a jpeg2000 image
Hi Nikos, Would i be able to use the 'i.segment' module on subsets of the image if i use 'r.external' instead of importing? Can you point me to where the differences are between importing and linking? Thank You, Paul Shapley On 18 July 2018 at 13:48, Nikos Alexandris wrote: > * Paul Shapley [2018-07-18 09:32:56 +0100]: > > Hi Users, >> >> Trying to import an 8.7gb (jpeg2000) image into Grass 7.4.1 64 bit. I get >> the error below. Tested the image in another OS GIS package and it opens >> without issue. Not sure why Grass wont import it. >> >> Thanks everyone! >> >> Paul Shapley >> >> > If it's a driver issue (like Daniel mentions in his post) and GDAL can > read it, do you really need to import it? You know that you can link to > it via r.external. > > Nikos > > [..] > -- *Paul J. Shapley *MSc CGeog (GIS) FRGS ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Rotating raster maps
On Wed, Jul 18, 2018 at 2:53 PM, Rich Shepard wrote: > I have .tif images at 1:5000 or 1:6000 scale that are each slightly > rotated clockwise on their rectangular backgrounds. The imported raster maps > are also slightly torqued so edges do not properly align (see attached > screenshot). > > Is there an i.* module that can rotate them Yes: https://grass.osgeo.org/grass74/manuals/addons/#i -> i.rotate Markus > so when patched together there > are no gaps? > > Rich > ___ > grass-user mailing list > grass-user@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Rotating raster maps
But are those tif images? Or GeoTiff? Because, if those are geotiffs, with correct georeferencing, I believe rotating will mess things up. On Wed, Jul 18, 2018 at 11:48 AM Markus Neteler wrote: > On Wed, Jul 18, 2018 at 2:53 PM, Rich Shepard > wrote: > > I have .tif images at 1:5000 or 1:6000 scale that are each slightly > > rotated clockwise on their rectangular backgrounds. The imported raster > maps > > are also slightly torqued so edges do not properly align (see attached > > screenshot). > > > > Is there an i.* module that can rotate them > > Yes: > https://grass.osgeo.org/grass74/manuals/addons/#i > -> i.rotate > > Markus > > > so when patched together there > > are no gaps? > > > > Rich > > ___ > > grass-user mailing list > > grass-user@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-user > ___ > grass-user mailing list > grass-user@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Rotating raster maps
On Wed, 18 Jul 2018, Daniel Victoria wrote: Some satellite images comes rotated, with black borders. But if we rotate them prior to patching, we mess up the georeferencing. The process then is setting those borders to null and then patching. If this is your case, then I'd try running `r.null` to set those borders as no-data and then use `r.patch`. But again, not sure if this is your case Daniel, Worth a try. Thanks, Rich ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Problem with half basins becoming fragmented using r.watershed
Thank you again Massi. This fixed my problem! On Mon, Jul 16, 2018 at 10:10 PM, Massi Alvioli wrote: > 2018-07-16 18:53 GMT+02:00 Erin Hanan : > > Hi Erin, > > let me forward your email to the list, since this may be interesting to > others. > > > Yes, this helps a lot; thank you! I've been reading through your paper > and > > see that you mentioned one possible solution would be to remove slope > units > > smaller than "cleansize", and then enlarge the adjacent slope units to > fill > > the missing area using the r.grow. I'm curious whether I can also achieve > > this using r.area to remove the small half basins and then r.grow. I've > also > > installed your software (r.slopeunits), and am planning to experiment > with > > the different approaches today. > > > > By the way, I forgot to mention it in my original email, but yes, I tried > > several different threshold values. Interestingly, changing the threshold > > tended to change the size of larger half basins, but the sliver and > > fragmented basins always remained a problem. > > > > Anyway, thanks again for your very helpful email! > > You are most welcome. Also, one of our cleaning approaches does > exactly what you suggest: > remove small areas and fill the empty spaces with r.grow. > > Let us know if you get meaningful results! > > > Massi > ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] Rotating raster maps
Some satellite images comes rotated, with black borders. But if we rotate them prior to patching, we mess up the georeferencing. The process then is setting those borders to null and then patching. If this is your case, then I'd try running `r.null` to set those borders as no-data and then use `r.patch`. But again, not sure if this is your case Cheers On Wed, Jul 18, 2018 at 12:06 PM Rich Shepard wrote: > On Wed, 18 Jul 2018, Daniel Victoria wrote: > > > But are those tif images? Or GeoTiff? Because, if those are geotiffs, > with > > correct georeferencing, I believe rotating will mess things up. > > Daniel, > >Probably GeoTIFF. If rotating is not the solution is there another way > to > patch them together without thin wedges? > > Regards, > > Rich > > ___ > grass-user mailing list > grass-user@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-user ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
[GRASS-user] r,in.gdal error when importing a jpeg2000 image
Hi Users, Trying to import an 8.7gb (jpeg2000) image into Grass 7.4.1 64 bit. I get the error below. Tested the image in another OS GIS package and it opens without issue. Not sure why Grass wont import it. Thanks everyone! Paul Shapley (Wed Jul 18 09:19:16 2018) r.in.gdal -o input=J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2 output=aerial_25cm_master memory=3000 Over-riding projection check Importing 3 raster bands... Importing raster map ... ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0 ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0 ERROR 1: Marker is not compliant with its position ERROR 1: opj_decode() failed ERROR 1: J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: IReadBlock failed at X offset 0, Y offset 0
Re: [GRASS-user] r,in.gdal error when importing a jpeg2000 image
On Wed, Jul 18, 2018 at 10:32 AM, Paul Shapley wrote: > Hi Users, > > Trying to import an 8.7gb (jpeg2000) image into Grass 7.4.1 64 bit. I get > the error below. Tested the image in another OS GIS package and it opens > without issue. Not sure why Grass wont import it. > > Thanks everyone! > > Paul Shapley > > > (Wed Jul 18 09:19:16 2018) > r.in.gdal -o input=J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2 output=aerial_25cm_master > memory=3000 > Over-riding projection check > Importing 3 raster bands... > Importing raster map ... > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed ... As posted by others, this is a problem of your GDAL installation. Please check which of the several JP2000 drivers you actually use. They quite differ in performance and compatibility. Also: which GDAL version do you use? Best Markus (who frequently works with JP2 data) ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r,in.gdal error when importing a jpeg2000 image
* Paul Shapley [2018-07-18 09:32:56 +0100]: Hi Users, Trying to import an 8.7gb (jpeg2000) image into Grass 7.4.1 64 bit. I get the error below. Tested the image in another OS GIS package and it opens without issue. Not sure why Grass wont import it. Thanks everyone! Paul Shapley If it's a driver issue (like Daniel mentions in his post) and GDAL can read it, do you really need to import it? You know that you can link to it via r.external. Nikos [..] signature.asc Description: PGP signature ___ grass-user mailing list grass-user@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-user
Re: [GRASS-user] r,in.gdal error when importing a jpeg2000 image
On Wed, Jul 18, 2018 at 10:32 AM, Paul Shapley wrote: > > Hi Users, > > Trying to import an 8.7gb (jpeg2000) image into Grass 7.4.1 64 bit. I get the error below. Tested the image in another OS GIS package and it opens without issue. Not sure why Grass wont import it. The errors are coming from GDAL, not GRASS. The same error messages should appear with GDAL tools that read the entire image, e.g. gdal_translate. Markus M > > Thanks everyone! > > Paul Shapley > > > (Wed Jul 18 09:19:16 2018) > r.in.gdal -o input=J:\Spatial Data\Aerial\APGB_received_20180416\aerial_25cm.jp2 output=aerial_25cm_master memory=3000 > Over-riding projection check > Importing 3 raster bands... > Importing raster map ... > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not
Re: [GRASS-user] r,in.gdal error when importing a jpeg2000 image
Did you try running gdalinfo on your image? Does it work? The GDAL raster format page [1] lists that JPEG2000 support is not compiled by default. So it could be that your gdal installation does not recognize this file [1] http://www.gdal.org/formats_list.html On Wed, Jul 18, 2018 at 5:33 AM Paul Shapley wrote: > Hi Users, > > Trying to import an 8.7gb (jpeg2000) image into Grass 7.4.1 64 bit. I get > the error below. Tested the image in another OS GIS package and it opens > without issue. Not sure why Grass wont import it. > > Thanks everyone! > > Paul Shapley > > > (Wed Jul 18 09:19:16 2018) > > r.in.gdal -o input=J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2 > output=aerial_25cm_master memory=3000 > Over-riding projection check > Importing 3 raster bands... > Importing raster map ... > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0, Y offset 0 > ERROR 1: GetBlockRef failed at X block offset 0, Y block > offset 0 > ERROR 1: Marker is not compliant with its position > ERROR 1: opj_decode() failed > ERROR 1: J:\Spatial > Data\Aerial\APGB_received_20180416\aerial_25cm.jp2, band 1: > IReadBlock failed at X offset 0,
