LP360 – This is the native 64 bit Windows version of LP360. It has no software prerequisites other than Windows. It executes on Windows x64, Version 7 and later. LP360 for ArcGIS® – A fully qualified extension for ArcMap® desktop. LP360 for ArcGIS® requires the Basic level of ArcMap. This remains a 32 bit product…
On the LP360 QA/QC Toolbar there is the option to add rectangular, circular, or polygonal area issues. After digitizing your area of interest, a dialog appears with some generic issue types in a dropdown menu. If you need to add a custom issue type, simply click in the dropdown to add your own issue description.…
When a base station file is corrupted or incorrectly recorded (for example: observation rate is not set correctly), a Continuously Operating Reference Station (CORS) may be available to use in its place. To obtain and utilize a CORS file, follow the instructions below: Visit https://www.ngs.noaa.gov/CORS_Map/ and navigate to the area of the flight. Once you…
When your data needs to be in a coordinate system that is not specified in LP360, you may need to create a User-Defined Coordinate System. One of the easiest ways to do that is by modifying a Known Coordinate System. For ease of demonstration I have color coded a User-Defined Coordinate System with what has…
MicroStation and TerraPhoto reference require a RGB orthomosaic image. The normal workflow for exporting sUAS derived orthomosaics from Metashape creates a RGBA image. Make sure the “Write Alpha Channel” setting in the screenshot below is unchecked to create a RGB orthomosaic in Metashape before attempting to import into TerraPhoto.
If the Loki or the base station recording is interrupted, there will be gaps in the raw data that will affect ASPSuite processing. This can be verified in ASPSuite. After completing steps 1-3, click on the diagnostics button in the top right of the ASPSuite window: In the window that pops up, click on “File”…
Starting with 2018.1, LP360 relies on a hosted license manager (Reprise License Manager or RLM). It requires an active connection between the client and server machine for license management and software use. RLM does not rely on Secure Sockets Layer (SSL) nor Transport Layer Security (TLS) protocols for Client-Server communications.
