|
POST
|
Open a case with Esri Support, likely a regression defect in Pro 3.2. I can replicate this issue with a new/clean 11.2 enterprise geodatabase on SQL Server 2022 and Pro 3.2. Using SQL Profiler, the SQL being passed to SQL Server is good and doesn't generate any errors or warnings, so this seems to be an internal Pro issue.
... View more
12-31-2023
02:15 PM
|
1
|
3
|
5640
|
|
POST
|
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
12-28-2023
12:51 PM
|
0
|
1
|
2334
|
|
POST
|
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
12-28-2023
09:25 AM
|
1
|
3
|
2341
|
|
POST
|
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
12-28-2023
07:23 AM
|
1
|
3
|
2785
|
|
POST
|
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
12-26-2023
09:15 AM
|
0
|
0
|
2800
|
|
POST
|
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
12-26-2023
09:10 AM
|
1
|
0
|
850
|
|
POST
|
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
12-19-2023
12:58 PM
|
1
|
0
|
4179
|
|
POST
|
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
12-19-2023
12:03 PM
|
1
|
0
|
1936
|
|
POST
|
Looks to be some issues with upgrading from 2023.2 to 2023.3: Monitor 2023.3 database connection
... View more
12-18-2023
08:18 AM
|
0
|
1
|
2551
|
|
POST
|
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
12-18-2023
07:22 AM
|
0
|
0
|
2081
|
|
POST
|
Are you asking how to taking a number like 0.123 (12.3%) and make it 12.3? If so, just multiply the current value by 100; otherwise, I am not sure what you are asking. The numeric field will never store the percent sign, that is simply a formatting option in a table view. If you want a percent sign with the actual data, you will have to use a string field.
... View more
12-18-2023
07:06 AM
|
1
|
2
|
2028
|
|
POST
|
It helps to provide information about data types and an example or two.
... View more
12-12-2023
05:57 AM
|
0
|
1
|
2755
|
|
POST
|
The vast majority of the patches to .NET 6.0.x are security patches, so it is strongly recommended to always run the latest version. In your case, I suspect it wasn't .NET 6.0.5 specifically that resolved the issue but more uninstalling and re-installing .NET 6.0.x that fixed any issues where .NET 8.0.x and previous .NET 6.0.x settings may have been conflicting.
... View more
12-02-2023
12:31 PM
|
0
|
2
|
5492
|
|
POST
|
Although a regular expression answer has been put forward, I believe there is a more straightforward regular expression than what has been already proposed. Also, all that is needed in terms of cursors is a single pass through the data set with an update cursor. First, the regular expression. You are trying to match pairs of species-values that have been concatenated into a single string, so there are 3 things to differentiate: 1) a species-value pair, 2) the species within that pair, and 3) the numeric value for the species in that pair. The following regular expression captures that logic: >>> import re
>>>
>>> reg_exp = "(?:([A-Za-z]+)\s*([0-9]+))+?"
>>>
>>> SPCOMP_samples = [
... "Pj 60Sb 40",
... "Pj 60Sb 40",
... "Sb 80Pj 10La 10",
... "Pj 60Sb 40",
... "Pj 80Sb 10Pt 10",
... "Pj 80Sb 10Pt 10"
... ]
>>>
>>> for sample in SPCOMP_samples:
... re.findall(reg_exp, sample)
...
[('Pj', '60'), ('Sb', '40')]
[('Pj', '60'), ('Sb', '40')]
[('Sb', '80'), ('Pj', '10'), ('La', '10')]
[('Pj', '60'), ('Sb', '40')]
[('Pj', '80'), ('Sb', '10'), ('Pt', '10')]
[('Pj', '80'), ('Sb', '10'), ('Pt', '10')]
>>> The regular expression uses a non-capturing outer group to find the species-value pairs, and then uses two internal capturing groups to differentiate the species from the numeric value. Using the expression with re.findall returns a list of tuples containing a species and a numeric value. Since each tuple contains the species and the value, you can use the species to look up the index of the species field in a cursor and update that field with the value. # Note: Code below hasn't been tested
reg_exp = "(?:([A-Za-z]+)\s*([0-9]+))+?"
fc = # path to feature class or shape file
with arcpy.da.UpdateCursor(fc, "*") as cur:
spcomp_idx = cur.fields.index("SPCOMP")
for row in cur:
for species, value in re.findall(reg_exp, row[spcomp_idx]):
species_idx = cur.fields.index(species.upper())
row[species_idx] = value
cur.updateRow(row)
... View more
12-02-2023
12:17 PM
|
2
|
3
|
7933
|
|
POST
|
Although ArcGIS Pro itself doesn't support a standardized regular expression implementation across all data sources, nearly all data sources do support a flavor of it. Without knowing the workspace or data source type, e.g., file geodatabase, mobile geodatabase, etc...., I can't offer any more specifics.
... View more
12-01-2023
07:17 AM
|
1
|
0
|
3467
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Friday | |
| 2 | 2 weeks ago | |
| 1 | 2 weeks ago | |
| 2 | 06-05-2026 10:30 AM | |
| 1 | 05-29-2026 08:22 AM |
| Online Status |
Online
|
| Date Last Visited |
yesterday
|