This will generate a csv file with all the correct headings that can then be loaded into GSAK (without change)įor more information on these fields see database variables Just use GPSBabel to convert your required file format to UNICSV. The main reason for this is to keep the text import compatible with GPSBabel (it equates "Name" with GSAK "Code", and "desc" with GSAK "Waypoint Name") It may not be immediately obvious, but going with this compatibility indirectly allows you to load hundreds of formats into GSAK. Pay special attention to the "Description" field (GSAK Waypoint name) and the alias "name" for "code". Note : There is often confusion in terminology with different software with the fields Code,Waypoint name, and description. TempDisabled - Tempdisabled status (boolean) State - State/Province name of the waypoint ShortHtm - Short description contains HTML code (boolean) ShortDescription - Cache short description PlacedDate - Date the cache was placed/hidden PlacedBy - Name of the cache placer/hider OwnerId - ID (usually a number) of the owner of this cache Longitude - Waypoint longitude, all GSAK formats are supported, but must be WGS84 datum LongHtm - Long description contains HTML (boolean) Latitude - Waypoint latitude, all GSAK formats are supported, but must be WGS84 datum However as a bare minimum you should include code,description,latitude,longitude:ĬacheType - A one character string representing the cache type ( more information )ĭifficulty - Difficulty (1.0 to 5.0, with. Field names may be in any order and not all are required. The first line of the text file must contain the comma or tab delimited list of field names for the following data. When comma separated, each field can be optionally enclosed in double quotes. This option will allow you load plain text files that are tab or comma separated. Pocket Queries from are usually the best source of bulk data for GSAK. This is the most common file type to load into GSAK. ZIP files are also supported (but they must contain GPX/LOC files). Select this format to load Groundspeak Pocket Queries, LOC files, and any other GPX files. By far the most common file type (and GSAK default) is the GPX file format - especially from unfortunately, the file is called POI vs probably a more appropriate CACHE.ġ7 # PROLOGUE Longitude,Latitude,Name, commentĢ0 # INDIVIDUAL DATA FIELDS, IN ORDER OF APPEARANCE:Ģ2 IFIELD LON_HUMAN_READABLE, "", ".5f"Ģ3 IFIELD LAT_HUMAN_READABLE, "", ".5f"ģ0 OFIELD GEOCACHE_TYPE, "", " %-.4s", "no_delim_before,optional"ģ1 OFIELD GEOCACHE_CONTAINER, "", "/%-.4s ", "no_delim_before,optional"ģ2 OFIELD GEOCACHE_DIFF, "", "(%3.1f", "no_delim_before,optional"ģ3 OFIELD GEOCACHE_TERR, "", "/%3.This box enables you to select the file type that you want to load into GSAK. It would appear that the GPSBabel POI style was created from the Geocaching reqs,Īnd NOT from the CSV files now found on the web for the Garmin GPS units. Might have to try some experiments with a test file. So - if the is not being handled at all, then the 4th comment field might be stripped out, and then any next might indicate a new waypoint and the 641 would be treated as the coord. ![]() How to tell Babel that the 4th field has embedded CR/LF's and is enclosed by "xxx"Īs an old programmer, it's always the "exceptions" that cause the most coding challenges. Or see how/what is being used by the "Garmin POI" selection,īut haven't found it as yet. I suspect that the conversion is not recognizing and processing the 4th field of enclosed -> "xxxx" Just shorten up your large address fields and try the conversion again. I had a similar problem with GPSBabel - it is very finicky with the input fields: I had a couple of extra fields that confused it. > No, there is a 641 in your input - it is the first 3 digits in the zip code for Kansas City. > Invalid latitude 641.183333 in waypoint. > gpsbabel.exe -p "" -w -i garmin_poi -f "C:\Diners.csv" -o gpx -F ![]() > and here's the GPSBABEL execution from the GUI, here's a couple of lines from the "Diners" CSV file - which in Notepad appear on their single lines
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |