[GRASS-user] [ERROR 4:unable to open EPSG support file gcs.csv]

[Ang Sherpa]

Thanks,
fixed by adding
os.environ['GDAL_DATA'] = r'C:\Program Files\GRASS GIS 7.2.0\share\gdal' at
the beginning of the script.

*Best,*
*Ang Dawa Sherpa*


On Sat, Mar 25, 2017 at 6:14 PM, Helmut Kudrnovsky <hellik at web.de> wrote:

> Ang Sherpa wrote
> > Thanks for attention,
> >
> > Tried everything I could. Any solution to incorporate %GDAL_DATA% in the
> > script, other than to manually adding GDAL_DATA path in system variable?
> >
> >
> >
> > *Best,*
> > *Ang Dawa Sherpa*
> >
> >
> > On Sat, Mar 25, 2017 at 4:02 PM, Helmut Kudrnovsky <
>
> > hellik@
>
> > > wrote:
> >
> >> Ang Sherpa wrote
> >> > Hi users,
> >> >
> >> > When I tried adding C:\Program Files\GRASS GIS 7.2.0\share\gdal to the
> >> > system path with following line of code, it doesnot work as expected.
> >> Am
> >> I
> >> > missing something?
> >> > My code is
> >> > new_path = r'C:\Program Files\GRASS GIS 7.2.0\share\gdal'
> >> > os.environ['PATH'] += os.pathsep + new_path
> >> >
> >> > Still this error persist.
> >> > 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.
> >> > ERROR: Unknown EPSG code 32645
> >> >
> >> > *Best,*
> >> > *Ang Dawa Sherpa*
> >> >
> >> > On Tue, Mar 21, 2017 at 3:36 PM, Ang Sherpa <
> >>
> >> > angsherpa232@
> >>
> >> > > wrote:
> >> >
> >> >> Yes, gcs.csv exists in both machine. Well, I reinstalled Grass 7.2
> and
> >> it
> >> >> worked.
> >> >> Thanks.
> >> >>
> >> >> *Regards,*
> >> >> *Ang Dawa Sherpa*
> >> >> *GIS technician - Irrigation Master Plan*
> >> >> *WRPPF - DOI, Nepal Government*
> >> >> *Lalitpur*
> >> >> *contact: 984 007 3861*
> >> >>
> >> >> On Tue, Mar 21, 2017 at 3:23 PM, Helmut Kudrnovsky <
> >>
> >> > hellik@
> >>
> >> > > wrote:
> >> >>
> >> >>> Ang Sherpa wrote
> >> >>> > Thanks Helmut,
> >> >>> >
> >> >>> > I am using standalone-winGRASS 7.2.0
> >> >>> > In both my PC and laptop when: echo %GDAL_DATA% is executed in
> >> >>> > winGRASS-console it shows the same location:
> >> >>> >
> >> >>> > c:\Program Files\GRASS GIS 7.2.0\Share\gdal
> >> >>>
> >> >>> could you have a look if gcs.csv lives in the folder above?
> >> >>>
> >> >>> may you re-install your winGRASS standalone-winGRASS 7.2.0?
> >> >>> may you try OSGeo4W-winGRASS 7.2.0 (https://trac.osgeo.org/osgeo4w/
> )?
> >> >>>
> >> >>> can't reproduce the error here at the moment.
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> -----
> >> >>> best regards
> >> >>> Helmut
> >> >>> --
> >> >>> View this message in context: http://osgeo-org.1560.x6.nabbl
> >> >>> e.com/ERROR-4-unable-to-open-EPSG-support-file-gcs-csv-tp531
> >> >>> 3117p5313354.html
> >> >>> Sent from the Grass - Users mailing list archive at Nabble.com.
> >> >>> _______________________________________________
> >> >>> grass-user mailing list
> >> >>>
> >>
> >> > grass-user at .osgeo
> >>
> >> >>> https://lists.osgeo.org/mailman/listinfo/grass-user
> >> >>
> >> >>
> >> >>
> >> >
> >> > _______________________________________________
> >> > grass-user mailing list
> >>
> >> > grass-user at .osgeo
> >>
> >> > https://lists.osgeo.org/mailman/listinfo/grass-user
> >>
> >> AFAIK adding the gdal related folder to %PATH% doesn't help.
> >>
> >> As mentioned in the error message, the variable %GDAL_DATA%
> >> should be defined in your script.
> >>
> >>
> >>
> >> -----
> >> best regards
> >> Helmut
> >> --
> >> View this message in context: http://osgeo-org.1560.x6.
> >> nabble.com/ERROR-4-unable-to-open-EPSG-support-file-gcs-
> >> csv-tp5313117p5314199.html
> >> Sent from the Grass - Users mailing list archive at Nabble.com.
> >> _______________________________________________
> >> grass-user mailing list
> >>
>
> > grass-user at .osgeo
>
> >> https://lists.osgeo.org/mailman/listinfo/grass-user
> >>
> >
> > _______________________________________________
> > grass-user mailing list
>
> > grass-user at .osgeo
>
> > https://lists.osgeo.org/mailman/listinfo/grass-user
>
> Are you running your python script inside or outside a GRASS session?
>
> Inside a GRASS session of standalone or osgeo4w wingrass, %GDAL_DATA% is
> already defined.
>
> If outside, %GDAL_DATA% may need to be defined when GDAL comes in.
>
> Have you maybe multiple gdal installations on your system?
>
> At
>
> https://grasswiki.osgeo.org/wiki/GRASS_and_Python
>
> there is
>
>
>
> -----
> best regards
> Helmut
> --
> View this message in context: http://osgeo-org.1560.x6.
> nabble.com/ERROR-4-unable-to-open-EPSG-support-file-gcs-
> csv-tp5313117p5314213.html
> Sent from the Grass - Users mailing list archive at Nabble.com.
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20170326/cfc23b57/attachment.html>