The issue that I found, was that in TELEMAC-3D the calculation of latitude or longitude (i forgot which one) was done twice, leading to nonsensical values in mesh3d. That is the bugfix that I proposed, and with that fix, our models works well. However, I don't think we have done models that cross the dateline. So there might be another issue as well. I will try to have a look at it soon.
Hi,
I understand this issue has been closed along with a MR that had even a test case to compare between 2D and 3D!
However, I still had problems at polar latitudes (and also for triangles across the +/- 180° meridian), which was fixed by modifiying these 2 routines:
flupri.f: I think the sustainable way of doing this, would be to use XEL/YEL in FLUPRI (because I am essentially re-doing the fix in LATITU for SPHERICAL COORDINATES = YES)
inbief.f: here I am just shutting off the SURDET calculation, but I don't even think it needed in the end, is it?