[GRASS-dev] select issue with wingrass

[Moritz Lennert]

On 09/11/07 19:19, Michael Barton wrote:
> 
> 
> On 11/9/07 11:04 AM, "Moritz Lennert" <mlennert at club.worldonline.be> wrote:


>>
>> Could you try creating an sqlite table with the same data and use
>> v.in.db on that ?
>> You have to make sure that the sqlite executable (and I think library)
>> are in your path.
>> You can set the PATH in the grass63.bat file:
>> set PATH=%PATH%;PathToSqliteBin;PathToSqliteLib
> 
> Can do that. But the issue is simply trying create points from a DBF. This
> is important for my teaching next semester too. Insisting that students try
> to figure out SQLite isn't very feasible.

The idea is not to tell you to use sqlite from now on, just to test 
whether the problem really is with the dbf driver or whether it is 
something else. Trying it with a different database backend helps 
narrowing down the issue.

Could you also send me the dbf so that I can try ?


> I thought that the dbf error was fixed. If not, it is good to know that
> v.in.db doesn't work currently. We can just use v.in.ascii instead.

Glynn rewrote a section of the dbmi library, i.e. the one treating all 
database interaction (not only dbf), but recently a new bug was 
discovered and I have been able to narrow it down to the dbf driver, but 
not have had more time to work on it since. However, this did not 
involve a windows error message such as you have...

> 
> 
>>
>>>>> Also getting an error on gdal import complainging about a gcs.cvs file
>>>> Haven't used gdal import for a while in wingrass, so will test that.
> 
> Got this dealt with. Interestingly, trying to import a file with an
> incorrect format with v.in.ascii gives the same error as trying to import a
> dbf file with v.in db, using dbf format. I don't know if this helps debug,
> but maybe it is a clue.

Quite probably. What is the incorrect format ?


> 
>>>>> =====
>>>>>
>>>>> ERROR 4: Unable to open EPSG support file gcs.csv.
>>>>> Try setting the GDAL_DATA environment variable to point to the
>>>>> directory containing EPSG csv files.
>>>> Have you tried setting this ?
>>> How would we go about setting this?
>>
>> Try setting it in the grass63.bat file:
>>
>> set GDAL_DATA=
> 
> You mean leave this blank/empty? Or do you mean to point this variable to a
> valid location?

The latter.


>> But is this a GRASS variable or a GDAL variable ?
> 
> I have absolutely no idea.

This questions was directed more to Glynn than to you ;-)

Moritz