v.in.gps.html 3.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899
  1. <h2>DESCRIPTION</h2>
  2. <em>v.in.gps</em> allows the user to import waypoint, route, and track
  3. data from a locally connected GPS receiver or a text file containing
  4. GPS data of many common formats. Translation is done via the
  5. <em><a href="http://www.gpsbabel.org">GPSBabel</a></em> program.
  6. <p>This software is not intended as a primary means of navigation.
  7. <h2>NOTES</h2>
  8. <em>v.in.gps</em> automatically reprojects data using the
  9. projection settings of the current location.
  10. The default input data projection is lat/lon WGS84. If your GPS outputs data
  11. using another projection or map datum, you may include the
  12. <em><a href="http://trac.osgeo.org/proj/">PROJ.4</a></em>
  13. parameters defining your projection in the <b>proj</b> option and
  14. <em>v.in.gps</em> will reproject your data accordingly.
  15. Great care must be taken to get these parameters correct!
  16. The automatic transform may be skipped by using the <b>-k</b> flag in which
  17. case the data will be imported unprojected, as it appears in the <b>input</b>.
  18. <p>Route and Track data may be uploaded as a series of points by using the <b>-p</b>
  19. flag, otherwise they will be imported as lines. You can run <em>v.in.gps</em>
  20. multiple times and merge the line and point vectors with the <em>v.patch</em>
  21. command if you want, but take care when merging dissimilar attribute tables.
  22. <h2>EXAMPLES</h2>
  23. <h3>GPS device connected via USB adapter</h3>
  24. Import waypoints, tracks, routes from /dev/ttyUSB0 and save
  25. to a GRASS vector map:
  26. <div class="code"><pre>
  27. v.in.gps -w input=/dev/ttyUSB0 format=garmin output=waypoints
  28. v.in.gps -t input=/dev/ttyUSB0 format=garmin output=tracks
  29. v.in.gps -r input=/dev/ttyUSB0 format=garmin output=routes
  30. </pre></div>
  31. <h3>GPS device connected via serial adapter</h3>
  32. Import waypoint data from a Garmin GPS connected at /dev/ttyS0 and save
  33. to a GRASS vector map named <i>waypoints</i>:
  34. <div class="code"><pre>
  35. v.in.gps -w input=/dev/ttyS0 format=garmin output=waypoints
  36. </pre></div>
  37. <h3>Import track data from a GPX</h3>
  38. Import track data from a GPX text file and save to a GRASS vector map
  39. named <i>tracks</i>.
  40. <!-- (currently buggy) The gpxlogger program distributed with
  41. <a href="http://gpsd.berlios.de/">GPSd</a> >2.30 is a good program for
  42. creating these logs. -->
  43. <div class="code"><pre>
  44. v.in.gps -t input=gpslog.gpx format=gpx output=tracks
  45. </pre></div>
  46. <h3>Import route data from GPS connected at /dev/gps</h3>
  47. Import route data as a series of points from a Garmin GPS connected at
  48. /dev/gps and save to a GRASS vector map named <i>routePoints</i>:
  49. <div class="code"><pre>
  50. v.in.gps -r -p file=/dev/gps format=garmin output=routePoints
  51. </pre></div>
  52. <h2>SEE ALSO</h2>
  53. <em>
  54. <a href="db.execute.html">db.execute</a>,
  55. <a href="v.in.ascii.html">v.in.ascii</a>,
  56. <a href="v.in.garmin.html">v.in.garmin</a>,
  57. <a href="v.db.connect.html">v.db.connect</a>,
  58. <a href="v.patch.html">v.patch</a>
  59. </em>
  60. <a href="http://www.gpsbabel.org">gpsbabel</a> from gpsbabel.org<br>
  61. cs2cs from <a href="http://trac.osgeo.org/proj/">PROJ.4</a>
  62. <h2>AUTHORS</h2>
  63. Claudio Porta and Lucio Davide Spano, students of Computer Science at
  64. University of Pisa (Italy).<br>
  65. Commission from Faunalia Pontedera (PI)<br><br>
  66. Based on <em>v.in.garmin</em> for GRASS 6.0 by Hamish Bowman<br>
  67. and <em>v.in.garmin.sh</em> for GRASS 5 by Andreas Lange
  68. <br>
  69. <!--
  70. When we tested the script with a Garmin GPS we noticed that importing waypoints
  71. the <i>time</i> field is not correctly set. The data reported is
  72. a default system time, while with a gpx text file this thing did not
  73. happen. We believe that is a <i>gpsbabel</i> trouble in translating
  74. from <i>garmin</i> to <i>xcsv</i> ...
  75. -->
  76. <p><i>Last changed: $Date$</i>