Completed 2D map doesn't appear over base map

I have a few different datasets covering different parts of the same area. Usually when I successfully complete creating orthophoto, it appears projected over base map (Google, Mapbox etc that is in the standard list of base maps in WebODM. But some datasets are not getting projected over base map. I can download them as tif and add as a layer in QGIS for example and they seem fine, but they don’t appear on WebODM base map.
Usually after task was complete you just click Vew Map button next to Download Assets and you see your orthophoto on the world map zoomed where is suppose to be, you can look at Surface Model or Terrain Model and everything is good, but some datasets I recently got completed not getting applied to to the base map. When you click View Map it shows you the world map not zooming to the location where your orthophoto suppose to be… If you zoom there yourself there is nothing there. I can’t view coloured surface and terrain models either, but I still can download them all as assets and they seem fine.
Wondering why is that?

1 Like

Really interesting.

Are you able to share your input data and processing settings so I can try to reproduce?

1 Like

Yeah I will try.
The internet here really pain in the butt, but I think I can push them through.
Not so many files there… around 140…
What the best way to share them?

1 Like

I just came up with a theory that explains that glitch sort of. :slight_smile:
I am mapping in quite unique place. Across the 180 meridian. Which is also known as Dateline or The Dateline… the place where people loose their drones as it’s quite unique place on Earth where drone literally get teleported from lets say western edge of the world map to the eastern one just flying across that line.
Some quite expensive and smart drones were lost there already by some careless pilots…
Happens very easy. If you start your flight from the eastern side of the map then send you drone across and push Return Home button or program it to return home after completion, the drone will fly away as it finds itself on the other side of the map and simply will try to fly around the world back home.
So I don’t send mine across the dateline on automatic mission but I map along the dateline from one side then I do separate flight from another…
And I just noticed, that those datasets that don’t get laid over base map are actually those from flying along the dateline… I basically overlap the dateline from one side at 179.9998 East and then from another side at 179.9998 West
So the dataset I get actually present on the both sides of the world map simultaneously and that’s probably trigger that glitch when WebODM tries to attach the orthophoto that covers both opposite edges of the world map.
Want to try it yourself? :wink:

2 Likes

Ha! Very interesting. If you open your imagery in QGIS does it display ok? It should just show up in the local UTM zone.

1 Like

The orthophoto and other tif files produced from that dataset displayed in QGIS fine. When I add them in QGIS lets say images from the flight along the western edge of the world… most of image sets over the area where it supposed to be in the west and the bit of it that overlaps the dateline showing in the east if I scroll the world map to the eastern side…
It’s interesting place indeed.

2 Likes

You’re in about the worst place in the world to map, haha. Quite literally the definition of an edge-case…

Thanks for exposing it to us!

1 Like

I think the Dateline crosses land only 3 times. Most of it In Antarctica and a bit in Fiji and Russia. It also pain in the arse to work with maps, especially vector maps that cover Earth from the both sides of the dateline… all vectors when they touch the dateline they don’t go across of it… they just fly around the globe to the other end of the map… just like any drone would do… so I have to always slice any vectors to accommodate them nicely from both sides of the dateline…

I will share a small dataset of that sort so you’d try it yourself… :slight_smile:

3 Likes