Report or data tag to display Arc data

[The Hamma]

Does anyone know how to display arc data in a table or data tag?

Specifically the Radius,Sweep, Chord, and Arc Length. 

[Pat Stanford]

I don't think those values are available in worksheets or Data Tags.

 

If you need them I think you will have to go with a worksheet script and develop them yourself.

[The Hamma]

17 hours ago, Pat Stanford said:

I don't think those values are available in worksheets or Data Tags.

Seems like basic values that should be able to be queried as they are required for every site plan.  I will request an enhancement.  

[rDesign]

Isn’t most of this information included in the preformatted Property Line reports? Or are the segment records only attached if you created the arcs as a part of a ‘property line’ object?

Tools: Reports: Create Reports: Preformatted Report: Property Line-Segments

 

Edited August 14 by rDesign

[The Hamma]

2 hours ago, rDesign said:

Isn’t most of this information included in the preformatted Property Line reports? Or are the segment records only attached if you created the arcs as a part of a ‘property line’ object?

In my Opinion the Property Line object is an overcomplicated tool for creating property lines.  The property lines are simply lines from one point to another with or without radius.  The property line tool is not the way any engineer would divide a property.  This is for inputting data that someone else has already created. I never use it.   

[The Hamma]

Ok so when looking at a line I was able to write a worksheet function to give the correct bearings to a line in vectorworks. but even if I replace the if's with WS_IF the data tag only reports the name of the tag.  Any ideas of what is wrong with the Data tag forumla?

 

Worksheet formula

