Latest Contributions by SepheFox

Ok, I upgraded to the ArcGIS Metadata for this test layer. No dice. Same result after I exported the file again: ... View more

First, I would only rename stuff in ArcCatalog, or the ArcCatalog window in ArcMap. That way you don't have to worry about the parts--it will do that for you. Second, how are you changing the projection of a raster? It shouldn't make any more files than you had before, unless your changing formats or something, and even then, folders shouldn't be involved. I would recommend creating file geodatabases to store your data in. You don't run into naming difficulties (except you can't start a name with a number) with a geodatabse, and there are a lot of other benefits, too numerous to mention. ... View more

Hi Joshua, what's the issue exactly? I don't see anything obvious in your screenshot. ... View more

October of last year? Not quite...  10.0 came out in 2010 . ... View more

Well I suppose I could try upgrading the metadata. We only switched to 10.3 last week though. Prior to that we had been using 10.2 since whenever that came out (years). In my screenshot example, the metadata stopped circa October 2014. It seems unlikely to be related. ... View more

Right, that is the expected behavior. Problem is, that's not what's happening for me, particularly with datasets that have a very loooooong history. See my previous attachments. ... View more

I keep notes too. That won't help if you make a mistake, or don't do what you thought you did. I second guess myself ALL the time, so the history for each data layer can be a really useful way of going back and seeing if you messed up in some way. It can also CYA when questions about data come up (or not ), months after the fact. I can't find any documented reason why this history doesn't extend all the way to the present, for some data. Maybe it's a bug of some kind? ... View more

Thanks for your comment. So, the help file you linked says: "Each geoprocessing tool that creates new output data or updates the input data will add metadata about the execution of the geoprocessing tool, which includes the tool name, its location, and the parameters used. This behavior can be disabled in desktop applications by un-checking the Log geoprocessing operations to a log file option found in the Geoprocessing > Geoprocessing Options dialog box. In a Python script, logging of geoprocessing history can be disabled using the SetLogHistory function. Metadata for a dataset is viewed by right-clicking a dataset in the Catalog window or ArcCatalog and choosing Item Description." You can see I do have that box checked in geoprocessing options: I performed a test, a simple export of an FC to a shapefile, just now. Here is the item description window for the output, showing results only up to October of last year: Do you see what I'm saying? I'm wondering if there is some kind of limit on the length of the geoprocessing history. ... View more

So I looked in the History folder described in the Stack Exchange thread. I see a long list of XML files there, but what are they? How do I view them, and, once viewed, how would I associate them with a particular feature class? It's the recent history that doesn't seem to be retained, so setting a longer time in geoprocessing options won't help. ... View more

Well, you could symbolize your lidar using classified, and then manually change the classification so that the first  class is -20-0, and then examine the raster for that class visually. ... View more

He Elio, if you have the spatial analyst extension I would try using the zonal statistics tool: ArcGIS Desktop. ... View more

Just to clarify, I'm not talking about the results window, but rather the metadata for a data layer. ... View more

Are you positive that C:\Users\JOC-001\Documents\ArcGIS\Default.gdb\Illinois exists, is a valid input, and is in the same coordinate system as your input layer? ... View more

Hi Justin, if, indeed the DGN data has no geographic location data, as you say, then it should be bought in without a spatial reference and georectified by hand. I suspect though, that your data does have some kind of location data applied to it, as it appears to be projecting, at least at the right size, if not the correct location. Assuming that your last picture, "coords", is the coordinates of the DGN, I don't recognize an obvious coordinate system. Try importing the original data into an empty map, and leave the spatial reference blank. If you examine the properties, source tab, what extent is shown there? A screenshot of this can often help people take a better guess at what coordinate system the data was created in. ... View more