I was trying out the Create Referenced Mosaic Dataset tool using a SQL Selection query to try to make a sub-set of rasters from a larger "Master" mosaic dataset but to my surprise it didn't seem to work. When I looked at the new referenced Mosaic dataset in ArcCatalog (contents pane) it looked like a complete copy of the contents of the "Master" mosaic dataset but not a subset.
However a colleague of mine pointed out that if you looked at the attribute table of the footprints for the referenced mosaic dataset (e.g. in ArcMap) you only see the rasters that the SQL selection query applies to so it does appear that the query did work. Has anyone else noticed this? Is this suppose to work like this?
It seems very misleading to have all the rasters of the "Master" showing up in the referenced mosaic dataset when looking at it's contents in ArcCatalog when you would think only a subset would show based on the original SQL query.
I have a Mosaic dataset in a filegoedatabase with 24 rasters in it. I ran the Create Referenced Mosaic dataset tool with a SQL query filter where OBJECTID = 1.
Looked at new referenced mosaic dataset output in ArcCatalog (contents pane) saw not only raster with OBJECTID = 1 but all 24 rasters. Expected to see only one raster in new referenced mosaic dataset whose OBJECTID = 1.
Hope that clears it up a bit
just a hunch which I have seen in other sql dialogs... don't type anything, but do selections of the inputs, the operand and use get unique values to provide the list. I suppose you are sure that all 24 are actually there outside of arccatalog and not just the original layout
Thanks for the tip Dan, I tried what you suggested but the end result is the same. The referenced mosaic dataset is still showing all the rasters from the original as included in the referenced mosaic dataset. See image below:
The odd thing is that when you add the referenced mosaic to ArcMap and look at the footprint attribute table it only shows the one raster (which was selected via the SQL Query). See image below.
So in effect the referenced mosaic dataset is working as intentded but it's just the contents view in ArcCatalog that is misleading in my opinion but I don't know, I didn't design the software so I don't know if it is meant to be like that
Did you ever find a solution to this? I'm experiencing the same behavior with my referenced mosaic datasets, which is causing problems further down the line in my workflow.
Hey Aaron sorry for the very very late reply! I don't log on to Geonet very often and I must have missed the notification about your reply.
To answer your question I have not found a solution to this. I just work with it like it is, perhaps it's been fixed in the latest version of ArcGIS desktop / Pro. I'm still using 10.3.1 but will be upgrading later to 10.5.1.