Latest Contributions by KimOllivier

But there is another  problem not covered by my workaround. OBJECTID can be 32 or 64 bit as well. This is much harder to change and even detect. The type is "ÓID" for both (not helpful) but you can find out the length is 4 or 8. If the table is empty you can edit the field schema by hand to fix it, but I don't know how to do it in a script. ... View more

You may need to fix a bug(?) that adds a blank field to the end of the arcpy.ListFields(fc) command. fields = arcpy.ListFields(input_fc) print(f"L42 {[f.name for f in fields]}") for field in fields: if field.type not in ('OID', 'Geometry'): # not allowed in fieldmappings if field.name: # very strange blank name added to list by Esri field_map = arcpy.FieldMap() # new for each field print(f"L46 {input_fc},<{field.name}>") ... View more

We handle this by having a point layer of labels that relate back to the polygons. There is only one point for each property, but some properties are multipart. That doesn't matter because they still have a total area. You only get one label so it is placed in the largest part. You add labels when they have been exploded and then choose the largest one. Run a summary by max area and then select the largest, discarding the others. If you want to get rid of the non-boundaries there is an aggregate tool. ... View more

There are two obvious tools to create a set of index sheets based on the centroids. Do you have a sheet size in mind? Thanks for the sample that makes it much easier to experiment. The first thing I did was to project the data to a filegeodatabase so that I have feet units. My first attempt was to just create Thiessen polygons around the points. This works well for even spacing. There are a few long bits around the edges. You could trim them up and straighten the fuzzy bits by snapping to the larger index.   I then tried a Graphic Buffer with a size of 290 metres. This also gave a good start, a bit of integration would snap the overlaps to a tidy grid.   ... View more

Even if the policy is correctly set for casting the ambiguous Integer type I still need a solution that works for me. I can see that computing has evolved from 16 to 32 to 64 bit integers and some are defined as signed and unsigned. I have seen LONG, MEDINT, INTEGER and SHORT as well as the new BigInteger to try to extend the meaning of 'LONG' which in 32 bit days meant only 32 bits. To keep backward compatibility the temptation is to reuse 'Long' for 64 bit when using a 64 bit compiler. I was interested to see that MEDINT was interpreted as Long and INTEGER as BigInteger going from a gpkg to a filegeodatabase. So redefining the gpkg field type might be a good workaround that avoids having to explicitly cast the fieldtype using a fieldmappings parameter with ExportFeatures_conversion() replacing CopyFeatures(). [note that sqlite does not care what you call it in the DDL, they are always 64 bit integers internally] The small print in the help also explains why the option setting in Options in ArcGISPro does not work for me. Because if running a script outside ArcGISPro in the command line you have to set the options in the arcpy environment. arcpy.env. But Double is useless for me. I want to use the field as an indexed key so it has to be some sort of integer. Insert below: useCompatibleFieldTypes (Read and Write) Specifies whether field types that are compatible with ArcGIS Pro 3.1 will be used. This setting relates to the use of the Date Only, Time Only, Timestamp Offset, and Big Integer field types in CSV tables and unregistered database tables with tools that create layers or table views. When set to True, a layer or table view created from these sources will use field types compatible with ArcGIS Pro 3.1. Date Only, Time Only, and Timestamp Offset fields will be displayed as Date fields, and Big Integer fields will be displayed as Double fields. When set to False, all original data source field types will be used.   Note: This property is applicable when used from stand-alone Python or for a geoprocessing service. When used in ArcGIS Pro, this property will always match the Use field types that are compatible with ArcGIS Pro 3.1 and earlier releases when adding query layers and text files option.   A better option I have implemented is to replace CopyFeatures_management() with my own function CopyFeaturesLong() that looks for any BigInteger arcpy interpretations and keeps them as a compatible Integer, not a Double. Here it is if you want to use it. There will need to be a similar function to replace CopyRows().       def CopyFeaturesLong(input_fc, output_fc): """CopyFeatures replacement to ensure every BigInteger is mapped to Long with a fieldmappings parameter using arcpy.conversion.ExportFeatures() with a bit of help from copilot! full paths to featureclasses assumed """ # Create FieldMappings and FieldMap objects field_mappings = arcpy.FieldMappings() # List of fields to process # it would be nice if objectid and shape could be excluded easily fields = arcpy.ListFields(input_fc) for field in fields: if field.type not in ('OID', 'Geometry'): # not allowed in fieldmappings field_map = arcpy.FieldMap() # new for each field field_map.addInputField(input_fc, field.name) # Check if the field type is BigInteger and change to Long field_name = field_map.outputField if field_name.type == 'BigInteger': field_name.type = 'Long' field_map.outputField = field_name # Add the FieldMap to the FieldMappings object field_mappings.addFieldMap(field_map) # Use ExportFeatures to apply the field mappings and create the output feature class arcpy.conversion.ExportFeatures(input_fc, output_fc, field_mapping=field_mappings) if debug: for fld in arcpy.ListFields(output_fc): print(fld.name,fld.type) print(f"{output_fc} Feature class successfully exported with updated field types!") return True def CopyRowsLong(input_tab, output_tab): """CopyRows replacement to ensure every BigInteger is mapped to Long with a fieldmappings parameter using arcpy.conversion.ExportTable() with a bit of help from copilot! full paths to featureclasses assumed """ # Create FieldMappings and FieldMap objects field_mappings = arcpy.FieldMappings() # List of fields to process # it would be nice if objectid and shape could be excluded easily fields = arcpy.ListFields(input_tab) for field in fields: if field.type not in ('OID', 'Geometry'): # not allowed in fieldmappings field_map = arcpy.FieldMap() # new for each field field_map.addInputField(input_tab, field.name) # Check if the field type is BigInteger and change to Long field_name = field_map.outputField if field_name.type == 'BigInteger': field_name.type = 'Long' field_map.outputField = field_name # Add the FieldMap to the FieldMappings object field_mappings.addFieldMap(field_map) # Use ExportFeatures to apply the field mappings and create the output feature class arcpy.conversion.ExportTable(input_tab, output_tab, field_mapping=field_mappings) if debug: for fld in arcpy.ListFields(output_tab): print(fld.name,fld.type) print(f"{output_tab} Table class successfully exported with updated field types!") return True       ... View more

