<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Folks,<div><br></div><div>Okay, through trial and error I figured it out. Lat Long coordinates entered into a SQLite data base should be entered as DOUBLE. I went over to decimal Lat Long and used negative instead of W. It came out fine. I used v.in.db to create a point vector. The only field types you can use as coordinates are INTEGER and DOUBLE. Since INTEGER cuts off the fraction (which can produce some peculiar point vectors) DOUBLE is what you need.</div><div><br></div><div>to used v.in.db you need to type "v.in.db table=name (whatever you name the table) driver=sqlite database=/Users/account/grassdata/LOCATION/MAPSET/named.db (You need the path to the database you created this is how I have it set up in OS X. In this case I stuck my target database in my MAPSET. I may do it elsewhere in the future) x=column with longitude y=column with latitude (I imaginatively used East and North) output=name of vector.</div><div><br></div><div>I haven't played with the fields "z" or "where" yet.</div><div><br></div><div>If anyone has anything to add, feel free. There may be a more efficient way of doing it, but this worked.</div><div><br></div><div>Kurt</div><div>
<br><div><div>On Jun 29, 2010, at 12:00 PM, <a href="mailto:grass-user-request@lists.osgeo.org">grass-user-request@lists.osgeo.org</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Palatino; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Message: 6<br>Date: Tue, 29 Jun 2010 09:58:45 -0400<br>From: Kurt Springs <<a href="mailto:ferret_bard@mac.com">ferret_bard@mac.com</a>><br>Subject: [GRASS-user] Re: grass-user Digest, Vol 50, Issue 73<br>To:<span class="Apple-converted-space"> </span><a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>Message-ID: <<a href="mailto:1FFCD860-4138-4E08-965D-4ED755509A95@mac.com">1FFCD860-4138-4E08-965D-4ED755509A95@mac.com</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>I am afraid I am using OS X and SQLite studio isn't ready for OS X yet. GRASS 6.4 is the latest binary build thus far.<br><br>I still need to know the best field type for Latitude and Longitude coordinates.<br><br>Kurt<br><br>On Jun 29, 2010, at 2:37 AM,<span class="Apple-converted-space"> </span><a href="mailto:grass-user-request@lists.osgeo.org">grass-user-request@lists.osgeo.org</a><span class="Apple-converted-space"> </span>wrote:<br><br><blockquote type="cite"><br></blockquote><blockquote type="cite">Message: 8<br></blockquote><blockquote type="cite">Date: Tue, 29 Jun 2010 07:37:23 +0100 (BST)<br></blockquote><blockquote type="cite">From: Benjamin Ducke <<a href="mailto:benjamin.ducke@oxfordarch.co.uk">benjamin.ducke@oxfordarch.co.uk</a>><br></blockquote><blockquote type="cite">Subject: Re: [GRASS-user] Entering point data with SQLite<br></blockquote><blockquote type="cite">To: GRASS user list <<a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>><br></blockquote><blockquote type="cite">Message-ID:<br></blockquote><blockquote type="cite"><span class="Apple-tab-span" style="white-space: pre; ">        </span><<a href="mailto:872729080.66359.1277793443836.JavaMail.root@mail.thehumanjourney.net">872729080.66359.1277793443836.JavaMail.root@mail.thehumanjourney.net</a>><br></blockquote><blockquote type="cite">Content-Type: text/plain; charset=utf-8<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 06/28/2010 09:52 PM, Kurt Springs wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Also, I have been using SQLite Database Browser 1.3. It doesn't place the rows of field names in the order they are created. In fact there seems to be no order at all and no way to rearrange the order.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I have found<span class="Apple-converted-space"> </span><a href="http://sqlitestudio.one.pl/">http://sqlitestudio.one.pl</a><span class="Apple-converted-space"> </span>to be an extremely<br></blockquote><blockquote type="cite">useful open source solution for SQLite DB management.<br></blockquote><blockquote type="cite">Also, the author is very friendly and prompt to accommodate<br></blockquote><blockquote type="cite">wishes for additional functionality.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Have you considered simply using v.in.ogr/v.out.ogr to<br></blockquote><blockquote type="cite">manage the data in an external SQLite3 database?<br></blockquote><blockquote type="cite">Starting with GRASS 6.5.svn and GDAL 1.7, this should<br></blockquote><blockquote type="cite">work well.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Ben<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">As always, any help will be greatly appreciated.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Kurt</blockquote></blockquote></span></blockquote></div><br></div></body></html>