New answers tagged grids
I don't know why "Feature to Raster" doesn't work, but found out that "Point to Raster" does! I just used my Shape-Layer as in-feature, the height as value field, MEAN for cell_assignment (That's the one for DEMs, right!?) and my wanted cellsize. Maybe this will help anyone in the future... :)
I think what you need is to geo-reference your data. Here's a link: http://docs.qgis.org/2.2/en/docs/user_manual/plugins/plugins_georeferencer.html and I'm sure ARCgis has something similar...as does Python+gdal, and any legitimate GIS program. The basic problem is that your coordinate system is totally non standard so doing a projection change will not ...
An oblique mercator projection might solve your issue. See this Q&A for details: Using customized Coordinate System for Archaeological site data
I can tell you the answer for the second question: How to show UTM-coordinates in the lower right corner. In leaflet the internal coordinate system is always longitude/latitude as far as I know, and you have to transform every time you need to work with your data. First make sure you have installed proj4.js and proj4leaflet.js. To show your coordinates you ...
You can do the rescaling using gdalwarp and Geotiff for temporary output: gdalwarp -overwrite -of GTiff -tr 0.000241 0.000241 D:\Download\NEU\asc.txt D:/Download/NEU/asc-square.tif and then convert to ASCII grid: gdal_translate -of AAIGrid D:/Download/NEU/asc-square.tif D:/Download/NEU/asc-square.asc Alternatively, you can use gdal_translate with ...
QGIS seems to default to the Golden Surfer version of AAIGrid is pixels are not square but puts out a "traditional" ASC header if they are square. Most systems will not support the dx/dy options (apart from Golden Surfer). You are also right that forcing the cell size sets the cellsize to be the X cell size and that could cause distortion. Alternatively, ...
Top 50 recent answers are included