Identify segments that are true curves and the curve properties

[LyonMNGIS]

Hello,

I am trying to identify true curve segments within a File Geodatabase layer. I know we can manually see if a single segment is a curve by selecting editing vertices in the edit tools pane, then for each segment within a feature we can right click and select "Change Segment."  From there we can see if the segment is already a line, or a  circular arc (true curve).  This seems like a lot of drilling down and I suspect there may be a cleaner way to identify curves.

Questions:

• The edit vertices tool displays the xy coordinates for each vertex in a line each line / feature which is shown in the bottom right of the image.  However, it does not identify if a segment between the vertices are a strait line or curve.  Is this possible?  In the example the segment between vertex 2 and 3 is a true curve.
• Within a layer can we bulk identify lines or segments that contain a true curve?
• As a bonus can we identify the properties of a curve such as the radius, arc length, etc?

Thanks!

[DanPatterson]

in arcpy's polyline class there is a hascurves method which would enable you to  determine polyline segments that have curves

Polyline—ArcGIS Pro | Documentation

[DanLee]

I wonder what you would like as the output.  Do you want an output that contains only the true curves, each as a feature or multipart feature for multiple curves from the same original feature? If possible, could you describe how you are going to use them in your workflow? Thanks.

[JenFrazer_USFS_NR-GISS-IRIN]

I am looking for a solution to this.  True curves was brought into AGOL. However it is not compatable with offline sync workflows in field maps.  The problem is when it was enabled- all my current feature services had that setting default 'yes' when it appeared. Super annoying- I had to audit everything.    I am having an issue now with an older feature service I did not catch. I suspect someone added a feature with a true curve.  Now I need to seek and destroy it so the feature service can be taken offline.  A simple output I would love is just a csv list of the OID number of the record in the feature service with the true curve.