使用 Autodesk Forge Viewer Geolocation Extension 时的结果不正确 [英] Incorrect results using Autodesk Forge Viewer Geolocation Extension

问题描述

这与

如您所见，模型上的选定点 [0] 与真实的 GPS 坐标相去甚远.此外，refPointLMV 具有巨大的价值.

当我从无人机照片中获取一些 lon/lat/alt 数据时，会发生类似的情况.无人机 GPS 数据将接近模型 positionLL84，例如 (4.586577106, 51.626037158, 49.095).但是，当我执行 Geolocation.lonLatToLMV(4.586577106, 51.626037158, 49.095) 时，我得到了屏幕外的结果.

我们已经与 Autodesk 进行了与此相关的支持查询开放了两个多月，但并没有取得太大的成功.他们说工程团队太忙了，无法解决这个问题，并建议尝试修复我们这边的错误.支持参考 LMV-5261.

我已经能够使用以下代码将 Geolocation.lonLatToLMV 的结果带入查看器空间:

const gpsPosition = new THREE.Vector3(经度，纬度，高度，);const 位置 = 查看器.getExtension('Autodesk.Geolocation').lonLatToLmv(gpsPosition);const data = viewer.model.getData();const globalOffset = data.globalOffset;const refPointTransform = data.refPointTransform;//应用变换position.add(globalOffset)position.applyMatrix4(refPointTransform);//HACK:应用上述转换后，最终//需要旋转 -45 度才能将点移动到位//完成此操作后，位置将与照片完全匹配.//看起来像一个奇怪的黑客，但我已经用 20 多张无人机照片进行了测试，它们都匹配.const quaterion = new THREE.Quaternion().setFromEuler(new THREE.Euler(0, 0, -Math.PI/4),);position.applyQuaternion(quaterion);

这里的问题是，我们正在使用单个模型进行测试，这显然不是一个强大的解决方案，我们可以期望它与我们投入的所有未来模型和无人机数据一起使用.

工程团队可能需要多长时间来解决这个问题?或者他们可能会解决这个问题?

解决方案

很抱歉由于农历新年而延迟.在与我们的工程团队核实后，目前的解决方案是执行以下操作:

1. 将项目基点移动到 N0 E0，但保持与正北的角度
2. 将 LAT LONG 复制到测量点

之后，应该可以期待 GEO 转换的结果.

这是上述设置和结果的快照

This is related to my previous question. I'm posting a new question to try and explain the situation better.

I am placing marker objects on a model using data taken from drone surveys. I have access to high accuracy GPS data and also omega/phi/kappa rotation data.

I am trying to use the Autodesk.Geolocation extension to convert the lon/lat/alt data to viewer space.

All models were originally created in Revit.

When I use the Geolocation extension, it seems like the refPointLMV and GlobalOffset are not correctly being taken into account.

Here's an example:

As you can see, the selected point [0] on the model is nowhere near the real GPS coords. Also, the refPointLMV has huge values.

Something similar happens when I take some lon/lat/alt data from the drone photo. The drone GPS data will be close to the model positionLL84, e.g (4.586577106, 51.626037158, 49.095). However, when I do Geolocation.lonLatToLMV(4.586577106, 51.626037158, 49.095) I get a result way off screen.

We've had a support query open with Autodesk related to this open for over two months now, but not had much success there. They said the engineering team is too busy to work on this and recommended to try and fix the error on our side. Support ref LMV-5261.

I have been able to bring the result of Geolocation.lonLatToLMV into viewer space with the following code:

const gpsPosition = new THREE.Vector3(
  longitude,
  latitude,
  altitude,
);

const position = viewer
  .getExtension('Autodesk.Geolocation')
  .lonLatToLmv(gpsPosition);

const data = viewer.model.getData();

const globalOffset = data.globalOffset;
const refPointTransform = data.refPointTransform;

// applying the transform

position.add(globalOffset)
position.applyMatrix4(refPointTransform);

// HACK: after applying the above transforms, a final
// rotation of -45 degrees is required to move the points into position
// once this has been done, the locations match up exactly to photos. 
// Seems like a weird hack, but I've tested with over 20 drone photos, they all match up. 

const quaterion = new THREE.Quaternion().setFromEuler(
  new THREE.Euler(0, 0, -Math.PI / 4),
);

position.applyQuaternion(quaterion);

The problem here is that we are testing with a single model and this is clearly not a robust solution that we can expect to work with all future models and drone data we throw at it.

How long is it likely to take for the engineering team to fix this? Or are they likely to fix this at all?

解决方案

Sorry for the delay due to the Chinese New Year. After checking with our engineering team, the current solution is to do the followings:

1. Move the Project base point to N0 E0, but remain the angle to true north
2. Copy the LAT LONG to Survey point

Afterward, the result of the GEO conversion should be expected.

Here are the snapshots of the above setting and the result

这篇关于使用 Autodesk Forge Viewer Geolocation Extension 时的结果不正确的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！