Latest Contributions by RPGIS

Hi @Ed_ , Try the solution below. My assumption is you it may be something to do with the layer name but it is hard to say what the issue is. // Store the layer as a variable var layer = FeatureSetByName($map, "sf") // Filter the attribute value and count values var FilterField = "attribute1" var FilterValue = 'YES' var YesCount = Count( Filter( layer , FilterField + ' = @FilterValue' ) ) // If the current feature's attribute is "Yes", add 1 to the count iif ($feature.attribute1 == "Yes" , yesCount + 1 , null )  Also, is your problem similar to the one found on stack overflow. Because if it is, then that would help anyone else here point you in the right direction. Similar sounding issue  ... View more

Hi @GretaFerloni  Python would be your best bet for this. Here are a few sources to help you along with that. Create a new project Create a new folder  ... View more

Hi @cat206  If you are using a python script then simply add a field that you can populate with the arcade expression and use that instead. I have used that method before. ... View more

Hi @cat206, GetFeatureSetInfo(GetFeatureSet($feature)).layerName does not need the GetFeatureSet. Simply having the $feature or using $featureset will do the trick. The other thing is, have you tried using console to see what it prints out because it should return the layer name only. If there are characters in the name that you don't want, then you can simply use split text function, which returns an array, and then select the first index of that array to get the name. ... View more

Hi @jacob_loughridge  Just to give you another tip about coding, especially in GIS, it is best to reduce using gp tools in a script or mid script since those create other features that then need to be utilized, which further complicates scripts. The one cool thing about the geometry methods in arcpy is you can also project features to different projections using projectAs (spatial_reference, {transformation_name}) geometry method.  ... View more

It could be it is having trouble reading the geometry of the line feature; depending on if you are using shapefiles vs featureclasses. It is generally recommended to avoid using shapefiles and use featureclasses in filegeodatabases since shapefiles are notorious for getting corrupted. Another option is to read through all of the segments and all of the points in the segments to find the closest point. Read through the line feature class to see if any shape value return. If there is a corrupted record, it will return as a null value. ... View more

Yes. It basically utilizes the geometry of the feature and runs an analysis using the arcpy geometry methods. I have made recommendations to people to avoid using selections in a script and simply utilize the capabilities of the cursors. The cursors themselves will accomplish any gis related task. ... View more

I rewrote your script as such because it was really difficult to read and identify where the issue was. Have you checked out the link in my previous post? It shows you how to utilize the geometry of a feature. The line of code you are trying to use, are you merely copy and paying it into your script or are you running the sample that I provided.  ... View more

So, there are a couple of things to mention, not so much the question but issues that I see with the script itself. Avoid nesting loops. In terms of performance, nested loops can be processing killers if they are used within themselves. All cursor functions have SQL clauses that can be used, so having separate select by attribute query layer is unnecessary. In my personal opinion, never set functions within the main portion of a script. I typically set them above the main processes and below the imports.  I would also recommend checking out arcpy geometry to get a better understanding of how to utilize feature geometries.   import arcpy from arcpy import ListFields from arcpy.da import SearchCursor as Searching , UpdateCursor as Updating # Retrieves records of an input layer/feature and returns a dictionary of values def GetRecords( Layer , ["OID@"] + Fields + ['SHAPE@'] , SQLClause ): SearchLayer = Searching( Layer , Fields ) if SQLClause is not None: SearchLayer = Searching( Layer , Fields , SQLClause ) return { row[0] : row[ 1:] for row in SearchLayer } # Returns a list of field names def GetFieldNames( Layer , ExcludeFields ): fieldnames = [ field.name for field in ListFields( Layer ) ] if type( ExcludeFields ) is list: fieldnames = list( set( fieldnames ).difference( set( ExcludeFields ) ) ) return fieldnames # Checks the distance between two geometries def CheckProximity( InputFeatureRecords , DistanceFeatureRecords , SetDistance ): WithinSetLimits = { } for IF_id , IF_Attributes in InputFeatureRecords.items(): for DF_id , DF_Attributes in DistanceFeatureRecords.items(): Point = IF_Attributes[ 0 ] Line = DF_Attributes[ 0 ] if Point.distanceTo( Line ) <= SetDistance: WithinSetLimits[ IF_id ] = DF_Attributes[ 0 ] else: WithinSetLimits[ IF_id ] = "Not Within 100 Feet of Stream or River" return WithinSetLimits Poles = '<PoleLayer>' Streams = '<StreamLayer>' PoleFields = GetFieldNames( infeature , '<[ list of field names to exclude ]>' ) StreamFields = [ "Stream_ID" , "StreamPermanence" ] PoleRecords = GetRecords( infeature , ["OID@"] + Fields + ['SHAPE@'] ) StreamRecords = GetRecords( infeature , ["OID@"] + Fields + ['SHAPE@'] ) CheckProximity( PoleRecords , StreamRecords , 100 )   The sample above isn't a solution but I just thought to provide something useful to give you a rough idea. ... View more

Here is what I have used in the past.   import arcgis.gis from arcgis.gis import GIS from arcgis.features import FeatureLayer import datetime import os gis = GIS('<Portal>',"<Username>", "<Password>") #print("Logged into AGOL...") source_outages_layer_item = gis.content.get("<itemID>") #Outages layer source_layer = source_outages_layer_item.layers[0] #print (source_layer) Current = datetime.datetime.now() #print (Current) source_layer.calculate(where = "1=1", calc_expression={"field": "Now", "sqlExpression" : "CURRENT_TIMESTAMP()"}) # Update The Outage Status source_layer.calculate(where = "Now > TimeField and Now < TimeField", calc_expression={"field": "fieldname", "sqlExpression" : "<Some Value {must match field data type }>"}) source_layer.calculate(where = "Now < TimeField", calc_expression={"field": "fieldname", "sqlExpression" : '<Some Value {must match field data type }>' }) source_layer.calculate(where = "Now > TimeField", calc_expression={"field": "v", "sqlExpression" : '<Some Value {must match field data type }>'}) # Update The Emergency Outage Timeframe source_layer.calculate(where = 'SQL Clause', calc_expression={"field": "fieldname", "sqlExpression" : "Expression"}) #______________________Write Text File_____________________# output_location = 'file location' TxtFileName = ("PythonScriptLog.txt") TxtFile_Output = os.path.join(output_location, TxtFileName) f = open(TxtFile_Output, "w") f.write(str(Current) + '\n' + '\n' + 'Successfully logged into AGO' + '\n' + 'Updated ' + 'Featureclass Name') f.close()   Something that I also realized later on is that you can also treat the feature service like any feature if you use the full url and have editing capabilities on the feature.   ... View more

That is what your issue is. If you are looking for a perfected grid, then the grid to index is your best option. Otherwise, the subdivide polygon is the only tool that would get your polygon to divide as proportionately as possible. ... View more