Latest Contributions by XanderBakker

I wonder if the code is correct. Seems to me there are a few strange things going on. On the next line there are two brackets missing: b = sum(row[0] for row in arcpy.da.SearchCursor(fc, 'QUANTITY_SOLID'),DefQ) should probably be: b = sum([row[0] for row in arcpy.da.SearchCursor(fc, ('QUANTITY_SOLID'),DefQ)]) First to create a list of unique values in a field you can do that on a single line like this: # find the unique 'SEGMENT_LENGTH' values, maybe use SHAPE@LENGTH instead? lst_seglen = list(set([row[0] for row in arcpy.da.SearchCursor(fc, ('SEGMENT_LENGTH'))])) I would probably do it differently and use a dictionary to store the unique length vs the sum of the Quantity Solid. Next a simple update cursor to store the results. def f(fc):     dct = {}     flds = ('SEGMENT_LENGTH', 'QUANTITY_SOLID')     with arpy.da.SearchCursor(f, flds) as curs:         for row in curs:             if row[0] in dct:                 dct[row[0]] += row[1]             else:                 dct[row[0]] = row[1]     flds = ('SEGMENT_LENGTH', 'QUANTITY_SOLID_SUM')     with arcpy.da.UpdateCursor(fc, flds) as curs:         for row in curs:             if row[0] in dct:                 row[1] = dct[row[0]]             else:                 row[1] = 0 # should not occur             cursor.updateRow(row)   return fc It still sounds strange to look for unique segment lengths and sum values for each unique length. Normally you see this the other way (sum length for a unique value)... ... View more

I doubt that raster fields are supported in ArcGIS Online, but maybe  Bernie Szukalski‌ can enlighten us on this topic. In case they are not supported, you could use some Python code to extract the rasters and store them on a server (or even dropbox) and create hyperlinks for each feature. The site below explains shortly how to export the rasters to files. How to export your raster datasets referenced in a “raster” attribute field (file geodatabase) using Python. | Esri Aus…‌ Another option would be the use of attachments: Configure pop-ups—Help | ArcGIS‌ Kind regards, Xander ... View more

Hi Drew, The client which I am advising at this moment, is taking its first steps with ArcGIS Online. Due to the confidentiality and the nature of the data and the analysis they conduct they might switch to Portal for ArcGIS, next to their custom developed ArcGIS for Server applications. You're right, Portal and AGOL4O both have their place. Kind regards, Xander ... View more

I was just thinking, I don't need the 10.2.1 functionality to do this. It is also possible to something like this: # start insert cursor for output points with arcpy.da.InsertCursor(fc_out, flds_out) as curs_out:     # start search cursor on lines     with arcpy.da.SearchCursor(fc_in, flds_in) as curs:          for row in curs:             number = 0             polyline = row[0]             line_ID = row[1]             chainage = 0             for part in polyline:                 for pnt in part:                     number += 1                     if pnt:                         ptGeom = arcpy.PointGeometry(pnt, sr)                         if number > 1:                             chainage += ptGeom.distanceTo(prev_pnt)                         # chainage = polyline.measureOnLine(ptGeom)                         elevation = pnt.Z                         curs_out.insertRow((ptGeom, line_ID, number, elevation, chainage))                         prev_pnt = ptGeom It uses the distanceTo on the point geometry to sum the traveled distance on the line... Kind regards, Xander ... View more

With respect to the placement of the labels, an option would be to use the optional points created in the Fishnet tool to label the cells. Since the points describe the center of the cell, the would have to be moved. This can be done with the FieldCalculator: At the fishnet tool switch on the option "Create label points" In the resulting point featureclass add a text field (for instance "labels") Let's first move the points using the FieldCalculator. Calculate the Shape field as follows: The pre-logic script is: def TranslatePoint(pnt, x_shift, y_shift):     return arcpy.Point(pnt.firstPoint.X + x_shift, pnt.firstPoint.Y + y_shift) At the "Shape =" part enter the formula: TranslatePoint( !Shape! , -1 * half your cell size, +1 * half your cell size) This will move the point half the cell size to the left and half the cell size up to go to the upper left corner. The next step will be to fill the labels field with the text for the labels; calculate the "labels" field: The pre-logic script is: def GetCoord(pnt):     return "({0}, {1})".format(int(pnt.firstPoint.X), int(pnt.firstPoint.Y)) At the "labels =" part enter the formula: GetCoord( !Shape! ) This will create a text of "(Easting, Northing)". Use this field to label the points to get something like this: Kind regards, Xander ... View more

