Hi Folks, 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.
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. I haven't played with the fields "z" or "where" yet. If anyone has anything to add, feel free. There may be a more efficient way of doing it, but this worked. Kurt On Jun 29, 2010, at 12:00 PM, [email protected] wrote: > Message: 6 > Date: Tue, 29 Jun 2010 09:58:45 -0400 > From: Kurt Springs <[email protected]> > Subject: [GRASS-user] Re: grass-user Digest, Vol 50, Issue 73 > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > 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. > > I still need to know the best field type for Latitude and Longitude > coordinates. > > Kurt > > On Jun 29, 2010, at 2:37 AM, [email protected] wrote: > >> >> Message: 8 >> Date: Tue, 29 Jun 2010 07:37:23 +0100 (BST) >> From: Benjamin Ducke <[email protected]> >> Subject: Re: [GRASS-user] Entering point data with SQLite >> To: GRASS user list <[email protected]> >> Message-ID: >> <872729080.66359.1277793443836.javamail.r...@mail.thehumanjourney.net> >> Content-Type: text/plain; charset=utf-8 >> >> On 06/28/2010 09:52 PM, Kurt Springs wrote: >>> >>> 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. >>> >> >> I have found http://sqlitestudio.one.pl to be an extremely >> useful open source solution for SQLite DB management. >> Also, the author is very friendly and prompt to accommodate >> wishes for additional functionality. >> >> Have you considered simply using v.in.ogr/v.out.ogr to >> manage the data in an external SQLite3 database? >> Starting with GRASS 6.5.svn and GDAL 1.7, this should >> work well. >> >> Cheers, >> >> Ben >> >>> As always, any help will be greatly appreciated. >>> >>> Kurt
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
