|
IDEA
|
@jcarlson- thanks for your post. Based on our screen-share this morning, the issues you’ve helped us to uncover are as follows: 1. The default angular unit is in Degrees for new projects. A project template would help with this. You could create a project template that has this setting pre-defined to be Degrees Minutes Seconds. There are few other benefits to using a project template. See the help topic here: https://pro.arcgis.com/en/pro-app/latest/help/projects/create-your-own-project-template.htm 2. When the traverse pane is open, and you go to the backstage to change a distance, direction or angular unit setting, the new unit settings don’t take effect immediately in the already-open traverse pane. You have to close the traverse pane and start a new one to see the unit changes. We'll explore some approaches to improve on this experience for future releases. -Tim
... View more
02-10-2022
12:28 PM
|
0
|
0
|
2472
|
|
IDEA
|
@jcarlsonthat's very strange. The only other thing I was wondering about is whether you tried it in a completely fresh project?
... View more
02-10-2022
09:22 AM
|
0
|
0
|
2487
|
|
IDEA
|
Hi jcarlson, what you describe sounds identical to a bug that was fixed for 2.5. (Esri internal reference: 1486) Are you working on Pro 2.5 or higher? If so, I'm not sure what might cause this bug to reappear. Here's a video showing use of the "+" and "-" in 2.9: And just to confirm you're looking in the right place for the Angular Unit settings in the project backstage: Good idea, Paul, about remembering the deflection angle when modifying the previous line.
... View more
02-09-2022
03:02 PM
|
0
|
0
|
2526
|
|
IDEA
|
After internal discussion with others on Esri staff ( @Scott_Harris @JenniferCadkin ) we may need some more information. However, based on what you’ve indicated so far we think that you are using the “Vary symbology by attribute” property to rotate point symbols. Is that correct? Going with this, we put together a mini test workflow to rotate an Arrow point symbol to be oriented along the same direction as existing features. This should help to show the relationship between the measure tool’s direction units and values, and the point symbol's Rotation style. The test workflow is as follows: Create a double field on a points feature class and call it “Direction” Add the point feature class to the map On the point layer, set the properties on the point symbol to be an arrow. Rotate the symbol so that it is pointing north in its default state. Do this under Properties -> Rotation, set the angle to 90°: Using the Vary symbology by attribute, set the Field to Direction, and set the Rotation style to Arithmetic: In the project backstage go to Options -> Units > Direction Units and set the default direction to Polar. Also, click the cell in the number column to get the Direction Formatting, and change the direction base unit to Decimal Degrees, and set decimal places: Add point features near or on the segments that will be measured. Use the Measure Direction Distance tool and snap to and click the first point on the segment, then snap to and double-click the second point. Select and copy the Direction component from the measure tool dialog Select the point and open the attributes pane, and paste the direction into the Direction field. The arrow points in the same direction as the measured line:
... View more
01-10-2022
10:42 AM
|
0
|
0
|
1946
|
|
IDEA
|
Hi Pascal, CopyLineFeaturesToParcelType does extra things that do not apply to connection lines. For example, it will look for closed loops and create a seeds for the closed loops that it finds. Such behavior is not needed for connection lines. But these are not hidden rules, they are documented in the parcel API SDK. As for connection lines, one coding rule I can think of is to make sure you have an Active Record when you write the new connection line feature so that it goes to the correct record, but this is also documented and is not only a coding rule; it applies also when using the editing tools. All rules should be documented. If there’s missing information, then it’s important that we make sure it’s documented for everyone. If you mean geometry / topology related rules, these are available to everyone via the properties of the topology that is used with the fabric. Since you're aware of the editing API, I presume that you have written code that creates connection lines, but you believe that these are not the correct result, or else you believe that there was too much code to write? Can you be more specific about what you're encountering so that we can understand your request better? Thanks. -Tim
... View more
12-02-2021
11:51 AM
|
0
|
0
|
1543
|
|
IDEA
|
Hi Pascal, If I understand your request correctly, this is already available using the standard editing API. Connection lines are standard features in a standard feature class. The SDK is not as specialized as it is for the ArcMap fabric, and so this gives developers a lot more access to edit the Pro fabric's feature classes. I can help with sample code but before I start working on that have you looked at the sdk documentation for editing concepts and editing snippets? https://github.com/esri/arcgis-pro-sdk/wiki/ProSnippets-Editing https://github.com/esri/arcgis-pro-sdk/wiki/ProConcepts-Editing -Tim
... View more
12-01-2021
03:01 PM
|
0
|
0
|
1560
|
|
IDEA
|
You could also try the GP tool called Table Compare. It has a "Schema Only" compare type.
... View more
11-17-2021
02:20 PM
|
0
|
0
|
2213
|
|
POST
|
Hi Mike, It looks like you need to check for nulls: var RecFeatRow = First(FeatureSetByRelationshipName($feature, 'RecordHasLand',['Name'], false));
if (RecFeatRow != null) {return RecFeatRow.Name;}
... View more
11-16-2021
02:43 PM
|
1
|
1
|
2398
|
|
BLOG
|
An add-in is available that provides expanded functionality for the spatial placement of CAD data sets that are in modified projections. (See below "What is a modified projection?") The add-in is called Transform CAD Layer, and is available here. It is used to transform a CAD layer by entering a scale factor, rotation, local coordinates and corresponding grid coordinates. Using the Transform CAD tool After you’ve installed the add-in, follow the steps below to use the tool to transform the CAD dataset. 1. In the Catalog pane, select and drag-and-drop the Polyline class onto the map. 2. The projection for the CAD layer needs to be defined if it is not already. This must be the projection that the transformation parameters are based on, otherwise the CAD Layer will not be correctly placed. To do this select one of the CAD layers in the CAD group layer in the table of contents. 3. The contextual ribbon for the CAD Layer becomes available, and presents the CAD Data tab. 4. Click the Define Projection button and use the GP tool that appears to set the projection for the CAD file. 5. If the add-in was successfully installed, then a button called “Transform” will be present in the Alignment group on the CAD Data tab. 6. Click the Transform button. 7. The Transform CAD Layer dialog appears. 8. Enter the parameters for local coordinates, grid coordinates, scale and rotation values. 9. Check the box Update ground to grid corrections if you want to use the scale and rotation values as the map's ground to grid correction settings. 10. Click the OK button to transform the CAD layer based on your entered transformation parameters. Note: The values that you type are remembered the next time you use the dialog. Click the Reset button to set all the transformation parameters back to starting values. What is a modified projection? You may not recognize the term “modified projection” and may be more familiar with one of its other names: local datum plane, engineering coordinate system, ground coordinate system or simply “surface” or “ground”. When receiving a CAD file from a surveyor or engineer, it is common to find that it does not spatially align with the rest of your GIS data. It may be offset a few thousand feet to the north east, or it may be miles away to the south west and may seem to be in an arbitrary local coordinate system. However, if the surveyor is using a modified projection then this information is usually provided as transformation parameters that indicate how the projection is modified, making it possible to use these parameters to place the CAD drawing in its projected grid location without the need for manually picking out geo-referencing links. Here’s an example of a simple modification in the notes of a subdivision plat from Houston, Texas: In this note all the criteria are present for converting between ground coordinates and grid coordinates. There is the reference to the projection that is being modified and information that the coordinates are “Surface” coordinates. The combined scale factor is provided, and there is no rotation mentioned, and no origin specified. Since the note does not explicitly provide the origin, the 0,0 origin of the State Plane coordinate system is implied. For this particular description above, the corresponding CAD file location in its original ground coordinates is located to the north east of the projected grid coordinate location. Since the add-in uses the convention of multiplying by the scale factor, for this example the scale to use would be the inverse, since the wording calls for "dividing"; hence 1/1.00013 = 0.99987, and it's entered as follows: Here is another example, showing the drawing settings used for some AutoCAD data. For this drawing, the equivalent entries to convert to the grid location using the Transform CAD Layer add-in are as follows: Why are modified projections used? Modified projections like these are used for large scale low distortion projections. Distances measured on the ground match the distances in the digital coordinate space of the mapping software environment without having to apply a scale factor and rotation. The reason they are successful is that they cover an area of a comparatively much smaller surface of the earth compared to the projection that they are derived from, and so using a flat plane for modeling a ground-based coordinate system is useful and practical for small site locations such as an engineering site, or a parcel subdivision. The combined scale factor is based on two components, the distortion caused by the projection and the scale caused by the elevation, as more fully described in the help topic Ground to grid correction. Code The CAD transformation functionality uses a similarity transformation. The code for this add-in is available on GitHub from the community samples repository, Transform CAD Layer code. Here’s a code snippet of the similarity transformation used to generate the vectors written to the world file: var pFrom1 = new Coordinate2D(dOriginX, dOriginY);
var pTo1 = new Coordinate2D(dGridX, dGridY);
var dDeltaX = dGridX - dOriginX;
var dDeltaY = dGridY - dOriginY;
var pFrom2 = new Coordinate2D(pFrom1.X + (10000 / dMetersPerUnit),
pFrom1.Y + (10000 / dMetersPerUnit));
var Rotated = GeometryEngine.Instance.Rotate(pFrom2.ToMapPoint(),
pFrom1.ToMapPoint(), dRotation * Math.PI / 180);
MapPoint RotatedAndScaled = (MapPoint)GeometryEngine.Instance.Scale(Rotated,
pFrom1.ToMapPoint(), dScaleFactor, dScaleFactor);
var RotatedScaledTranslated = new Coordinate2D(RotatedAndScaled.X + dDeltaX,
RotatedAndScaled.Y + dDeltaY);
if (WriteWorldFile(sTargetWldFile, pFrom1, pTo1, pFrom2,
RotatedScaledTranslated))
{ ... Video demonstration: Using the Transform CAD Add-in References Format of world files used for CAD datasets: World files for CAD datasets. CAD coordinates systems: CAD geospatial coordinates Ground to grid correction: Ground to grid correction Transform features: Transform features Add-in Releases https://arcg.is/0qru58 (3.2 and higher) https://arcg.is/1bb9Lq (3.0 and higher) https://arcg.is/1vnymX (2.6, 2.7, 2.8, and 2.9) Thank you to the Esri Community Thanks to those who sent their CAD datasets and transformation parameters: @Geographic_Mythos, @StevenLowman , @Mark_Hotz, @Matt_Trebesch @LaurenConnor , HeatherWidlund
... View more
11-11-2021
08:09 PM
|
5
|
6
|
9879
|
|
POST
|
With 2.9 we now have new SDK documentation content on COGO API topics: https://github.com/esri/arcgis-pro-sdk/wiki/ProConcepts-COGO
... View more
11-11-2021
02:00 PM
|
0
|
0
|
2330
|
|
POST
|
@WileyBogren- on your question: I'm still curious if there's a way to use Transfer Attributes to actually put the values into the intended COGO fields rather than new ones, or at least to get around the 'REQUIRED' flag on the added fields in order to delete them afterwards. As a workaround you could try the following: Run the GP tool Disable COGO, Run Transfer Attributes, Calculate the results from the added fields to the original COGO fields, Delete the extra fields that were created , and then Run Enable COGO.
... View more
10-15-2021
03:05 PM
|
0
|
1
|
3708
|
|
POST
|
Hi mcguerd, here's a quick way to calculate a text field and populate it with the quadrant bearing text by converting it from a double that represents north azimuth, decimal degrees: 1. Open the Attribute table of the line layer: 2. Right-click the column header of the Text field you want to calculate, and click "Calculate Field" 3. Set the Expression type to Arcade: Copy the following Arcade function and expression into the code block area, and click OK or Apply. Of course, you can adapt the code if you want to change the symbols like the "°" into a "-" etcetera. This expression also assumes your source field name is called "Direction" . function NorthAzimuth2Quadbearing(azimuth){
return ConvertDirection( azimuth, {directionType:'North', angleType: 'Degrees'}, {directionType:'Quadrant', angleType: 'DMS', outputType: 'text', format: 'pd[°]mm[\']ss["]b'})
}
NorthAzimuth2Quadbearing($feature.Direction)
... View more
10-11-2021
03:05 PM
|
3
|
3
|
4275
|
|
POST
|
Also related. The Reverse Direction command used with Edit vertices will reverse the geometry as well as the COGO Direction value:
... View more
09-15-2021
06:36 PM
|
1
|
0
|
3656
|
|
POST
|
Sorta-kinda. (-: If your second traverse from start of line 1 to end of line 3 has a good misclose, then it means that if you were to do the full loop traverse POB to POB, it would also have good misclose. So in that sense the QA result would be equivalent. If your second traverse has a poor misclose, then the mistake could be in either the first set of lines or in the second set of lines, but you'd have the same problem to solve regardless if you'd done a complete loop traverse. To get the full loop of lines within the same traverse grid, then the lines do need to proceed in the same direction, and so your idea of reversing the existing traverse, and then completing the loop would be a nice enhancement for solving your use case.
... View more
09-15-2021
03:34 PM
|
0
|
0
|
3659
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 09-18-2024 12:38 PM | |
| 4 | 09-18-2024 01:01 PM | |
| 3 | 04-26-2024 11:14 AM | |
| 1 | 04-04-2024 03:04 PM | |
| 1 | 02-15-2024 04:08 PM |
| Online Status |
Offline
|
| Date Last Visited |
Friday
|