=IF((ANGLE>=0), IF((ANGLE=90), CONCAT('N 0°'), IF((ANGLE<90), CONCAT('N ', TRUNCATE(90-ANGLE, 0), '° ', INT((90-ANGLE-INT(90-ANGLE))*60), ''' ', ROUND((((90-ANGLE-INT(90-ANGLE))*60)-INT((90-ANGLE-INT(90-ANGLE))*60))*60), '"', ' E'), CONCAT('N ', TRUNCATE(ANGLE-90, 0), '° ', INT((ANGLE-90-INT(ANGLE-90))*60), ''' ', ROUND((((ANGLE-90-INT(ANGLE-90))*60)-INT((ANGLE-90-INT(ANGLE-90))*60))*60), '"', ' W'))), IF((ANGLE=-90), CONCAT('S 0°'), IF((ANGLE>-90), CONCAT('S ', TRUNCATE(90+ANGLE, 0), '° ', INT((90+ANGLE-INT(90+ANGLE))*60), ''' ', ROUND((((90+ANGLE-INT(90+ANGLE))*60)-INT((90+ANGLE-INT(90+ANGLE))*60))*60), '"', ' E'), CONCAT('S ', TRUNCATE(ANGLE-ANGLE-ANGLE-90, 0), '° ', INT((ANGLE-ANGLE-ANGLE-90-INT(ANGLE-ANGLE-ANGLE-90))*60), ''' ', ROUND((((ANGLE-ANGLE-ANGLE-90-INT(ANGLE-ANGLE-ANGLE-90))*60)-INT((ANGLE-ANGLE-ANGLE-90-INT(ANGLE-ANGLE-ANGLE-90))*60))*60), '"', ' W'))))

 

Data tag Formula

#WS_IF((ANGLE>=0), WS_IF((ANGLE=90), CONCAT('N 0°'), WS_IF((ANGLE<90), CONCAT('N ', TRUNCATE(90-ANGLE, 0), '° ', INT((90-ANGLE-INT(90-ANGLE))*60), ''' ', ROUND((((90-ANGLE-INT(90-ANGLE))*60)-INT((90-ANGLE-INT(90-ANGLE))*60))*60), '"', ' E'), CONCAT('N ', TRUNCATE(ANGLE-90, 0), '° ', INT((ANGLE-90-INT(ANGLE-90))*60), ''' ', ROUND((((ANGLE-90-INT(ANGLE-90))*60)-INT((ANGLE-90-INT(ANGLE-90))*60))*60), '"', ' W'))), WS_IF((ANGLE=-90), CONCAT('S 0°'), WS_IF((ANGLE>-90), CONCAT('S ', TRUNCATE(90+ANGLE, 0), '° ', INT((90+ANGLE-INT(90+ANGLE))*60), ''' ', ROUND((((90+ANGLE-INT(90+ANGLE))*60)-INT((90+ANGLE-INT(90+ANGLE))*60))*60), '"', ' E'), CONCAT('S ', TRUNCATE(ANGLE-ANGLE-ANGLE-90, 0), '° ', INT((ANGLE-ANGLE-ANGLE-90-INT(ANGLE-ANGLE-ANGLE-90))*60), ''' ', ROUND((((ANGLE-ANGLE-ANGLE-90-INT(ANGLE-ANGLE-ANGLE-90))*60)-INT((ANGLE-ANGLE-ANGLE-90-INT(ANGLE-ANGLE-ANGLE-90))*60))*60), '"', ' W'))))#

 

 

Result from the worksheet of four lines each pointing to a different quadrant

 

[Pat Stanford]

You can't mix and match between WS and Data Format.

 

Once you type #WS_ until the next )# everything in the middle needs to be in Worksheet format functions only.

 

You can mix #WS_ )# and other #Data Tag# in a single data tag because they are both in data tag format.

 

So try your nested IF inside a single #WS_ delimiter.

 

But it may be too long. Not sure if DT formulas or #WS_ formulas can be over 255 characters.

[The Hamma]

51 minutes ago, Pat Stanford said:

So try your nested IF inside a single #WS_ delimiter.

That did the trick, Unfortunatly the align to object does not work on lines. 

[Pat Stanford]

Yep I can't make it alight to a line or a polygon either.  Time for a VE. You don't even need to hold your breath for a month.

[The Hamma]

For the Arc I was able to calulate the Radius, Diameter, and Chord Length, but since the start and end angles are not reported or many of the x y corrdinates I am unable to determine the angle of the chord.  See attached drawing for reference. It seems to me that there should be some formula out there to calculate this. 

 

ARC DATA TAG.vwx

[Pat Stanford]

You might have to resort to worksheet scripts,

 

Get2dPt will get you the center and end points of an Arc.  

 

Index of 1 gets the center point.  Index of 2 and 3 get the arc end point.

 

RunScript does work in Data Tags.

 

 

Procedure ArcPoints;
{©2024  Pat Stanford - pat@coviana.com}
{licensed under the Boost Software License 1.0}
{https://github.com/boostorg/boost/blob/master/LICENSE_1_0.txt}
{TL/DR Use as you want, attribution for source, No warranty}

{Worksheet Script to return the X or Y coordinate of a point on an Arc}
{Takes two parameters, first is either a character X or Y to}
{determine which part of the coordinate to return.}
{Second is the index of the point.  0 = arc center. 1 or 2 are the}
{arc end points}

{=RunScript('ArcPoints','X','2')}

VAR	H1		:Handle;
	X1,Y1	:Real;
	S1		:String;
	N1		:Integer;
	
BEGIN
	H1:=WSScript_GetObject;
	S1:=WSScript_GetPrmStr(0);
	UprString(S1);
	N1:=WSScript_GetPrmInt(1);
	Get2DPt(H1,N1,X1,Y1);
	If S1='X' then WSScript_SetResReal(X1);
	If S1='Y' then WSScript_SetResReal(Y1);
End;

Run(ArcPoints);

 

[The Hamma]

2 hours ago, Pat Stanford said:

You might have to resort to worksheet scripts

Can the script live in the resources or at a specified external location or does it need to be in a script palette?

[Pat Stanford]

It can be saved as a text file and stored in any of the Resource folders defined for the BuildResourceList commands. But that means that every user is going to have to have a copy of the txt file. If I am doing this (which is very rarely), I typically use code 120 to specify the Reports & Schedules folder in Default content.  RunScript should look in User->Workgroup->Application folder looking for the file.

 

=RunScript(120,'ArcPoints.txt','X',2)

 

If you leave it in a script folder in the Resource Manager, then the script will travel with the file and be useable by whoever has the file.

 

 

[The Hamma]

Ok so Runscript returns a value of X,  Can I reuse the value of X in the formula or do I have to invoke the Runscript every time?

Specifically in the data tag

 

Edited August 15 by The Hamma

[Pat Stanford]

I think you will have to rerun it every time.

 

Rather than trying to do the whole thing in Worksheet functions, you are probably better off going to VS/Python and putting all the calcs into a single Worksheet Script. Then you only have one script to run to get your Data Tag output rather than multiple scripts and a bunch of Worksheet stuff.

[The Hamma]

On 8/15/2024 at 2:25 PM, Pat Stanford said:

Rather than trying to do the whole thing in Worksheet functions, you are probably better off going to VS/Python and putting all the calcs into a single Worksheet Script. Then you only have one script to run to get your Data Tag output rather than multiple scripts and a bunch of Worksheet stuff.

Thanks again.  Everything is working great.  I had to create two data tags (one is "Arc Bearing" and the other is "Arc Opposite Bearing") for the arcs because the bearing Northing can't be controlled with the direction that the arc is drawn.  

Also I did put theArcPoints.vs  in the  Reports & Schedules folder in Default content in my workgroup folder. 

 

Updated 08/16/2024 bug fixes

 

 

Arc Bearing.vwx

Edited August 17 by The Hamma

[The Hamma]

I revised this for Vectorworks 2025.  

The line labels will rotate with the lines automaticaly and they also compensate for when the Georeferencing Angle to North is changed from 0 degrees. 

 

You will need to put the "ArcPoints.vs"  in the  \Libraries\Defaults\Reports_Schedules of your USER, WORKGROUP, or APPLICATION library folder.

 

The tags are in Site Property Line.vwx file. 

 

 

ArcPoints.vs