You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I feel like this new LIDAR stuff is a little confusing to use.
The collection won't be recognized in our system as a "lidar collection" (and thus you won't get silvimetric processing capabilities) unless the selected sensor type has "is lidar" checked to true. However, there is also a LIDAR wave length. And so for the end user I think one could be easily mistaken thinking they are creating a LIDAR collection since their wave length is set to LIDAR.
I ran into this during development but I'm also seeing it happening right now in prod. Somebody is uploading data to a collection with sensor (True View 515 (LIDAR)), and the sensor wave length is LIDAR, but the sensor type is Laser (which doesn't have "is lidar" checked).
The text was updated successfully, but these errors were encountered:
I feel like this new LIDAR stuff is a little confusing to use.
The collection won't be recognized in our system as a "lidar collection" (and thus you won't get silvimetric processing capabilities) unless the selected sensor type has "is lidar" checked to true. However, there is also a LIDAR wave length. And so for the end user I think one could be easily mistaken thinking they are creating a LIDAR collection since their wave length is set to LIDAR.
I ran into this during development but I'm also seeing it happening right now in prod. Somebody is uploading data to a collection with sensor (True View 515 (LIDAR)), and the sensor wave length is LIDAR, but the sensor type is Laser (which doesn't have "is lidar" checked).
The text was updated successfully, but these errors were encountered: