Quote:
|
Originally Posted by Dutch
Because according to the information on the gpsvisualizer site, it needs the lat/lon fields first.. It disregards the fields there isn't any header information for in the first line.
|
Just to clarify, The first line does need to have field names, but you can write your own header line, and the order of the fields doesn't matter, especially if you're plotting waypoints. (If you want to draw a track from plain-text, you would need to have a first column that indicated "T" for track, either as a field name or under a "type heading.")
If there's enough interest, I can certainly look into adding support for reading NetStumbler log files directly (using the file upload form, not the text-entry waypoints form). If you want to make that happen, send me a few sample files, both from the U.S. and from Europe; contact address is at the bottom of
GPS Visualizer.
I also have a couple of questions:
1) Would you prefer to have your log files plotted as waypoints or as tracks? (Or both??) I would guess waypoints.
2) If they're waypoints, what should the "name" and "description" fields be? I would think the SSID for the name, but for the description, would it make more sense to use the MAC address, the SNR, or what? Keep in mind that the name and desc fields could also combine info from multiple NetStumbler fields, e.g., name = "linksys (42)", desc = "10:13:13 (GMT) / 00:03:2f:20:7b:37." But I'd need to make a decision and stick with it.
3) Is there a standard filename extension for NetStumbler log files, like ".nsl" or something? Usually, GPS Visualizer recognizes files by suffix.