Elevation Benchmark

[beanus]

I've been using the elevation benchmark tool in view ports and I've just realised that if I move a viewport vertically the benchmark value changes, is there a way to stop this happening?

[Yancka]

No.

With built-in elevation benchmark you can only check the option to Use Control Point and then manually place it on 0 level.

[klinzey]

I think this was fixed in 2010.

[Yancka]

Oh, mine.... I already was trying to write PIO for this... can anyone with VW2010 test it an approve that it indeed works?

[Ken]

You can "compensate" for it by adding or subtracting the Reference Elevation in the OIP.

[willofmaine]

Why don't Elevation Benchmarks just use the file's Z=0 value? All of the design layers are set with respect to this Z=0, so it seems it would make sense for section viewports to also use this value. Buildings could be set at their real-world elevations or, alternatively, a file-wide adjustment could be used if one prefers to model their first floor at Z=0. Either way, having to explain to a client that their building is sitting higher or lower on the site than expected because the viewport was moved on the sheet is not terribly appealing...

[mike m oz]

I agree with Will. If a Layer's Z has been defined as 98' (or 98 m) then the Elevation Benchmark object should be aware of that and in Elevation and Section Viewports automatically reflect that. Moving the Viewport around on the Sheet Layer should not affect this.

[Jonathan Pickup]

I'm with mike and will

[J Lucas]

That would be "Intuitive". That is what I intuitively expected the first time I used the Elevation Benchmarks.

[gScott]

i have a symbol with all the main levels dashed,

with benchmarks, all set relative to the symbol's

0,0 datum.

slap that in the annotations, at the correct height

relative to the model + fewer screw ups are

encountered on site; only one set of levels

to update + keep an eye on..