Latest Contributions by JeffreySwain

Hi Ross,  I apologize for the delay. So I was meaning something like this. Since the training manager allows you to create individual samples that are within the same class, then I meant you could 'group' or 'collapse' them as I have in this graphic.  After re-reading your statement, I don't think that is what you want to do. So I would propose this instead, perhaps a different way of doing this. I would recommend trying to take advantage of some different application. Since what you described is more of a observation, than an image classification training sample you could take you imagery (thinking it is an image or imagery service/layer) and then use something like Field Maps or Quick Capture to collect the data as you desire. You could publish your imagery data in ArcGIS Image for ArcGIS Online.  I know it is thinking a little outside the box, but if you used quick capture for example, you could make the 'types of animals you are observing.' Let's say duck, deer, rabbit, squirrel, bird for rough examples, then you could make a quick capture app with each of them as the 'observation' in a feature layer in ArcGIS Online. Then when you found a bird, marked it ion the image - then it would record it as a bird and then give it a number. You could then quickly spin thru the image and have the data you are looking for with numbers attached.  What you are doing with the training sample is not as designed. The multiple selections would be taken in a group to generated a Esri Classifier Definition, which would then be used to classify an entire image. From your description, the samples have to be found with intense scrutiny to assess what type of animal is there. So if you were to take your training samples and then create the .ecd, then I am not sure the classification is valid, since you said each of the observations are of different animals.  The training sample manager will allow you to quickly create a point file, but not in manner you are wanting I think.  Here is the info on Quick Capture and Field Maps. I think they maybe worth your time. I know each is a 'mobile' app, but on an Ipad or similar device you can load up the imagery layer you want and then push that through and zoom/classify at your leisure. Just be sure not to use the gps of the device you are using.  ... View more

Hi RossSmail, Out of curiosity, can you describe the workflow you are using here?  If they are the same class, then why not combine them from time to time?  Were the training samples pre-generated or automated and require you to confirm if they are valid? I can definitely see where this could be hard to manage, but wanted to know more about your workflow for this process.  Please let me know.  ... View more

Well done explanation.  Thanks a bunch! ... View more

If you are interested in more Esri Training web courses, please see the Introduction to Green Infrastructure , Building the Foundation for Green Infrastructure, and GeoPlanner for ArcGIS: Exploring the Green Infrastructure in Your Study Area  web courses. ... View more

It sounds like you may be setting up a weighted overlay with multiple layers if this is the case you should probably consider a consistent cell size for all of your layers  and don't forget to use snap raster to avoid cell registration errors. So long as the cell sizes match, then the tool will not have to resample to normalize the data, which may be the issue you are describing.  If you want to create excess perhaps buffering the original polygon some prior to conversion would help. This could give you plenty of room to clip against. ... View more

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