Tom - can you provide a bit more information? 1) are you outputting TIFF format, and have you tried other formats?2) are you using any compression?3) have you tried reading your output images in software other than MapInfo?4) are the images 8 bit, 16? single, multi band? integer or float?5) can you upload a small sample for us to examine?Thanks[ATTACH=CONFIG]17521[/ATTACH]Cody B.
CodyI have tried multiple formats and compressions with the same results.I have tried opening or viewing with graphics programs like Photoshop and Irfanview with the same results.I have attached sample.zip containing a rectified image from 10.1The image is fairly low res earth imagery, is visible with ArcMAP, but black with Photoshop.9.3 or 10.0 did not give me this type of grief.Thank you in advanceTom
I was having this issue too -- thanks Travis for the suggestion. Changing NoData from "256" to blank fixed the problem. What's up with that?
BTW, Jeffrey Swain, I checked, and the bit depth had been upgraded to 24... strange!
Anyway, thanks for the suggestion!
The promotion is most likely due to the resampling. When the raster is resampled the bit depth is promoted to allow for any change in spatial extent due to projection change or something else. You can see this effect, by clipping a raster with a graphic selected by Data > Export data. When you perform this, there will be a prompt asking you if you would like to promote the bit depth. Say 'No' and it will remain the bit depth of the original. If you say 'Yes' then the exported raster will have the promoted bit depth. Since you said yours is 24 bit, then perhaps the originals were 16 bit? Just a guess. Using the Copy Raster tool to turn it back down to the proper bit depth should work, provided you won't be losing any values in the process.
When you are exporting your image in ArcMap, do you keep the default values and just check the "Use Renderer" and the "Force RGB" boxes? I had the same issue and I solved it this way.
Source: 4th step in the ressource page ArcGIS Help 10.1
I was just helping a client with almost the same issue (8-bit RGB TIFF, saves as rectified black TIFF) and found the same fix, but I was setting 255 as the nodata value. You actually can still use this file, but you have to set RGB stretch to not-None in ArcMap and this doesn't help you at all outside ArcMap.
I didn't get any joy out of changing the environment settings, mostly because I believe they only apply to geoprocessing tools.
My Google-Fu failed. Does anyone know of a way to set the default nodata value in the Georeferencing - Rectify - Save As dialog so that you don't have to reset it for every single rectification?
This issue was really screwing with me in CityEngine 2016.1. I'm glad I found this post.
I can verify that this issue persists in ArcMap 10.3.1 and that setting the 'NoData Value (optional)' setting to 0 when using Clip (raster) is the only way to solve it. It will set the 'Pixel Depth' to 8 Bit and the 'NoData Value' to 0, 0, 0.
Do not set the value to blank! Blank sets the 'Pixel Depth' to 16 Bit and the 'NoData Value' to 256, 256, 256.
You can see the difference in Windows Explorer.
Wow, this just happened to me in 10.6.1. Did you guys really not fix this yet? Such that the default is a blank NoData field? I just wasted 20 min trying to figure this out
Just happened to me as well. Wasted over an hour testing different export settings and self-trouble-shooting. Entire georeferenced images were exporting as all black, even within ArcMap, and somehow even managing to mess up the control links on the image, e.g. after export, I was left with an all black image that was not in the position of the original georeference, e.g. image shifted 100 ft to the right.
To fix:
Check the boxes: "Use Renderer" and "Force RGB" and set NoData value to 0.
Thanks Chris !!
and Jeremy of ESRI (for giving us some background to this).
This fixed the problem for me too!. I was doing almost 30 mins of trouble shooting and fortunately I came across this thread. ESRI should make a technical support article for this issue if they have not already done so, especially since people are still having to deal with this after 8 years.
There are many people like us using other 3D Modeliing software packages like Leapfrog 3D and Vulcan etc in conjunction with ESRI products and readily available knowledge of this issue would come in handy.
Thanks again,
Aziz
I’m getting black output in ArcGIS Pro as the georeferenced image is saved as per the screenshots below.
What could be the issue here?
is this a bug?
the image is attached
Hey @JamalNUMAN ,
Might be better to start a new one for more visibility, but I think you should be mindful of this setting.
When you save the georeferenced image, in order to catch any changes in the extent often the default is to promote the bit depth of the input image and then assign a new NoData Value. Be sure to review the properties of the image before you save it and make sure that the bit depth and the NoData value matches. For me since it looks like you are using a jpeg, I might convert it to a tif first and then georeference that. Sometimes jpegs can be touchy when georeferencing in my experience.
The issue appears to be a bug in Pro 3.0.2 as the X, Y, columns, and rows are assuemd to be populated automatically.
I tried it in P 3.1.1 and works fine
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
