|
POST
|
ArcGIS Pro writes GPMessages and creates the ImportLog folder in the project’s Home folder (the Home folder is also where Pro stores other “managed” project items). If you ever changed the Home folder, Pro does not move existing managed items from the old Home folder to the new one—so you can end up with GPMessages/ImportLog “outside” the folder you’re currently expecting. This is documented behavior: the Home folder “contains… geoprocessing messages” and changing it “does not move or copy” items from the previous home folder. Change current settings for a project—ArcGIS Pro Your Default Toolbox is on Microsoft OneDrive. Esri cautions that cloud storage services such as OneDrive are not supported unless stated otherwise, which can contribute to inconsistent behavior when items are referenced from synced locations. Projects in ArcGIS Pro
... View more
4 hours ago
|
0
|
0
|
3
|
|
POST
|
What release of ArcGIS Pro are you using? I'm using 3.6.4 and following your instructions do not see this error message.
... View more
4 hours ago
|
0
|
1
|
78
|
|
POST
|
ArcGIS Pro 3.5 can add DWG/DXF content as GIS feature layers, but it does not import an AutoCAD paper space layout/title block as an ArcGIS Pro Layout while preserving CAD layout formatting (paper space, viewports, plot styles/CTB, etc.). In Pro, CAD drawings are treated as read-only feature datasets, not layout documents: CAD data as ArcGIS Pro layers—ArcGIS Pro | Documentation
... View more
5 hours ago
|
0
|
0
|
2
|
|
POST
|
@vlabrie - I see that you submitted an Esri Support ticket this week. Was the analyst able to resolve this item? Please advise.
... View more
8 hours ago
|
0
|
0
|
10
|
|
POST
|
This usually happens for one of two reasons in ArcGIS Pro: First, your line symbol needs Symbol layer drawing to keep segments “joined” and ordered at small scales. When you zoom out, Pro has to draw many more line features at once. If your symbology relies on multi-layer line symbols (for example, cased roads, stacked symbol layers, or effects that must connect across adjacent features), the appearance can change unless you explicitly control how symbol layers join/merge across features and their internal draw order. Try these steps: Select the line layer in Contents Go to Feature Layer tab > Drawing group > Symbology In the Symbology pane, open the Symbol layer drawing tab Turn on Enable symbol layer drawing Use Join or Join and Merge (and adjust symbol class order) to maintain connectivity and the intended drawing order across segments Or reason #2 - if it's mainly wrong in the exported PDF, it may be a vector viewing/anti-aliasing artifact. Some exports look “fragmented” or appear to change when you zoom in/out in a PDF viewer because the output is vector and the viewer re-renders strokes differently at different zoom levels. You could try some of the PDF presets on the Export Map dropdown menu and see if that helps...
... View more
8 hours ago
|
0
|
0
|
8
|
|
POST
|
This may be related to Microsoft Windows updates (notably KB5083769 and KB5082417 released in April 2026) introduce changes to file handling and SMB-related operations. Try uninstalling both of the forementioned Windows updates by going to your Systems->Windows Updates->Update History and click Uninstall Updates. Locate KB5083769 and/or KB5082417 and uninstall the updates. Restart your PC and try again. Hopefully this addresses this issue.
... View more
8 hours ago
|
0
|
1
|
22
|
|
POST
|
You’re hitting “Invalid search geometry” because your rule calls Intersects(hs, $feature) / Intersects(hs, buff) when the search geometry is sometimes null/empty/invalid (for example, the edited point has no shape yet, bad geometry, or a null geometry is being passed into Buffer()/Intersects()) Try these changes (key fixes: guard for null geometry, don’t call First() until you know there’s a result, and request only needed fields😞 // SAN POINTS QA/QC | UPDATE NETWORK ID
var f = $feature.Feat_Code
var o = $feature.Functn
var oid = $feature.OBJECTID
// ---- Guard: feature must have valid geometry ----
var g = Geometry($feature)
if (g == null || IsEmpty(g)) {
return null // or return $feature.NetworkID (whatever your target field is)
}
// HALF-SECTION
// Only request the field you need; keep geometry available for distance
var hs = FeatureSetByName($datastore, "HalfSection", ["HalfSec"], true)
// 1) Intersect with the feature geometry (not the feature object)
var interFS = Intersects(hs, g)
// Container checking prevents First() on an empty set
var halfSec = null
if (!IsEmpty(interFS, true)) {
halfSec = First(interFS).HalfSec
} else {
// 2) Fallback: buffer search, but only if buffer succeeds
var buff = Buffer(g, 1000, "feet")
if (buff != null && !IsEmpty(buff)) {
var candidates = Intersects(hs, buff)
var nearestHS = null
var minDist = Infinity
for (var feat in candidates) {
var d = Distance(g, Geometry(feat))
if (d < minDist) {
minDist = d
nearestHS = feat
}
}
if (nearestHS != null) {
halfSec = nearestHS.HalfSec + "xy"
}
}
}
// ...continue with your decode() / network id logic...
return halfSec Notes relevant to your snippet: Use Intersects(hs, Geometry($feature)) (or g) rather than Intersects(hs, $feature) to avoid type/geometry ambiguity. First(Intersects(...)) is fine only after you’ve verified the FeatureSet isn’t empty (use IsEmpty(fs, true)). If some HalfSection polygons are invalid, you can also see this error; repairing geometry on the HalfSection feature class can help.
... View more
Friday
|
0
|
0
|
86
|
|
POST
|
In the ACS 5-year or Esri estimates, there is an enriched "Median Household Income" field. In ArcGIS Pro, I also went to the Catalog Pane, clicked the Portal tab, and then clicked the ArcGIS Online cloud. I then searched for "Median Household Income" and there were many results. I added the "Median Household Income 2025 - Esri Demographics" web map to ArcGIS Pro. It's very detailed. Further, there is an ACS Median Household Income (latest) feature layer that I added to the map as well. It does down the Census Tract level. Not sure how it corresponds to the AMI from HUD but it's a good source to consider.
... View more
Friday
|
0
|
0
|
164
|
|
POST
|
Your filter may not be excluding what you think (spaces vs NULLs). SHORTNAME IS NOT NULL only excludes NULL values. It will not exclude empty spaces or strings that are just spaces. NAME <> ' ' excludes exactly one space and will still allow an empty string, two spaces, etc. So your source features can still pass the filter and then append blank/NULL values into the target, overwriting existing values. Try filtering with something that excludes both NULL and "blank-ish" strings. For example: SHORTNAME IS NOT NULL AND TRIM(SHORTNAME) <> '' or NAME IS NOT NULL AND TRIM (NAME) <> '' There is a BUG-000157944 for ArcGIS Pro that was fixed at 3.7 that may be related as well.
... View more
Friday
|
1
|
3
|
164
|
|
POST
|
If the layer you’re publishing/overwriting from in Pro is a service layer (hosted feature layer / feature service / map service), that’s very likely the cause of the 003999 at Upload Service Definition. Overwrite is designed to replace a web layer based on its source dataset (file/enterprise geodatabase, etc.). When the “source” is already a service, Pro often can’t stage a valid SD to overwrite, and you end up with generic server-side failures like 003999. Best practice is to make the source a real dataset, not a service Use a FGDB or enterprise geodatabase feature class as the authoritative source in the map. Publish/overwrite the hosted feature layer from that dataset. This is the most reliable “push updates to Field Maps” pattern.
... View more
a week ago
|
0
|
0
|
51
|
|
POST
|
This was answered in the ArcGIS Pro SDK community referenced here - Solved: How to add property sheet to layer's properties wi... - Esri Community (your question)
... View more
a week ago
|
0
|
0
|
39
|
|
POST
|
This line is the problem: df = DataFrame(columns=['Shape X', 'Shape Y']) It replaces df (the CSV you read) with a new a new DataFrame that only has those two columns. Try these changes: # Pandas section ------ df = pd.read_csv(parameters[1].valueAsText) # remove spaces from ALL column names df.columns = df.columns.str.replace(" ", "", regex=False) # write back to the same output CSV df.to_csv(parameters[1].valueAsText, index=False)
... View more
a week ago
|
0
|
0
|
156
|
|
POST
|
In your Python script, do you have a line that says: pdf.includeAccessibilityTags = True IncludeAccessibilityTags Property—ArcGIS Pro - it defaults to FALSE so perhaps this is why you're not seeing the tags? Also - another workflow - Solved: Automatically add PDF metadata for accessibility a... - Esri Community
... View more
a week ago
|
0
|
1
|
52
|
|
POST
|
Here's some information I learned from reviewing other cases: That message is coming from the Python Raster Function / deep learning model code (fastai/PyTorch), and it indicates your model (or the raster function calling it) passed an input with the wrong shape into an affine/warping step: ValueError: not enough values to unpack (expected 4, got 3) at fastai.vision.image._affine_grid means the code expected a 4D tensor size (N, C, H, W) (batch, channels, height, width) but received only 3 values (typically (C, H, W) or (H, W, C)), so it can’t proceed. The trailing message “Python Raster Function's .vectorize() method returned nothing” means the raster function’s vectorization step produced no features (often because inference failed earlier due to the shape error, or because the result was empty), so the geoprocessing tool can’t generate an output feature class/table. If this happened while running Detect Objects Using Deep Learning / similar deep learning tools in ArcGIS Pro 3.5.x, there is a related known issue where vectorization fails after the python raster function step: BUG-000182421 for ArcGIS Pro
... View more
a week ago
|
0
|
0
|
41
|
|
POST
|
Here's what I learned from studying the internals: "Those dropdowns are part of ArcGIS Pro’s tool UI, not part of what a geoprocessing service can describe to clients. When you publish Focal Statistics to ArcGIS Server/Enterprise as a web tool, the service exposes parameters through the REST “GP” interface using supported server-side parameter data types. During publishing, some Pro parameter types (or composite/specialized UI controls) may be converted to simpler types (often a string), and the service metadata does not include Pro’s neighborhood “chooser” definitions—so the Server “Geoprocessing Service Directory” (and many clients) can only show a basic input box, not Pro-style dropdowns/widgets. Esri notes this generally as: some parameter data types are not supported in geoprocessing services and can be dropped or become GPString after publishing; you can verify what your parameter became by checking the task’s REST endpoint (“Task Information”). Input and output parameters—ArcGIS Pro If you want dropdown behavior for the service, you typically implement it in the client UI (web app or custom Pro add-in) and pass the correctly formatted neighborhood value to the service." Hope this helps!
... View more
a week ago
|
0
|
0
|
49
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | Friday | |
| 1 | 2 weeks ago | |
| 1 | a week ago | |
| 1 | a week ago | |
| 1 | a week ago |
| Online Status |
Online
|
| Date Last Visited |
9 hours ago
|