My blog

Note. You will evaluate on  16.png and 1.png that expressing a problem about .sr. operation related to module error.Thus,I will wait for solutions Ekrem Erkuş Geophysics Engineer/TURKEY Datalink: https://hatarilabs.com/ih-en/how-to-create-a-geospatial-groundwater-model-with-modflow-and-flopy

  Datalink: https://hatarilabs.com/ih-en/river-well-aquifer-geospatial-groundwater-flow-model-with-voronoi-mesh-tutorial

We witness frequently thistype module problems about cartopy; import cartopy.crs as ccrs import cartopy.feature as cfeature  I sign to alternative condition of Basemap for such problems.Thus,I tested example including a comparison; Source link: https://ocefpaf.github.io/python4oceanographers/blog/2013/09/23/cartopy/ Test conclusion with basemap: Yes.Thus,we can express that very useful basemap solution for users witnessing thistype module problems about cartopy😐 Datalink: https://github.com/ocefpaf/2016-Python-course-CBO Ekrem Erkuş Geophysics Engineer/TURKEY

 I can express an ordinary problem about gdal module of various person for geospatial mapping field.Where,main matter of users an error syntax as a conclusion of "import gdal" compilation😐 In the other hand,understanding commonly confusions about using gdal as a comparison with successful conclusions of a compilation as  "from osgeo import gdal" 😑 Thus,I approved explanation via an example.Firstly,we can observe examples of using as "import gdal" compilation.For example; http://www2.geog.ucl.ac.uk/~plewis/geogg122_current/_build/html/Chapter4_GDAL/GDAL_Python_bindings.html And,my compilation conclusions code as a whole(Note.Where,I focused an error chapter based on module.So,I didn't care disability conditions due to some external files of program); Yes,you are right,I used "from osgeo import gdal" instead of "import gdal"!!!Thus,I will suggest that you must have satisfying module installation capabilities based on gdal and librar