In that case the Fishnet would be the way to go. In the Fishnet dialog, specify your lower left corner (rounded coordinates, which should be multiples of the cell size) at "Fishnet Origin Coordinate". At "Y-axis coordinate" specify your upper left corner (I assume you don't have rotation) At Cell Size With and Height specify the size of your cell At Number of Rows specify the number of cells you want vertically and  at number of Columns specify the number of cells you want horizontally. Select polygons as output geometry. This creates featureclass of the cell polygons. Now labeling is a different aspect. The fishnet created (and optional labels) don't have any additional information on the cell coordinates.  However you can add this information through the FieldCalculator: Add a new text field Calculate the Field (right click on column header) Specify the following information: This will fill the newly added field with the text "(X value, Y value)". Labels the featureclass with this field. You can add an label expression to add additional text: "Upper left (E, N):" & vbnewline & [labels] This will create a label like: Upper left (E, N): (X value, Y value) The only point is, that the label will be centered in the cell. Kind regards, Xander ... View more

I'm glad it worked for you. Good luck! ... View more

Hi Paul, From your example I don't really understand the concept of a "financial year". To fill the EndDate columns with the value 31/21/2300 doesn't seem right, since polygons that expire before that date, but have an end date after the current processing date, are included too. It is possible to add the name and create a new column "OutputName" that holds the name and a date range. What is not very clear to me is this: For the first record in your Excel it seems that the current processing date is "31/03/1965". In the code I provided the first processing date will be "01/04/1962" which will create a name "Reserve A 01/04/1962 - 01/04/1962". For the next record it will include those polygons for which the start date is before or on the current processing date ("07/06/1965") and the end date is on or after the current date. This will include also the first record, creating an overlap in range and an OutputName "Reserve A 01/04/1962 - 07/06/1965" Since the first record in the sample shapefile has an end date of 31/21/2300 it will be included in all the features. Maybe you can explain a little more on what you are trying to achieve? ... View more

That's nice, I was't aware of this possibility. If the list get a little longer, you may want to consider using a dictionary, like this: def FindLabel([YourFieldName]):     dct = {1: "Bob Hope", 2: "Bob Costas", 3: "Bob Marley",           4: "Bobby Bowden", 5:"Bob the Clown"}     district = int([YourFieldName])     if district in dct:         return dct[district]     else:         return "<ITA>Unknow supervisor</ITA>" I used this on the feature ID (FID) field of a shapefile with values ranging from 0 to 7 and got this: ... View more

Hi Paul, I have included some Python code that created a new shapefile with the merged polygons. The attributes are still to be defined. In the code the processing date is assigned the the output date fields. Prerequisites: Create two new columns that hold the start and end date as date (not as text). You can do this by adding the fields "DateFrom" and "DateTo" as date fields Calculate the new fields and simply assign the field StartDate and EndDate to it The reason to do this is to simplify the syntax of the where clause used in the script. Configuration: Change line 6 to point to your input shapefile Change line 7 and 8 to hold the field names of the date fields (the newly added fields) Change line 11 to point to a shapefile that will be created The script will: Create an empty output shapefile Create a list of unique dates from the start date field Loop through each date and create an expression (see lines 29 - 31). It will select all polygons with a start date less than of equal to the current date and  where the end dates are after the current date On lines 35 - 42 the polygons that match the query will be merged into a single (multipart) polygon On line 46 the polygon is written to the output shapefile import arcpy, os from datetime import datetime arcpy.env.overwriteOutput = True # change path to datasource fc = r"D:\Xander\GeoNet\MergePolsDate\Reserves_copy.shp" fld_start = "DateFrom" # create date field and fill it with content of StartDate fld_end = "DateTo" # create date field and fill it with content of EndDate # output shape fc_out = r"D:\Xander\GeoNet\MergePolsDate\Reserves_merged.shp" # create empty output shapefile ws_path, fc_out_name = os.path.split(fc_out) arcpy.CreateFeatureclass_management(ws_path, fc_out_name,     "POLYGON", fc, "SAME_AS_TEMPLATE", "SAME_AS_TEMPLATE", fc) flds = ("SHAPE@", fld_start, fld_end) # create a unique list of dates from start date lst_dates = list(set([row[0] for row in arcpy.da.SearchCursor(fc, (fld_start))])) lst_dates.sort() # insert cursor to store features to new featureclass with arcpy.da.InsertCursor(fc_out, (flds)) as curs_out:     # loop through list of unique dates     for date in lst_dates:         # create an expression         expression = "{0} <= date '{2}' AND {1} >= date '{2}'".format(             arcpy.AddFieldDelimiters(fc, fld_start),             arcpy.AddFieldDelimiters(fc, fld_end), date)         i = 0         # create the searchcursor with the expression         with arcpy.da.SearchCursor(fc, flds, where_clause=expression) as curs:             for row in curs:                 pol = row[0]                 if i == 0:                     # first polygon is just the polygon"                     polygon = pol                 else:                     # next polygons are added with union                     polygon = polygon.union(pol)                 i += 1             # insert the feature into the output featureclass             # TODO: manage attributes             curs_out.insertRow((polygon, row[1], row[1])) In case of any doubts, just post a reply. Kind regards, Xander ... View more

ZIP the extract of your data (shapefile or FGBD), and use the "reply" option in this thread. In the editor in the upper right corner you will see a link "Use advanced editor", once in the advanced editor you will see in the lower right corner the possibility to attach a file. ... View more

There is a point I don't really get; when the end date of a record (current date you want to process) is not equal to 2300, BUT it is higher than the current date, should it be removed from the output? It seems more logic to me if for each unique date in the StartDate you use all the records for which the start date is before the current date and the end date is after the current date and use those records to create the polygon. Anyway, I would probably use some Python code to: create a unique sorted list of start dates create a layer through the select by attributes dissolve the polygons and create a new featureclass (or add it to an existing one if you want the new merged polygons to be stored in 1 featureclass) Then there is still the issue of what to do with the attributes of the records you're merging... If you're willing to post a piece of your data, I can have a look and see what code is needed. Kind regards, Xander ... View more