Latest Contributions by DuncanHornby

You need to look at the coordinate system of your datasets. If they are wgs84 then 0.05 refers to 0.05 decimal degrees which sounds like a sensible value. If your dataset is projected, for example in metres, the 0.05 is 0.05m so depending upon the extent of the layer that might be producing billions of cells which obvious is meaningless and not what you want. ... View more

If it really is one point and the label you want to display is information that does not exist in any part of any attribute then you can simply type the text as shown below. But this approach in my opinion is you being slack and that will only come back and bite you...  What happens if you want to share this data or some other might want to do some spatial processing with your data? Your label exists nowhere but in the layer in the project. I would create a new field and populate it with the text that will become the label. Then it is clear where the label is coming from and becomes useful information that you or others can take advantage of.   ... View more

I suspect there are several ways to resolve this and some clever SQL. But this is how I would do it. Firstly the table needs to be a file geodatabase table so you can add a new field. So If your data is in Excel then you need to export it. Add a new field, call it keep and set it to SHORT. The following logic takes advantage of the fact you have pre-sorted the data. Open field Calculate tool and apply the following to keep field. The code block is: count = 0 last = 0 def tag(month): global count,last if last == 0: # First row last = month count = 1 keep = 1 elif (month == last) and (count < 5): keep = 1 count += 1 elif (month == last) and (count >= 5): keep = 0 count += 1 elif (month != last): keep = 1 count = 1 last = month return keep Now run a simple select by attribute to select rows where keep = 1 Export selection to a new table. ... View more

Your model is using inline variable substitution as you have %Name% at the end of the raster dataset name. But nowhere in your model do you have a variable called Name with a value to substitute into. Add a text variable called Name to your model, fill it with simple text, e.g. water and the output raster will ultimate be called dp_water. ... View more

To add to Dales answer you probably want to export the data to make it permanent otherwise it only exists as temporary layer in the map. ... View more

A possible solution to this is to reclassify your rasters before you do the mosaic. You want to be reclassifying the VALUE field (this being the field that holds the pixel value) into the value you have in your CLASSVALUE field. So taking your P71 example  VALUE becomes 1 when it was 0, 2 when is was 1 and so for. I would do all this from backed up versions just in case you mess up the reclassify. Then when happy delete the backups.   ... View more

Looks like you have found a possible bug in Arcpro and how the different tools reconcile the relation Are Identical to. I would say you should edit your question and include the test data as a zip file for people to test to see if others can replicate the issue and discount if it is a hardware issue. ... View more

Want to bump this  up as recently I have found the need to reclassify range of pixel values into floats and was surprised to discover the reclassify tool only supports integer format as output. I have a work around but it would be good if the reclassify and reclassify by table accept floats as an output format. ... View more

I think may be an alternative approach to this idea that achieves the same end result is to continue allowing tools to export with metadata but have a tool (and a UI button) that clears the metadata to a default "nothing", as if you have just created the dataset for the first time.     ... View more

Anyone from the geoprocessing\python esri team have a solution to this? If you have a toolbox  (atbx) with dozens of embedded scripts how to do you en masse encrypt all scripts?  I'm regularly hitting this problem and in need of a solution. ... View more

Whilst ESRI ruminate on this idea, are you aware of whitebox tools? They have a tool that does exactly what you want RasterToVectorPolygons that will take a float raster. Its free and has been exposed as a geoprocessing toolbox which you can download here. You will be forced to accept it's limitations, for example it takes a tif as input and outputs shapefile, which are known to have size limitations.  I tested on a small section of a DEM which is float32   The result is: I tried it on a larger section of DEM and it seemed to lock up but that was probably me being impatient. You might find if you have to process large rasters your existing work flow whilst irritating may be the fastest approach?   ... View more

Seems alright to me. Remember a multi-value comes back as semi-colon separated, so first thing I tend to do split it into a list. You can add the following line to your execute function to get an idea of what is returned. arcpy.AddMessage(account_numbers.split(";")) ... View more

Your idea is unlikely to get traction. A float raster is typically some sort of surface where every pixel has a different value. Yes you might get areas where there are clusters of pixels with the same value but I would imagine that is an exception rather than a rule. So taking an elevation raster I have at hand it has 6558 cols by 12150 rows. That could very easily end up outputting a polygon dataset with 79,679,700 polygons!  Start messing around with lidar derived data and you could end up with billions of polygons.   ... View more