Latest Contributions by Tim_McGinnes

The most common way of displaying raw data without normalizing is to use proportional symbols. ... View more

The Zonal Statistics tool should work for this. Input would be your 100m buffers and DEM, and choose MEAN as the statistic. Will return the average of the DEM values in the buffer which you can then quite easily compare to the original DEM value to see if they are generally above or below. ... View more

You can load the WMS layer into ArcGIS and look at the Properties. Screenshot attached shows the layer and that the spatial reference is WGS84 (EPSG:4326). You can also do a GetCapabilities request on the WMS service itself: https://wms.geonorge.no/skwms1/wms.nib?service=wms&request=GetCapabilities  It shows that the service supports quite a few different coordinate systems: <Layer queryable="1"> <Name>ortofoto</Name> <Title>ortofoto</Title> <Abstract>ortofoto</Abstract> <CRS>CRS:84</CRS> <CRS>EPSG:4326</CRS> <CRS>EPSG:25833</CRS> <CRS>EPSG:32632</CRS> <CRS>EPSG:32633</CRS> <CRS>EPSG:32634</CRS> <CRS>EPSG:32635</CRS> <CRS>EPSG:32636</CRS> <CRS>EPSG:25832</CRS> <CRS>EPSG:25833</CRS> <CRS>EPSG:25834</CRS> <CRS>EPSG:25835</CRS> <CRS>EPSG:25836</CRS> ... View more

As far as I know, you can't choose a output pixel depth when using most geoprocessing tools. There are some exceptions, for example the Copy Raster tool. The pixel depth (8 bit\16 bit etc.) and type (integer\floating etc.) can however be changed automatically by a tool. This is discussed for example on this page:  For certain tools, the type of the output is determined by the types of all of the inputs. For example, if the tool takes several input rasters, and all of them are integer save for one that is floating point, the output raster would be floating point. When the output is floating point, fewer of the raster storage environments may be supported. And if you add NoData to an existing raster it can also change the pixel depth: Link Accordingly, when NoData is added to a raster that already has a full bit range (meaning that there is at least one cell in the raster extent occupying all the values in the bit range, for example, when 0 to 255 are all represented), it is promoted to the next higher bit depth. For example, a hillshade grid with cell values of 0 to 255 (which would otherwise fit within the 8 bit range), that also contains some NoData cells, is represented as unsigned 16 bit. If you choose to change a rasters bit depth then it can lead to loss of precision (going to integer from floating or unsigned to signed for example). There may be other issues as well. Hope that helped! ... View more

Hi John, that tutorial is out of date now. Esri now provide a very easy installer at this site: https://github.com/Esri/deep-learning-frameworks  If you do want to clone environments and do a Conda install that site also has the latest instructions.   ... View more

If it is the stretch causing the colour change, then instead of the Colormap to RGB transform you can add a Stretch transform to the mosaic dataset and set the Stretch Type to None. ... View more

You could try adding a raster function to your mosaic dataset. In catalog right click on the mosaic dataset and choose Edit Mosaic Dataset Functions. Open the Raster Functions pane by clicking on Raster Functions in the Imagery tab. Find the Colormap to RGB function under Conversions and drag it into the editor. Link up the functions and then click Validate and Apply. I don't have any colormap image files to test this on but in theory it should work! ... View more

I think those original images might be using a colormap. Can you check the properties of them under Source - Raster Information and find out what is under Number of Bands, Format, Pixel Type, Pixel Depth. Have you tried different output formats when creating the tiles - PNG8, JPEG etc.?  ... View more

Correct, that is a high point in the ground surface. If you want to intersect at 3 feet above ground level over a large area like that then you will have to look at creating a surface, then doing the intersect. This would involve a lot more work. Your building models look very simple and there doesn't seem to be be any real change in the outlines as you move up in z value. Just running the Multipatch Footprint tool might be sufficient by itself. What's the idea behind intersecting at 3 feet above ground? ... View more

Maybe try manually putting the transformation in? Save the map to a .mapx file. Open in text editor and look for the datumTransforms section. Should look something like the below when you have one.  Modify as required (the ____ parts), save, and Import Map into a new project. Does the ETRS89 to OSGB 1936 transform get added from the properties? Maybe put it in by itself before you export as a good starting point. "datumTransforms" : [ { "type" : "CIMDatumTransform", "forward" : true, "geoTransformation" : { "geoTransforms" : [ { "wkid" : ____, "latestWkid" : ____, "transformForward" : false, "name" : "____" }, { "wkid" : ____, "latestWkid" : ____, "transformForward" : true, "name" : "____" } ] } }, { "type" : "CIMDatumTransform", "forward" : false, "geoTransformation" : { "geoTransforms" : [ { "wkid" : ____, "latestWkid" : ____, "transformForward" : false, "name" : "____" }, { "wkid" : ____, "latestWkid" : ____, "transformForward" : true, "name" : "____" } ] } } ],   ... View more

After you project, why not write the projected data back over the original data source? Maybe delete the existing records, use Define Projection to the new projection then Append the new features. This should work for relationship classes in gdbs and relationships defined in MXD\APRX files. This may not work if ObjectID or GlobalID is being used as the relationship key however. ... View more