|
IDEA
|
Really hoping that the Pro SDK will soon support linq/lambda interfaces.
... View more
09-03-2020
01:53 PM
|
0
|
0
|
1677
|
|
IDEA
|
Really hoping that the Pro SDK will soon support linq/lambda interfaces.
... View more
09-03-2020
01:53 PM
|
0
|
0
|
1835
|
|
POST
|
Hi Rich, While I have you...in the Pro SDK is there a way to quickly select all desired attributes without using a cursor to iterate over features. I'm hoping there are some extension methods using lamda linq syntax: myFeatureclass.attributes.select(x=>x.name).toList() or something similar would be awesome. Thanks! Mike
... View more
09-03-2020
09:48 AM
|
0
|
1
|
2438
|
|
POST
|
Thanks Rich...my brain is still stuck on ArcObjects...didn't even think to directly reference the attribute name in the row cursor. BTW - I don't have any fields hidden at all...they are all defaulted as is when the Parcel Fabric was added via our Portal instance.
... View more
09-02-2020
10:25 AM
|
0
|
0
|
2438
|
|
POST
|
Hi All, I am trying to get a field index of a hosted Parcel Fabric featureclass in a mapview but it seems to be returning the 'wrong' index. I have the Fabric hosted on Portal so we are editing the branch-versioned feature service. When I call the typical methods to get the indexes: var Parcels = MapView.Active?.Map.GetLayersAsFlattenedList().FirstOrDefault(fl => fl.Name == "Fabric Tax Parcels") as FeatureLayer; int indx = Parcels.GetFeatureClass().GetDefinition().FindField("name"); or int indx = Parcels.GetTable().GetDefinition().FindField("name"); ...they both return 1. 1 is the correct index in the actual geodatabase featureclass, but in the mapview index 1 is GlobalId...so I'm getting globalid values returned rather than the desired 'name' field. I'm assuming this isn't specific to the Parcel Fabric rather to branch-versioned/hosted feature services but I'm just using that as my example. Any help would be great! Thanks Mike
... View more
09-02-2020
09:50 AM
|
0
|
4
|
2485
|
|
POST
|
I'm a bit confused on this one and hope someone can shed some light. When attempting to add a Pro Fabric to a new map I keep getting these errors on each feature class in the fabric: "Layer cannot be edited, please change the layer elevation units or the layer source vertical units to be the same." We reprojected our fabric from NAD 83 HARN Meters/NAVD US FT to NAD 83 2011 Intl Feet/NAVD US FT. When the fabric is added to a new map these errors show and the elevation units are all default set to Meters. Am I missing something? Shouldn't it be choosing the layer units automatically? Thanks! Mike
... View more
08-13-2020
03:23 PM
|
2
|
2
|
2192
|
|
IDEA
|
Reset Panes is helpful but it would be way better to add more functionality to the various tab groups in the view. Adding the standard web-browser-type things like 'Close All', 'Close Others', etc (like that mapping tabs have) to the non-mapping tab groups would be a much better improvement. This would also be enhanced if each group of tabs, depending on where they are docked, have separated closing behaviors. Mike
... View more
08-12-2020
10:16 AM
|
0
|
0
|
5918
|
|
IDEA
|
Amir, Our county surveyors office does courtesy reviews on all surveys before they are filed using MicroSurvey 2020. There are instances of true curves in nearly every CAD data set provided by them. The ideal workflow for us would be as I described before where we could just pull the CAD data in (from the local coordinate system) and somehow capture the COGO bearings/distances/curves as they sit locally...then bring the linework to the desired location and move/scale/manipulate it without losing the original measurements...then use the standard copy-lines-to Pro Fabric workflow to integrate it into the fabric. Mike
... View more
08-12-2020
09:39 AM
|
0
|
1
|
2471
|
|
IDEA
|
Amir, Our county surveyors office does courtesy reviews on all surveys before they are filed using MicroSurvey 2020. There are instances of true curves in nearly every CAD data set provided by them. The ideal workflow for us would be as I described before where we could just pull the CAD data in (from the local coordinate system) and somehow capture the COGO bearings/distances/curves as they sit locally...then bring the linework to the desired location and move/scale/manipulate it without losing the original measurements...then use the standard copy-lines-to Pro Fabric workflow to integrate it into the fabric. Mike
... View more
08-12-2020
09:39 AM
|
0
|
1
|
3460
|
|
POST
|
The anchors are still definitely an issue in Pro 2.6. I was fighting with this until a saw the quick work-around here by adding a Rectangle Text element instead. This actually works a lot better and it's easier to control the element flow. We are using this to dynamically insert text into a print layout for the Javascript API and it's now working great! Thanks!
... View more
08-12-2020
07:45 AM
|
0
|
0
|
4173
|
|
IDEA
|
Hi Amir, Our current workflow to import CAD data into the ArcMap parcel fabric is to first export the CAD linework to a feature class, add that to a blank ArcMap project, start editing to allow copying of the lines then paste the line work into the traverse dialog in a separate project with the editing fabric. Our CAD data comes from our surveyors office in a local coordinate system so the copy-paste into the traverse dialog preserves/generates the correct bearings-distances. My thought was to automate this process in Pro where I can create feature classes from the CAD linework, calculate the COGO values with python (in the local coordinate system) and preserve the correct bearings/distances for import into the Pro fabric. I know that, in Pro, I can bring in the CAD linework, georeference it from it's local coordinate system, copy-lines-to them into the fabric, then update the COGO bearings and distances. However, this will only preserve the correct bearings/distances if we are careful not to scale or rotate the linework in any way...only move them. Is there a way to copy line work from CAD into a traverse dialog ala ArcMap Fabric? -- or some other better workflow? Thanks! Mike
... View more
08-06-2020
07:41 AM
|
0
|
1
|
2470
|
|
IDEA
|
Hi Amir, Our current workflow to import CAD data into the ArcMap parcel fabric is to first export the CAD linework to a feature class, add that to a blank ArcMap project, start editing to allow copying of the lines then paste the line work into the traverse dialog in a separate project with the editing fabric. Our CAD data comes from our surveyors office in a local coordinate system so the copy-paste into the traverse dialog preserves/generates the correct bearings-distances. My thought was to automate this process in Pro where I can create feature classes from the CAD linework, calculate the COGO values with python (in the local coordinate system) and preserve the correct bearings/distances for import into the Pro fabric. I know that, in Pro, I can bring in the CAD linework, georeference it from it's local coordinate system, copy-lines-to them into the fabric, then update the COGO bearings and distances. However, this will only preserve the correct bearings/distances if we are careful not to scale or rotate the linework in any way...only move them. Is there a way to copy line work from CAD into a traverse dialog ala ArcMap Fabric? -- or some other better workflow? Thanks! Mike
... View more
08-06-2020
07:41 AM
|
0
|
1
|
3460
|
|
POST
|
I can't seem to find a (simple - via parameters) modification to the 4.x LayerList widget that will allow a ctrl+click under a group layer to check/uncheck all layers within that group as the standard ArcMap or ArcPro TOCs do. Does anyone know if this is possible out of the box? Thanks Mike
... View more
05-28-2020
08:13 PM
|
0
|
0
|
873
|
|
IDEA
|
It would be great to have the ability to call the Update COGO tool/method from Python in Pro.
... View more
05-08-2020
12:36 PM
|
6
|
6
|
2685
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 05-01-2026 10:36 AM | |
| 1 | 11-14-2011 01:45 PM | |
| 15 | 10-29-2024 10:14 AM | |
| 1 | 05-31-2023 12:34 PM | |
| 1 | 05-30-2024 02:54 PM |
| Online Status |
Offline
|
| Date Last Visited |
05-19-2026
09:36 AM
|