Blog #2
Replies: 4 comments 2 replies
-
Reality Check: State of autoesdaExposureAs I write this on 20 April 2022, autoesda (v0.0.3) is available on conda-forge and PyPI. autoesda was a product of my BScHons(Geoinformatics) research at the University of Pretoria and I gave numerous talks motivating for its development. Getting to this point would not have been possible without the helpful videos in this playlist. I gave a presentation at PyCon ZA 2021 which can be viewed here. I also decided to enter the 2021 GeoforAll student competition – my entry video can be viewed here. This entry subsequently won me the award for the “most promising tool”, and I was invited to present at the 2022 GeoforAll student conference. My presentation can be viewed here. Next StepsThe possibilities are endless with further development of the autoesda library, however I have the following broad goals in mind for the immediate future:
|
Beta Was this translation helpful? Give feedback.
-
Developing a QGIS pluginThe videos in this playlist where very helpful in developing a QGIS plugin. As the autoesda QGIS plugin will require the use of geopandas and its assosciated dependancies, the reqular issues with installing it arises. Using the OSGeo 4W Shell (installed with QGIS) I could install geopandas/fiona/rasterio/GDAL/etc... with the original binary files. This will be necessary to run the plugin on your local computer. Required Software:
The original plan was to include the autoesda source code in the QGIS plugin files, however this seems illogical as if the autoesda library were imported, the plugin would benefit from the updates to the library and changes to the plugin will not need to be made manually. I now need to work on:
The second task of the two is easier said than done. Currently the autoesda python library saves the HTML file to the working folder (not practicle within the QGIS environment). For this reason, I have decided that the change needs to be made within the autoesda Python library itself. The planned changes is to split the current process into two functions. Function 1 will accept the GeoDataFrame (and other parameters) and generate the report by means of an HTML string which it will pass back to the line calling the function. Function 2 will save the HTML string to an actual HTML file. This function will accept the HTML string and a file-path as parameters and its output will be the HTML file saved at the specified location. |
Beta Was this translation helpful? Give feedback.
-
Similar workThroughout the development of the autoesda Python library and QGIS plugin, I have used the following available tools as a guide on what should be included, what improvements can be made, and any other useful information.
The following libraries are also of interest for further development: |
Beta Was this translation helpful? Give feedback.
-
|
Had a look at dask-geopandas today - it would be interesting to see if it would benefit autoesda. |
Beta Was this translation helpful? Give feedback.
-
Useful links |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hello World 👋
Welcome to my blog, I hope to use this platform to informally document my journey as a Geoinformatics student as I develop the autoesda library as part of my research. This blog aims to be a guide for both the general public, as well as a space for me to keep track of my own thoughts. This includes useful links, design principles and aspects of the software development life-cycle that I may be struggling with.
DISCLAIMER: This blog will be extremely subjective and should by no means used as a definitive guide. The inclusion of useful links or the mention of any entity does not equate to endorsement!
Beta Was this translation helpful? Give feedback.
All reactions