In AutoCAD, polar tracking helps you draw lines at specific angle increments. If the polar tracking angle is set to 30°, which of the following angles will the cursor snap to when you move it freely?
Think about multiples of the set angle increment.
Polar tracking snaps the cursor to multiples of the set angle increment. With 30°, the cursor snaps to 0°, 30°, 60°, 90°, etc.
You want to draw a line at exactly 75° using polar tracking. The polar tracking angle is set to 45°. What should you do to draw the line at 75°?
Consider the angle increments and how to get 75° as a multiple.
Since 75° is not a multiple of 45°, you need to set the polar tracking angle to a smaller increment like 15°, which divides 75° evenly.
Given a polar tracking angle increment of 22.5°, which of the following DAX expressions correctly calculates the nearest polar tracking angle for a given angle value in degrees?
NearestAngle = ROUND('Angles'[Angle] / 22.5, 0) * 22.5
Think about rounding to the nearest multiple.
Rounding the angle divided by 22.5 and then multiplying back gives the nearest multiple of 22.5°, which matches polar tracking snapping.
You want to create a dashboard visualization that shows the distribution of line angles drawn with polar tracking enabled at different increments (15°, 30°, 45°). Which visualization type best helps users compare the frequency of lines at each angle increment?
Consider which chart type clearly compares categories and counts.
A stacked bar chart clearly shows counts per angle increment side by side, making comparison easy.
Consider this DAX measure intended to snap an angle to the nearest 10° increment for polar tracking:
SnappedAngle = ROUND('Table'[Angle] / 10, 1) * 10However, the results are incorrect. What is the cause of the error?
Check how ROUND's second argument affects rounding precision.
ROUND(number, 1) rounds to 1 decimal place, not to nearest integer. It should be ROUND(number, 0) to round to nearest whole number.
