I’m working on a ReactJS app, and I would like to use the WebODM ‘viewer’ to display/render GeoTiff files I upload to my app.
My idea was to upload a GeoTiff to my app, and to then have that geotiff forwarded to my WebODM instance through the WebODM API, and have that GeoTiff placed in a (new) project (through the API as well), so that it can be viewed.
After this, I should be able to open the geotiff (map), and I was thinking of grabbing the unique iframe that should be available, embed this somewhere in my app, and through this iframe ‘render’ the geotiff (map) in the WebODM viewer.
The above should result in me clicking a geotiff in my app, and it opening this geotiff in the WebODM viewer through the iframe.
However, is it me or is it really not possible to upload/forward GeoTiff files into WebODM? If it is possible to upload/forward GeoTiffs to WebODM, can someone explain me how to do it?
And if not, does anyone have any idea how else to implement the WebODM viewer into a react app?
I don’t believe our workflow is really setup to accomodate that, though you might be able to force it with enough effort.
Have you given a look to GeoTIFFJS or Leaflet for rendering geospatial data in web contexts?
Thanks for your welcome, and for your reply of course
I think, indeed through ‘forcing’, I may have a chance, and I have looked into both mentions. However, my biggest challenge as of now is that I can’t seem to upload GeoTiff files and view them in the WebODM viewer, so this is what I would like to focus on / get answered first, before I look deeper into alternatives. .
When I create a new project and try to upload the GeoTiff, I got two errors:
1st one was something along the lines of max entries exceeded 10. I was getting this error when trying to upload a tif file.
2nd one was cloud point processing server is offline. Even though I had that server running on my computer.
So what I did was upload the tif file on that server (node ODM) and it took like 1.5 hour to process that file and during that time my CPU was running at it max. I was worried it may burn.
Then, when the processing was complete I got this zip file to download and that zip file contains different files like Metadata, get json and bunch of other stuff. I think internally WebODM uses these files to render a tif file.
When I inspected the online viewer I didn’t got any tif file I got some Metadata file and geojson file.
I believe I’ll be able to progress (perhaps not find a solution, but a las) if I would be able to upload a GeoTiff into WebODM and view it. The question thus remains: can I do this and if so, how?
Hello, did you have a chance to look at this?
I am not able to assist you more as I don’t code and this is not working within how the program is designed, so I can’t really give more guidance on how you should proceed to modify things for your usage, unfortunately.
Maybe someone else might have ideas for you.
Is it a “normal” geotiff or COG (cloud optimized geotiff)?
There are some other open source solutions that might help you
Also geoserver can “store” and publish a geotiff as a webservice (wms) but Im not sure it fits your needs.
Hi! I don’t think you need to be able to code to tell me wether or not a geotiff can - in some way - be uploaded to WebODM, so I’d be still very keen on hearing if, and if so how, that would be possible!
Thanks! To keep it short; I basically only need to know how to upload geotiff files to WebODM (if that’s possible at all), so I can view them in the WebODM viewer.
Anything is possible if you code it, but no, the current platform is not designed to do what you want to do.
You would have to make extensive code changes to do so.
Perhaps looking into Leaflet and GeoTIFFJS would be a more direct route.
Thanks again! That’s true, but I was merely wondering if WebODM would be able to process GeoTiffs out of the box. Can you confirm that it is not possible to upload Geotiffs into WebODM (without custom code) and view those in the viewer?
FYI: Alternatively I’ve coded my own viewer now, so I’m good, but it would still be very nice to be able to use the WebODM viewer and all its features instead.