Skip to main content

Location of projects and datasets on a global scale

What determines the location of the red locator dot for a dataset vs a project

Written by Karen Joyce

When you upload geotagged drone mapping data, GeoNadir will automatically read the latitude and longitude of your images. It uses the information of the first image it reads to put a 'red dot' on the world map to mark its location.

After the data have been processed to create an orthomosaic, the location of the red dot may shift to be more representative of the entire dataset.

Sometimes, we may have difficulty extracting the full coordinates from the first image. In this case, the dataset may appear off the west coast of Africa - represented at 0,0 latitude and longitude. After processing, this should be updated to the correct location of the dataset.

What about the red locator dots in the projects summary page?

Remember that a project can contain many different datasets, as well as vector layers. This means that the red locator dot on the project summary map is indicative of the whole project area, not just of an individual dataset.

Therefore, if you have a project that contains a dataset in Europe, and another dataset in Australia, its red locator dot may end up somewhere in India or the Indian Ocean!

When you first add raw data into a project, that project may remain zoomed to the global extent rather than the dataset itself. For any project containing global extent data, the red locator dot in the project summary page will be automatically placed off the west coast of Africa - represented at 0,0 latitude and longitude. As soon as you start working in the project, this will update and the red locator dot will appear in the correct location.

Did this answer your question?