|
IDEA
|
Thank you @BojanŠavrič ! This answers the question and has helped me get the ah-ha moment! This will definitely help us prepare for our future CSRS and NATFR2022 adventures.
... View more
02-11-2026
06:11 AM
|
0
|
0
|
259
|
|
IDEA
|
@BojanŠavrič , we really appreciate this update for Canada! We reviewed the Geographic Transformation documentation, and it mentions that NAD83v80vg is being used for all the CSRS transformations (v3 to v6; v3 to v7; v3 to v8). We also tested and it does give the same coordinates when transforming to v6/7/8 (and matches documentation). The Esri Coordinate system installer does install three NTV2 velocity files for NAD83v80VG, and NAD83v70VG, and NAD83v6VG files. However, only v80vg is in use. This means transforming from v3 to v6/7/8 gives the same results. When we use the full desktop NRCan TRX tool (not the web version), it can use the 3 different velocity grids (same 2010 epoch). This creates a bit of a variation b/w the software outputs (however v3 to v8 is the same in both software since both using v80vg). We can see the difference in v6vg, v70vg, and v80vg is extremely small, but since they are all included with the Coordinate System installer, wondering why v60vg and v70vg aren't being used for the v6 and v7 transformations? Should the target frame match the velocity grid (v7 using v70vg)? or better to always use latest velocity grid? Otherwise, aren't they all just v8 with v6 or v7 labels? "There is no spoon"? Sorry if I'm misusing some terms here and appreciate any feedback you may have. PS. If not mentioned lately, thank you to you and your fellow creators for Equal Earth PCS!
... View more
02-10-2026
11:07 AM
|
0
|
0
|
283
|
|
POST
|
Thank you @JMutunga , It was set to Single Workspace. I switched it and it confirm it works. Although no thanks to the error message. ArcMap was single WS and it still worked since you could only edit the parent in the join - but as now confirmed, Pro doesn't work in the same way. Agree that the messaging leads one to think there is something else wrong and not related to the WS config (see error image). Still a bug IMHO, but on the messaging side of things and already a logged issue. Although hard to know if related since there are no bug details. @DenisLalonde , appreciated your reply as well, and for sharing the related bug report! Next time we cross paths in Ontario, I owe you a pint! Josphat, you can join too if up you come up north!
... View more
05-28-2025
01:15 PM
|
1
|
0
|
1638
|
|
POST
|
Thank you @JMutunga, Hopefully we can update soon and glad this is solved at 3.4x.
... View more
05-28-2025
12:48 PM
|
0
|
0
|
1098
|
|
POST
|
Hi @Robert_LeClair , thank you for taking the time to review. I did a few updated tests and it still doesn't work (3.3.2 and 3.3.5), sadly I can't test in 3.5.0 at the moment. I made a copy of the FC into the fileGDB and it worked. I tried the join with keep-all and just matching and also made a copy of FC without archiving and no attachments in SQL Server - which the error still occurs. This is a 10.8.1 eGDB in SQL Server. So could be related to Pro version, or combo with eGDB version/db. I will see if I can get a 3.5.0 Pro setup to test as well and hopefully have some success. I'll keep this open for the time being, but good to know it doesn't happen in all scenarios.
... View more
05-28-2025
07:58 AM
|
0
|
0
|
1668
|
|
POST
|
We have a Feature class in the project default fileGDB, we enabled "start/stop" edit mode in Pro 3.3.5. The issue is as follows for Calculate Geometry: If we start editing > open the table > r-click on a field and run "Calculate Geometry": Once complete, both Save and Discard buttons are still greyed out. When you click to stop editing, you aren't asked to save edits, and all Calculate Geometry edits are lost. The only workaround is to do a manual edit afterwards, then save. If we start editing > open the table > r-click on a field and run "Calculate Field": Once complete both the Save and Discard buttons are enabled. Works as expected. Assuming a bug and a trigger of some type just isn't running in this specific scenario. Others notice this issue as well?
... View more
05-27-2025
08:54 AM
|
0
|
2
|
1256
|
|
POST
|
We have a point layer in SDE/SQL Server, archiving enabled, not versioned. We enabled "start/stop" edit mode in Pro 3.3.5. We can edit the FC directly without issue. But when we join the FC to a table in a fileGDB by ObjectID, the join works fine, but we can't edit the source FC. One of two scenarios will happen: Start the edit session but the layer isn't editable; or Try to start editing but get an error saying we can't edit the FC since not versioned. We flip to ArcMap, and it works as expected, we can edit attributes without issue. Not a great workaround as we are hoping to remove it soon. Anyone else encounter this or have a tip around it from Pro?
... View more
05-27-2025
08:00 AM
|
0
|
7
|
1779
|
|
POST
|
We've been using the Search Widget with the geocode.arcgis.com address search for many years now (it's the default). Pretty stable overall, but over the past few months we've noticed it is struggling to find accurate results for rural areas, which were successfully found in the past. Addresses that were historically point level address matches, are now only returning a street level match. This is happening in many cities in southern Ontario, Canada. We realize it changes a bit over time, but we don't usually have a downward trend and less accurate results. Some random ones still work, but many that worked 6 months ago are no longer getting the same level returned. Has there been a removal of existing address points? Are others noticing this change? We are using the default widget URL source: geocode.arcgis.com. These searches are in Ontario Canada (Waterloo, Cambridge, Wellington County, and surrounding areas). We limit the search widget with an extent to southern Ontario as well. Example address: "4889 Townline RD, Puslinch, ON." Address is verified from County GIS website parcel and did work in the past. We would historically also find this with "4889 Townline RD, Cambridge, ON." as well (and how Google finds it).
... View more
05-27-2025
07:51 AM
|
0
|
0
|
392
|
|
POST
|
Hi @JoeBessette , Thank you for posting this information. Could you elaborate on what other types of refactoring were required? I'll try to find an old git commit I can also test this on.
... View more
02-04-2025
12:57 PM
|
0
|
1
|
3280
|
|
POST
|
Hi @EirikH , Sadly didn't find an easy solution. I'm still using Vite but had to change Esri JS from ESM to AMD, then everything worked. I'm still using ESM imports for everything else, just not the Esri bits. It would be too much work to switch to newer @arcgis/core components at this point since it is a decent sized app. ESM with 4.27 still works, but not 4.28 (for this specific issue). AMD works with both 4.27 and 4.28, and we needed a fix that was in 4.28. I haven't tested on the newer 4.31 yet, but did notice it's the last release for the AMD npm packages. Webkit is a PITA for compatibility and testing so AMD for now but hoping ESM will be more successful in the future.
... View more
01-07-2025
06:32 AM
|
1
|
0
|
3408
|
|
POST
|
Hi @KrzysztofMroczek , did you ever find a solution to this? This just started happening to us recently as well. Any thoughts are appreciated. JS API 4.28 and issue is recent and in Edge/Chrome, but not FF.
... View more
09-26-2024
07:39 AM
|
0
|
0
|
960
|
|
POST
|
On my install it changes HKCU. Not sure if since I had opened software before (as there also settings in HKLM), but the Current user did the trick for me.
... View more
09-24-2024
09:55 AM
|
0
|
0
|
1536
|
|
POST
|
If you change using the GUI you can see that it changes "SOFTWARE_CLASS_FN" and not SOFTWARE_CLASS. Although maybe changing both is best just in case?! Hope this helps.
... View more
09-23-2024
11:14 AM
|
0
|
0
|
1557
|
|
POST
|
We've been using the admin settings available in the Pro.settingsConfig file and have run into some conflicting information with the help/sample, and XSD. The overview help for these settings provides a sample of settings but also states "This sample does not include all available application settings and properties". There is a link to the complete list as well. However, if we open the ProSettings.xsd in the Pro installation folder, the list is different. Some settings are in the XSD, but not listed in the complete list: Examples are both "WarnOnSubtypeChange" and "StretchVertices" in the XSD Editing Section (16 edit settings in XSD and only 12 in document list). Some settings are in the "complete list" but not in XSD: The entire "<Report>", "<Authentication>" and "<ShareDownload>" element sections. Oh, I should ask a question.... is there a complete, complete list? Will all settings work if not in one location or the other, or possibility of removed meaning it is deprecated? A secret handshake to get the full list? The list has been different for a while and just updated to 3.3.2 and checked that these are still conflicting. Or maybe this post will lead to an update of the XSD and help 🙂 Tagging @KoryKramer and @GIS_Weasel as from previous threads you both have some history working the the Pro.settingsConfig file too and always appreciate your insight.
... View more
09-20-2024
06:58 AM
|
0
|
1
|
1037
|
|
POST
|
Hi @JakubPruchnik, Could you expand on the proper order - Do you mean the same order as the XDS file? as you would see in the GUI?
... View more
09-20-2024
06:13 AM
|
0
|
0
|
1631
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 05-28-2025 01:15 PM | |
| 1 | 01-07-2025 06:32 AM | |
| 1 | 09-06-2024 09:59 AM | |
| 1 | 07-09-2024 12:04 PM | |
| 2 | 05-16-2024 05:32 AM |
| Online Status |
Offline
|
| Date Last Visited |
02-11-2026
05:38 AM
|