Latest Contributions by JeffreySwain

Depending on your polygon you can get better results with a smaller cell size. That may solve some of the 'saw tooth' issues you are having.  Also be aware that if your line does not line up horizontally within a coordinate system that you will continue to have issues like this.  They can be mitigated, but not eliminated. A more appropriate question is what are you trying to achieve with the conversion where they have to match up exactly. ... View more

I think this has to do with the potential values in a float data range.  Just like you cannot create an attribute table on a raster with 32 bit float bit depth. The number of potential rows that could be added are too high and the software will prevent you from doing this operation. When you turn the floating point values into an integer, then you can access it. Perhaps your database is preventing the error that would otherwise occur and forcing it into another field type.  I haven't tested this, but the behavior is probably expected. ... View more

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.  ... View more

Right now John, the functionality to do that is not available, but should be available in a future release. ... View more

What bit depth were the original tifs?  Since they are 1 band I assume they were not 16 bit originally?  I think that the issue is probably with the bit depth being up converted.  I would consider establishing a NoData value and not promoting the value.  What you described used to be common with 1 bit data that would be upconverted and then in the pyramids the data would be lost.  Overviews by default are 8 bit, and that promotion can be problematic.  So I would consider the original conversion and not promote them from 1 bit.  ... View more

I understand your frustration. After checking the status of the bug report, it is still marked as 'assigned', which means it is being actively worked on by a developer. I know that it is not a solution, but know that it is still being worked on and should be resolved in future releases. ... View more

The source imagery can be 8 bit, but if the spatial reference is altered or if the NoData value is specified outside the range of 0-255, then the process will resample the raster. In the resampling, rather than delete data or replace values, the bit depth on the raster will be upgraded to the next bit depth.  So if you values run 0-255, a NoData value of say '0' is not set, then the process will make the NoData value 256. Then it will look at the values and upgrade the bit depth. This change from 8 bit to 16 bit usually causes a lot of the loading issues.  ... View more

When dealing with lists like this, I usually try printing out the list to see if it is what you think it is.  To piggy back to what Xander said, consider those help docs, but also I have found printing them out, copying them and they trying to run them in the Py Window seems to help me determine the proper syntax.  ... View more

So are you encountering an error? Or what his happening.  On first look, all I see is that you are using the 'Mosaic' tool rather than the 'Mosaic to New Raster' tool?  If as your title says you are looking for a new raster, then use the second tool.  Unless you are going to create a new raster prior to using the mosaic tool. ... View more

I would consider using the 3d City template and then utilize the tools to apply the roof heights.  The template is available here on GitHub. Once the values are added to the polygons, using ArcScene or ArcGlobe and setting the extrusion to the value obtained.  Please continue to look at the GitHub site as new tools are being developed all the time. They may be of use to help modify the block buildings created by the process you have described. ... View more

I see that pic now, I apologize, I am still sorting out the GeoNet-ness and missed it initially.  I do not think you should have to do it that way.  I think the design is to use a chain like Composite Bands > Geometric > Pansharpened (it would tier in the chain so you would only have to do it once rather than for each band) and only use it once.  I would think that Development would like to know if you are having to jump through such hoops.  After all this is just one scene, the if you applied the functions in a mosaic dataset, then this might be problematic unless you applied the chain during the import of the scenes to the mosaic dataset.  To get to Development, a call to Support might be in order.  However if you are fine with your workflow, then I suppose it is not necessary.  I see this as a potential bug in the software, not simply a workaround given your data.  Thanks for sharing. ... View more

So you could not use the Image Analysis window, mosaic dataset or tool to process this?  The workflow expects multiple bands and having the RPCs per band should not be a problem.  I would try the image analysis window or mosaic dataset. You probably should not have had to process each band and if you did, then I think that Support would like to see the data to pass it to development.  Mosaic Dataset Image Analysis Window The software should be able to recognized the scene normally and then apply the geometric function to the whole scene. ... View more

There is also the ability to use a mosaic dataset so that you can process multiple scenes. Since you say that you have multiple, then I would consider this. The process is similar to the Image Analysis Window, but you can apply the functions to multiple scenes.  Depending on your DEM you are using to orthorectify, you may consider creating a mosaic of the DEMs prior to this, but otherwise it should work fine.  Check out this link for the tutorial to orthorectify with the mosaic dataset. ... View more