|
POST
|
I hate using the python window since it's design is so lame, opting rather to run all my python from Spyder.
... View more
12-18-2020
08:53 AM
|
0
|
2
|
2402
|
|
IDEA
|
Seems like there is an idea for this already. I agree, very frustrating.
... View more
12-18-2020
08:47 AM
|
0
|
0
|
7650
|
|
POST
|
I guess I missed the announcement; @KoryKramer would you care to comment on this? I run the Address Data Management Solution, so I won't be upgrading till that gets the green light.
... View more
12-17-2020
07:16 AM
|
0
|
0
|
4592
|
|
POST
|
It should not be too difficult... Hopefully You'll need to get familiar with Arcade; start with some basic concepts with rules and ramp up to more complex. I started out exactly opposite to that: In my first exposure to Attribute Rules, I tried to figure out some very complex rules within an ESRI Solution, and nearly lost my mind. (These days I'm wondering if there is anything left to lose...) This forum is especially helpful so don't be timid; post your questions as you encounter issues. I'm bringing @XanderBakker into this: without his advice and help I wouldn't be able to spell Attribute Rules or Arcade. Attribute Rules are very useful; I especially like using them in concert with Geodatabase Sequences. One caveat with using attribute rules is once they are deployed on a feature class, that feature class is unavailable to ArcMap users and/or users of ArcGIS Pro 2.0 and earlier.
... View more
12-16-2020
03:23 AM
|
1
|
0
|
4180
|
|
POST
|
I think I got things figured out; not sure why the above query didn't work out for me. Today, I worked on my python script such that it does not leave any <null> values behind. Now I just rematch the all the unmatched addresses rather than performing the selection at all. Seems to work just fine. My suspicion is that is one of those generic errors that gets picked up somewhere and has you chasing a red herring...
... View more
12-14-2020
02:19 PM
|
0
|
0
|
3729
|
|
POST
|
Also, in practice, it would behave like a custom Arcade expression to display dynamic (calculated) fields in Pop-Ups, but actually stored in the geodatabase... What you are describing is an attribute rule, and you should be able to create one that does what you want... See this post: https://community.esri.com/t5/developers-questions/how-can-i-get-x-y-in-dec-degrees-from-a-poly-feat-serv-using/td-p/72397
... View more
12-14-2020
11:35 AM
|
1
|
1
|
4210
|
|
POST
|
Date fields in Excel can be tricky sometimes and as @DanPatterson mentions if there are blank or null values in your spreadsheet things get even worse. See this post of mine from last year: https://community.esri.com/t5/arcgis-pro-questions/date-field-in-excel-to-table-tool/td-p/21251
... View more
12-14-2020
08:01 AM
|
0
|
1
|
3452
|
|
POST
|
Working with it some more, it is just a quarky weird error. I just got it again after adjusting all the Single Line Input Values and rematching a selected set of Status = U and Single Line Input Is Not Null. It threw the error, and I tried it again a moment later and it rematched beautifully. Can't explain it. If I can get it to work more often than not, I'll call it good...
... View more
12-11-2020
02:36 PM
|
0
|
0
|
3744
|
|
POST
|
ArcGIS Pro 2.6 I am encountering an odd error when rematching address in arcgis Pro. Unmatched addresses is nothing new for the data I'm working with, and to try and speed up the rematch process I edit the values in the Single Line Input field save the edits and rematch. Utah addresses are easy to fudge: if an address like 6349 W 7380 S misses, I run a little python script that rounds it to the nearest hundred so the Single Line Input value is 6300 W 7400 S. I have a POI role in my locator for those rounded values so that is a good match. The problem I'm encountering is it works to a point. I select a number of unmatched addresses, update the Single Line Input field and rematch. I can do that several times and then I get this error: JoeBorgione_0-1607719983805.png The locator and all the data I'm working with is all local and for that matter, I am signed into AGOL for my Pro License. It seems random; one time it'll error out with 120 records selected, other times with 50 records selected. I have a machine with Pro 2.5 on it and when all 500 + records are selected, they rematch just fine. If I manually click through the unmatched records with the green check in the rematch pane, I rematch all day long, but not in bulk. I have a big geocoding project coming up and I know there will be tons of bad addresses which is why I testing this approach now on smaller address tables. @BradNiemand
... View more
12-11-2020
01:01 PM
|
0
|
4
|
3752
|
|
POST
|
That's kind of a funky error by mentioning a proxy. You might be better off getting a hold of ESRI Tech Support for this one.
... View more
12-11-2020
07:17 AM
|
0
|
1
|
4048
|
|
POST
|
From the compact help page: JoeBorgione_0-1607616559628.png swap out the following in my code: #replace:
arcpy.CompressFileGeodatabaseData_management(fgdb)
#with
arcpy.Compact_management(fgdb) That should do the trick for you....
... View more
12-10-2020
08:12 AM
|
2
|
0
|
5143
|
|
POST
|
I'm pretty sure I've never compressed a fgdb. when I read about it in help page, I got the impression that it's a one and done operation. Compressing an Egdb is an ongoing maintenance operation and I've written and executed scripts for those.
... View more
12-10-2020
07:26 AM
|
0
|
0
|
5151
|
|
POST
|
It would not be a tough script to write; psuedo code might like look like this: import arcpy
arcpy.env.workpace = #directory of geodatabases
fgdbList = arcpy.ListWorkspaces("*", "FileGDB")
for fgdb in fgdbList:
arcpy.CompressFileGeodatabaseData_management(fgdb) The question I have though is what is the purpose of compressing a file geodatabase on a regular basis?
... View more
12-10-2020
07:14 AM
|
2
|
2
|
5154
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-11-2018 07:12 AM | |
| 1 | 05-17-2021 11:18 AM | |
| 1 | 06-29-2021 11:42 AM | |
| 1 | 07-05-2012 07:49 AM | |
| 1 | 09-03-2016 06:16 AM |
| Online Status |
Offline
|
| Date Last Visited |
05-19-2026
11:56 AM
|