LocateOp ScanAtPoint -how to set tolerance to be 2D only

Hi

Are there any possibility to make the LocateOp ScanAtPoint to only look at the distance in the XY plane instead of 3D

I am working in VBA with the XFT object. My problem is that we work in 3D and sometimes I need to find a nearby feature that have a big difference in the level. For Instance having a point in the bottom of a sewer line and I need to find the a GroundLevel point within 1 to 2 meters in XY planen but the sewerline mayby 8 meters below the ground.

If there is no way to make the ScanAtPoint to look only at the 2D distance it is a very strong wish for a upcoming release Smile

Any idea to a work around is very wellcome too!

Waiting and hoping

Erik

Parents
  • Hi. I don't think that is possible today. I assume you are directly passing the point on the sewerline as reference point for the locateOp. May I suggest that instead you pass as referencePoint the same coordinate but with Z=0 ? That would center the search at ground level. Even though we're still searching with a "sphere" at least we'll be centered properly. Adjust the tolerance for the distance you're interested in and you'll find your point. There may be more than one result for the ScanAtPoint operation I guess, so you can filter out the good one.

    Hope this helps,

       Martin

      

Reply
  • Hi. I don't think that is possible today. I assume you are directly passing the point on the sewerline as reference point for the locateOp. May I suggest that instead you pass as referencePoint the same coordinate but with Z=0 ? That would center the search at ground level. Even though we're still searching with a "sphere" at least we'll be centered properly. Adjust the tolerance for the distance you're interested in and you'll find your point. There may be more than one result for the ScanAtPoint operation I guess, so you can filter out the good one.

    Hope this helps,

       Martin

      

Children
  • Hi Martin

    Thanks for a quick response. All though Denmark is very flat, a common aproximation of all ground levels to 0=Mean sea level is not fair :-). I guess you meant that if I know the average ground level, I could use that.

    Well that's worth considering!

    BTW:  Will the located features in the enumeration be in the same order as the exist in the designfile or with the closest first??

    Please don't forget to put the 2D scanAtPoint on the wishing list

  • Hi. I don't know the order of the located features and to be honest, I'm not sure you should rely on that as it may change depending on file writes and such.

    I'm not sure we could do much better with a "2D" scanAtPoint. If we're in a 3d dgn we normally behave in 3d. If we had a 3d dgn and coded a 2d function, we'd probably work at z=0 anyway. Note that  this is what Microstation does when you attach a 2d reference in a 3d model, it assumes z=0.

       Martin