Welcome back to the community, @nandlalnepal! Could you kindly provide me with the following details through a private message? Maybe I could have a closer look at your case?
- Username
- Project name
- Server
You should be able to send me a private message as outlined in the post discussed previously:
Dear Support team,
My problem has not yet been solved which became critical for my data collection and related works, can you please loot at it and suggest me ASAP,
Thanking you,
Dear Kal_Lam,
please find the detail as follows:
Username: xxxxxxx
Project name: Leprosy cases - based data Nepal
Server: kf.kobotoolbox.org
I am very sorry that my problem is not yet solved, and I am facing an expert data for download.
Waiting for your response,
Thanks
Hi, sorry for your inconveniencece but the issues is not solved, please see here today’s result and please suggest me,
@nandlalnepal, we have identified an issue in our backend system (Formpack) that affects the geopoint values when trying to download data in XLS format. As a temporary workaround, if you still want to proceed with downloading your data in this format, please uncheck the GPS question (geopoint question type) as illustrated in the screenshot below:
If you still require the GPS question (geopoint question type), you can easily download your data in the XLS (legacy) format. Please refer to the screenshot below for guidance:
We will keep you informed as soon as we have resolved this issue. We sincerely apologize for any inconvenience this may have caused and appreciate your patience during this time! Thank you for your understanding!
FWIW I took a quick look at some of your submissions (but not all 17360 of them! 
) and note that there appear to be a few with gps fields that have arguably malformed geopoint values (!). Specifically, valid geopoints must have 4 space-separated components: latitude, longitude, altitude and accuracy. Whereas several of your submissions appear to be missing an altitude and accuracy value [I wont share an example here for privacy reasons, but there are several so they should be easy to spot; eg uuid 6998c39f-bf04-4020-839f-1bf13c88691c]
I have no idea how they got like this because both Enketo and KoboCollect always populate geopoints with all 4 fields, and will set the altitude and/or accuracy to 0 if they cannot be determined.
I’m not saying this will necessarily fix your issue, but it does suggest that there might well be some malformed geopoints elsewhere in all these submissions that the export code might now be tripping up on and causing it to fail.
FWIW I was able to create a simple geopoint form just now and submit some data to it from both Enekto and KoboCollect, and it exported fine. So exporting geopoints appears to still be working.
@nandlalnepal, it appears that the problem originated from your GPS data point rather than the formpack itself. Below is a screenshot illustrating what went wrong:
The geopoint question type is designed to capture four specific components, but it appears that your submission included five components, which the formpack was unable to process. To resolve this issue, please edit your submission 613315993 according to the instructions in the image below. This should address your concern effectively.
If you continue to experience any issues, please don’t hesitate to reach out to us. We’re here to assist you!
@nandlalnepal, we would like to learn on how this occurred.
Did you made any changes to your submission? Understanding these details would assist us in preventing similar issues with formpack moving forward.
Dear Kal_Lam and team,
Many thanks for your support and contribution. I have identified that 479 data has such problems, it was because they were directly copied and pasted from excel cells hence creating extra spaces. I will solve the problems first and convey you how it was done.
Thanks
Nand Lal Banstola
@nandlalnepal, thank you for confirming on this!
