> For the complete documentation index, see [llms.txt](https://docs-7.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-7.phoenixlidar.com/lidarmill-desktop/workflow-kk/uploading-files/imagery/importing-ladybug5+-data.md).

# Importing Ladybug5+ data

The Ladybug5+ camera stores images in stream files with the file extension *PGR.* When a PLP file containing Ladybug sessions is first opened, it's necessary to import the PGR stream files into the project (SpatialExplorer should warn you in the Message that the PGR files need to be imported). 

To import PGR files, navigate to **Tools -> Camera -> Import Camera Sessions from Data**:

<figure><img src="/files/5Gigtnw7aePjhSOssOKk" alt=""><figcaption></figcaption></figure>

For most customers, **FLIR Ladybug5+ (USB on notebook)** should be selected as **Camera Model**, as this indicates that the PGR stream files were stored during acquisition on a notebook PC, which is by far the most common method of storing PGR streams. Similarly, most customers have an additional, non-Ladybug camera, used for aerial imagery collection, such as an A6K-lite or Sony A7R4, so in most cases the **Camera Index** should be set to **1**, rather than **0**. If the lidar system does not have a traditional camera used for aerial imagery, then **Camera Index** should be set to **0**.&#x20;

Use the **Data** field to point SE to the directory containing the PGR streams. For organizational purposes, it's best to copy the PGR streams into the cam1 directory. It's best to use **Timestamps** that are stored in the PGR streams (**Parse from photos**), but if this fails for some reason you can try using **events from the navigation system**.&#x20;