When I import a set of waypoints in CSV format the number of points is truncated, yet if I import the same data as CSV to Google Earth Pro, export as a KMZ and then import the KMZ to Alpine Quest the missing data points are there.
In this instance I'm using an edited version of the Geolytix Retail Points data of supermarket and convenience store locations in UK (Open Data), the original CSV file can be downloaded here https://drive.google.com/file/d/1B8M7m8 ... x.ghost.io if the url is no longer valid an updated url can normally be accessed from this blog article https://geolytix.com/blog/supermarket-retail-points/
Importing as KML doesn't give me the same control in AQ over how the information is displayed as importing as CSV, and CSV is easier for me to quickly edit.
The support forum is temporarily read-only. For urgent requests, please email contact[at]psyberia.net
Import CSV data truncated
-
- Site Admin
- Posts: 6407
- Joined: Wed Apr 14, 2010 9:41 pm
Re: Import CSV data truncated
Thanks for this report.
I check the file and the problems comes from un-escaped quotes in text field.
I'll make sure the app handles this case in the next update.
Until it's available, you can regenerate the CSV file with the option "Quotes all text fields", and it will work fine.
Sorry about that.
I check the file and the problems comes from un-escaped quotes in text field.
I'll make sure the app handles this case in the next update.
Until it's available, you can regenerate the CSV file with the option "Quotes all text fields", and it will work fine.
Sorry about that.
Do you like AlpineQuest ? Leave a small comment on Google Play !
Re: Import CSV data truncated
thanks for your help , this file and others work now, Just to note that using the option "Quotes all text fields" is when you save CSV using OpenOffice Calc rather than MS Excel.