New answers tagged import
To expand on David Bitner's answer, here's an example ogr2ogr instruction demonstrating an optional OGR SQL clause to rename fields from a source dataset (shapefile in this case) before they are brought into a target dataset (a PostGREsql table): ogr2ogr -f "PostGreSQL" PG:"host=127.0.0.1 user=YourUser dbname=YourDB password=YourPass" ...
As Andre mentioned in GRASS your LOCATION coordinate system must match the coordinate system of the data being input. You can create a new LOCATION when you input the original tiff file by using the location= parameter. For example: r.in.gdal input=E:\cdnh43e_v1.1r1.tif output=cdnh43e_v1 location=LCC Now run: g.region raster=cdnh43e_v1 to set your ...
In GRASS, location and dataset should share the same projection. On-the-fly-reprojection is only available in advanced GIS packages like QGIS or Arcgis. To change the projection, use gdalwarp to a different filename outside of GRASS.
You have about three options: (Best) In the GRASS plugin, open the GRASS shell - it's at the top of the Module tree. Type into the command line the r.in.gdal command, and include the location=... parameter. This will create a new LOCATION based on your custom CRS, and import the raster there. You'll then need r.proj to reproject your other layers into this ...
Top 50 recent answers are included