Latest Contributions by GünterDörffel

Since you are working in an Enterprise Geodatabase Environment it is hard to tell why this is locked. It lockes when trying to create the fields - even if this is a process that accepts existing fields. I can make another modification - and remove the ATTEMPT to create the fields as they are never actually need to be added - I've updated the attachement above. I left the warning for existing fields in there but added a counter-message that tells you how many records are updated. Keep in mind: I only check for the LAT field being NULL ... if so - record is updated .... I renamed the UI-selection to be POINT_LAT_LONG only to reflect more what you do ... hope it works for you - then you owe me a beer 🙂 and some points here 🙂 ... View more

Here something to try that shows VERY VERY FEW of the possibilities but is also advanced at the same time: Find attached a small zip. Please extract to c:\temp .. important to make it work without changes. It is a 10m resolution dataset, OGD for the whole of Austria. This mosaic does come with some pre-rendered overviews but it does not contain the raw data. The raw data is on Amazon and will be cached as soon as you request some part of it! So be patient when you zoom in ...  Add the Mosaic to ArcMap (I assume?). The default you see is a plain elevation type of display. I also added three predefined function templates for you to open. Proceed like this: In ArcMap open layer properties of Image Sub-Layer. Go to Processing Templates Tab and start by selecting "Hillshade" and apply. This will display the Raster as a Standard ArcGIS Hillshade. The fun stuff with functions is, that you can pass arguments to them. See this screenshot: If you name a property ZFactor_1 and change the value and apply - the display will change. So as an end-suer you can have access to settings of a function template if wanted ... The second function included is "Slope in classes" which shows that a classification can be handed over to the mosaic. It is done by a colormap (also part of the zip) and will be reflected in the TOC The third example uses this dataset twice as input to a vector field renderer function.Please zoom in considerably, probably double up the layer and make the hillshade-view your "basemap". Then with the vector field you'll see sort of "decination vectors" created from slope and direction. Will look something like this when applied as described. And remember to be patient when zooming in ... data will be fetched from Amazon. With local real data in appropriate formats, mosaics are FAST 🙂 Regards and hope that helps Guenter ... View more