Not Found In Epsg Support Files

Posted on by admin

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 1: Translating source or target SRS failed: EPSG:4326. I am using GDAL 1.9.0, released 2011/12/29. I will be grateful for any help. Type the EPSG code. Next, add your EPSG code. A full list of codes can be found at Spatial Reference. Again, most GCP maps are in WGS84 or one of the NAD83 (typically not HARN, CSRS, or NAD27) State Plane Coordinate Systems.

I'm trying out the Docker toolchain.
https://github.com/t3r
Foundhttp://wiki.flightgear.org/Howto:Docker ... _toolchain
I downloaded the elevation from viewfinderpanoramas
http://viewfinderpanoramas.org/dem3/N30.zip
when running I get this. Docker is running on W10 if it is relevant.
Code: Select all
bash-4.3$ gdalchop work/STRM-3 SRTM-source/*.hgt
ERROR 6: EPSG PCS/GCS code 4326 not found in EPSG support files. Is this a valid
EPSG coordinate system?
ERROR 6: No translation for an empty SRS to PROJ.4 format is known.
Segmentation fault
bash-4.3$ srtmchop

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Sign up New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comments

commented Dec 4, 2014

Anaconda's version of GDAL doesn't work as expected. Normally programs such as gdalwarp just work. In the case of Anaconda's, the installation is either missing, or hiding some important data files.

This is resolved by following the instructions in the error (export GDAL_DATA=/path/to/gcs.csv), but it becomes cumbersome when creating multiple conda environments, all requiring a manual tweak to work correctly.

Is there a way to include gcs.csv in the Anaconda distribution without having to manually define GDAL_DATA?

commented Dec 8, 2014

Running gdal-config --datadir shows where GDAL searches for gcs.csv. In the case of a conda installed GDAL in an environment called 'gdal', the result is:

which does not exist.

commented Dec 10, 2014

This can be easily solved by Continuum by adding a couple of lines to the build.sh recipe, see e.g. the last three lines in this file. Then you don't need to set up a variable.

Not Found In Epsg Support Files

commented Apr 12, 2015

@tswicegood thanks for talking with me today at PyCon I got some great information from you guys.

I'd love to find a solution (and test @jgomezdans proposed solution) for this and submit it (ideally as a PR to the actual recipe).

  • Am I missing the source of the recipe for this?

If I cant get the source recipe why would I not just try and fix the recipe here and always use the 'conda' channel? What is the relationship between Anaconda, binstar(defaults), and binstar(conda)?

Not Found In Epsg Support Files Online

Closed

commented May 14, 2015

Epsg 9840 Not Found In Epsg Support Files

GDAL has been repackaged into libgdal and gdal (the python bindings).
These changes were introduced for gdal 1.11.2 build number >= 2 on windows and >= 1 on unix.
This repackaging should resolve all outstanding issues that I've seen for anaconda's gdal. If there are other problems, please open a new issue.

I will eventually work on updating the recipes in conda-recipes to reflect this new packaging of gdal.

added a commit to quintusdias/glymur that referenced this issue Dec 26, 2015

Refactor printing of geotiff UUID box
Open

commented Mar 2, 2017•
edited

To fix this error do the following steps.

  • go to the activate.d folder of your conda env, this should be something like:

C:ProgramDataAnaconda2envs ENV_NAME etccondaactivate.d

  • Then create a new bat file with the next text:

This new bat file will replace the text with double quotation marks and a slash after dp0, that is shown as follow

bye!

Epsg Pcs/gcs Code Not Found In Epsg Support Files

Open

Epsg Pcs/gcs Code 4326 Not Found In Epsg Support Files

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment