FAQ: Why are my outputs in the middle of the ocean?

Why are my outputs in the middle of the ocean?



If you are a DataHub user who just found your outputs lying in the middle of the Atlantic Ocean or any other ocean, this article is for you.

There are a couple of possible reasons why your outputs are in the Ocean:

1.  The outputs were intended to be there

2.  The outputs were incorrectly projected

3.  The outputs had coordinates referenced to UTM origin

We will be focusing on reasons 2 and 3 as they are the ones most likely to produce an issue with your project.


Incorrect Projection

Incorrect projection most commonly happens due to an incorrect Coordinate Reference System (CRS) or a mismatch between the site CRS and CRS of the uploaded pre-processed file.  We highly recommend reviewing the CRS info of all files in the uploaded dataset when you observe large misplacements of outputs.

If you believe that all are correct and consistent but there are still issues in the geolocation, kindly send the support team a message.


Outputs referenced from UTM origin

UTM or Universal Transverse Mercator is a projection system that divides the world into 60 zones and projects them onto a flat surface to determine its position.  This coordinate reference system has its origin 0,0 plotted at the intersection of the Prime Meridian and the Equator.  If you try searching this location in Google Maps, it will fall in a place inside the Atlantic Ocean.



Image Source:  Google Maps


Point clouds, when not assigned with a CRS, usually have coordinate values that has an origin of 0,0.  When these are uploaded as UTM pre-processed file in DataHub, they will be placed in the Atlantic Ocean.  If you observe the same symptoms on your outputs, we highly recommend reviewing the CRS of your uploaded file and its expected position.


Still Having Trouble?

Send us a message at!

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk