Survey123 fails to print map in report

Question

Recently, in some of our projects we experience the error that the location question fails to print the exact position the Survey was sent at.
Survey was obviously sent with coordinates (could provide evidence if needed).
Attached, you will find the statement we use to print plus an additional statement with simply the geopoint question attribute (${location} in our surveys). It seems to be the case that the map renders at 0,0 position and does not respect the actual coordinates, the survey was sent in.
We have no idea why this is happening in some of our surveys and have no clue where to start looking at.

Any help is appreciated.

Thank you!

report_template_issue.pdf

report_template_issue.docx

CiciXiao_1-1741286957590.png

AyanPalit_0-1741286020370.png

MarcMuehleisen · Answer

What makes it even more weird/complicated is that only some users have this issue.
Some will a fine map with zoomed location, others don´t.
Tried resetting the view (delete it and recreating via Share survey), but it did not change anything about this behaviour.

MarcMuehleisen · Answer

Maybe i should have added, that there is no pin/marker that is printed in the report.

The geopoint question in our surveys is required (so it cannot be null) and i confirmed it in multiple places (WebMap, Survey123 Website). We even extract lat, lon with pulldata("@geopoint",${location},"y") as can be seen in the screenshot.
Even directly in Survey123 Website when selecting a record, i can see the exact position the survey was sent at (see same screenshot).

Generating a report from the same selected record still gives just a default map which means that he cannot render the exact map position.

report_template_issue2.pdf

report_template_issue2.png

CBarrett · Answer

> Survey was obviously sent with coordinates

You say this, but it's unclear that you've confirmed the ${location} has coordinates other than Null Island. Look at this survey record in your Portal's Survey123. If it shows up in Null Island, then the report is accurately generating for the coordinates given.

Sometimes bad geocodes give me this location and so I have to manually fix them. I should probably set a check in the survey to prevent these.