Correction: you cannot hide fields in Pro, they all have to be visible. ... View more

I am interested in your workflow. I do an identical task. I prototyped it in Pro and then moved it to a Notebook online. I could not use arcpy online, only arcgis so I found Pandas did help. If you get feedback that you don't have edit rights reported then I would take notice. I get this sort of thing, such as arcpy.Exists() not finding a file. Note that Esri has just completely revamped user roles, licencing, permissions. Have a look at the new system. Are you the owner of the FeatureLayers? ... View more

Still a problem for me at Sept 2024. Sort of works if you add a WFS source from the MapViewer, but not if you add it as a FeatureLayer. It ignores the layer dropdown list and just picks the first one. ... View more

The only way I have done this is by using the Python API and Pandas to find the maximum value and then update a field ... View more

"Not all Arcade functions are suitable for every profile. For example, profiles that execute expressions for all features in a layer (e.g. visualization and labeling) don't allow expressions to access data via FeatureSet functions." I don't think you are allowed to use Arcade in a map filter because of the overhead implied. You will have to process the highest value earlier before the data is in a MapView. ... View more

It can be done everywhere else! Dashboards can do it. Pro can do it. ArcView 3 could do it. There was a concept plugged by Esri as a 'join by shape field' that was intuitive and spacey.  What else is more fundamental in a GIS? There is a manual tool that does an Intersect to a new static Feature Layer that also costs a lot of credits, not good enough. ... View more

I appears that the field item is not recognised as numeric. I am also wrestling with WFS feeds being read only and intermittent. My idea is to copy the WFS feed to a real Feature Layer daily that you have full control over the schema and also filters. This is easy from Pro, but not ideal and not automated. So maybe a AGOL Notebook with a Task to refresh each night? I found Arcade is disabled for WFS layers so that is not an option. ... View more

If you put both feature layers into a FeatureLayerCollection then you can turn them both on or off together. ... View more