Latest Contributions by JoshuaBixby

When you say " 6,000+ piece dataset", do you mean the traillistsortpt list is 6,000+ items or the pt_tbl layer has 6,000+ records? ... View more

I only have time to comment on the SearchCursor structure, the current code can be condensed down to two lines: with arcpy.da.SearchCursor(pt_tbl, "NUM_SEC") as cursor2: traillistsortpt = sorted(set(row[0] for row in cursor2)) ... View more

As much as I agree Esri should release a .NET 6 and beyond version for the File Geodatabase API, I think Esri should be more "open" minded and simply release the specificiation.  Releasing the API instead of the specification was a low-bar attempt at being "open" in the first place. ... View more

I am guessing it is a Pro 3.2 issue since: 1) the SQL being passed to SQL Server seems to work fine, and 2) everything renders fine in Pro even with the notification something isn't being parsed correctly. ... View more

The root of a file geodatabase is a directory, and hardlinks aren't allowed on directories.  Hardlinking individual files between separate file geodatabases will definitely cause corruption of one or more of the geodatabases, it would be a matter of when and not if. If you have lots of duplicative geospatial data, it is better to change your workflows and practices to reduce the duplication than relying on filesystem-level functionality that is completely unaware of the filesystem structure of geospatial data. Storage isn't free, and it can definitely add up in cost if mindlessly wasted, but in general the price of strorage pales in comparison to the cost of collecting or deriving data. ... View more

Data de-duplication doesn't work like that, or else no one would use it with active storage volumes.  Data is only de-duped when it is truly duplicative.  If a file is changed and no longer has duplicative contents/data, then it is no longer de-duped.  Data de-duplication is more advanced than just hardlinking files.  If someone is only hardlinking files and saying they are doing data de-dupe, it is time to get a new IT person. ... View more

The two lengths you are looking at are not measuring the same "length."  Although Esri doesn't clearly state it, the behavior you are seeing can be explained by the Fields view in the ArcGIS Pro GUI displaying FieldDescription Class—ArcGIS Pro length while the ArcPy Field object is giving you Field Class—ArcGIS Pro length.  The FieldDescription Class length only applies to String and OID fields, so it shows nothing/empty for numeric data types, while the Field Class length applies to all fields. ... View more

You will likely get more responses if you take the time to type out the errors and traceback instead of using a screenshot. ... View more

You are more likely to get some responses if you take the time to type out the errors and some additional infromation in text instead of making people read a poor-quality screenshot. ... View more

This information shared here so far isn't really sufficient to dive into a deeper discussion of what may be going on with your systems and these tests.  There are so many details that matter and aren't provided yet.  For example, what exactly is the workspace for the Pro test?  Are the datasets in a memory workspace?  How big are the datasets and what spatial types are involved.  Is the data in the enterprise databases part of a geodatabase?  What about versioning of the data if part of an enterprise geodatabase?  If versioned, what does the state tree look like?  What exactly is the spatial SQL you are using, and how are you executing it against the database? Overall, spatial predicates are expensive on the database side compared to other operators and predicates because they are much more complex mathematically.  Do get an example of the complexity, check out jts/modules/core/src/main/java/org/locationtech/jts at master · locationtech/jts · GitHub to see the algorithms the JTS project uses to implement spatial operators. ... View more

Python has very robust string formatting you can use and it won't require a code block.  For the expression, try: "{:.0%}".format(!condicao!/!total!) ... View more

Looks to be some issues with upgrading from 2023.2 to 2023.3:  Monitor 2023.3 database connection ... View more

Specific support for SQL syntax and operators varies depending on the back-end data source.  Although Esri doesn't standardize some syntax and operators at the software level, anything beyond the most simple can vary depending on the data source, so it is always good to state what data source or workspace you are working with. ... View more