Firstly, I really appreciate all the work that goes into WebODM and the time spent responding to queries.
I’ve noticed that when I download results using the Projection → Custom EPSG option, the outputs don’t appear to be reprojected, they still come out in the UTM zone automatically selected by ODM. I’ve tried entering both the EPSG code and a full PROJ string, and while the files download correctly, they still seem to be in the automatically assigned projection (e.g. WGS84 / UTM zone 50S). Couple of queries -
1 - Is the Custom EPSG option actually intended to reproject the outputs, or is it meant for a different purpose? I typically work in project grids such as EPSG:10488 (GDA94 / ALB94), but WebODM usually processes everything automatically in WGS84 UTM 50S (even when I use GCP file with a project grid)
2 - If the download option isn’t performing a reprojection, is there a way to have WebODM/ODM process the entire project directly in a specified EPSG/PROJ grid, such as EPSG:10488 (GDA94 / ALB94)?
It’s meant for reprojecting the outputs. Strange that it’s reverting back to UTM even if you explicitly request a different one. If you can provide some reproduction steps and a dataset I could try to look into it. I ask because it seems to work fine with my datasets. Are you using the latest version? (3.1.3)
No, I’m running the Windows installer version 2.8.1 - maybe the upcoming update will fix the issue. My dataset is pretty huge, so will try to replicate the issue on a smaller survey to provide the dataset for your review. Cheers
May I ask if you specified the Custom EPSG option in the API call? I’m using version 3.1.2, and setting the EPSG code doesn’t take effect. Could you please guide me on how you configured it? Thank you very much!
When I choose Custom EPSG in the download options, the files still come out in the default UTM projection. I’m using the WebODM interface only (not calling the API directly), and changing the EPSG code or using a proj string doesn’t seem to change the output.
From my side it looks like the option is accepted, but the data itself isn’t being reprojected. I’m happy to test further or share an example — what’s the best way to provide a dataset?
Uploading the raw GeoTIFF somewhere like Google Drive or Dropbox would do. Would also be nice to have exact reproduction steps (what EPSG code did you choose)?
I’ve uploaded the raw GeoTIFF outputs and a screen recording showing the reprojection/export process here: https://drive.google.com/drive/folders/1KMvSIobC2LQz7sFO4N6y9F2FU8WxljzI?usp=drive_link
In the video, I export the same task multiple times using different projections. However, when inspecting the resulting GeoTIFFs in QGIS, all outputs report the same CRS: EPSG:32750 (WGS84 / UTM Zone 50S).
When you type an EPSG code, just type “10463”, not “EPSG:10463”. I think that’s probably the issue. I see from your video you’re copy/pasting EPSG:10463, but it’s probably causing the projection code to be ignored.
Mm, looks like that EPSG code is missing from WebODM’s internal database.
Using the latest version (or Lightning) there’s an option to export via PROJ definition, but the Windows release hasn’t received updates in a year (Windows Native Installer Update Timeline - #3 by JazperInc), so you can’t do that from there yet.
Here’s the export dialog with the latest version of WebODM (3.1.3)
awesome thanks - I will continue to reproject in QGIS until the latest version is available. Just wanted to make sure it wasn’t user error - thanks for looking into it!
