3
While you country data seems to cover the whole planet (distinguishable are Cuba to the west, tilted at 90 °, Greenland overly large at the top middle, and something like Sri Lanka to the east, in the middle), your project, or more precisely, your projects coordinate reference system (CRS) covers only a small portion of the globe. While these "restricted" ...
3
I'm one of the maintainers for the solaris project. I tried to reproduce your error in my environment but could not.
If you open an issue in the solaris github repo with the full traceback, and your python/solaris/pyproj/fiona versions, then we would be happy to try to figure out what's going on.
2
How about something like this,
try:
gdf = geopandas.read_file(shape)
except DataIOError as err:
# log error if you want
# log(str(err))
raise TypeError
clip(raster, shape)
Good all try/except
Edit: Just to add some links fiona open doc, geopandas read_file is based on fiona open geopandas io doc.
2
You could shift the features to their correct locations by using the command line tool ogr2ogr. If you wanted to shift all the features at 8 meters at a 45 degree angle (northeast) then use the following code
ogr2ogr shifted_data.shp original_data.shp -dialect sqlite -sql "SELECT ShiftCoords(geometry,5.657,5.657) FROM original_data"
Ogr2ogr is part of ...
2
A RAT is just a table that crosswalks the numeric values contained in an integer raster to descriptive attributes. It is not realistic to have a RAT for a true floating-point raster (eg., elevation) and really does not make much sense to. If one wants to represent a
process as nominal than you just reclassify it into the desired ranges.
A good way to ...
2
According to Solaris Documentation, You have to pass an integer value for crs.
crs (int) – The coordinate reference system for the output GeoDataFrame as an EPSG code integer.
Try to use 4326 instead of 'epsg:4326'.
result_polys = sol.vector.polygon.georegister_px_df(mask2poly,
affine_obj=tile_tfm,
...
2
I haven't found a "nudge" feature. In situations similar to your use case, however, I have:
Selected the feature, then zoomed in significantly to blow up the corner/point I wanted to place precisely, and then used Move feature to move at that scale, before zooming out again.
Created a utility layer, into which I placed precise points, and then used snapping ...
1
In QGIS 3.10.1 the developers put clipping of rasters in the Raster toolbar, in the Extraction section, it is now called "Clip Raster by Mask Layer". In the tool window there is an opportunity to select a CRS for input (or leave source CRS) and output rasters.
Definitely works with different CRS: I clipped a raster in Projected CRS with a mask layer in ...
Only top voted, non community-wiki answers of a minimum length are eligible
