You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I am new to machine learning and am finding it challenging to understand how to utilize the features from your Encoder in my application. It would be beneficial if someone could provide an example of how to run predictions without QGIS. Thanks a lot for future replies!
The text was updated successfully, but these errors were encountered:
You may refer to the GeoSAM-Image-Encoder Python package documentation for more information. This package is part of the Geo-SAM project and is a standalone Python package that does not depend on QGIS. This package allows you to encode remote sensing images into features that can be recognized by Geo-SAM using a remote server, such as Colab, AWS, Azure or your own HPC.
The prediction process must currently be performed in QGIS. We may provide a standalone script in the future for cases where the required prompts are already available. Another option is to use samgeo, which is a pure python package developed by Qiusheng Wu
@Fanchengyan Thank you very much for your answer! Yes, I figured out how to run the encode script for any file outside of QGIS - the only mystery left is how to run predictions for the obtained features outside of QGIS. This will allow the use of the obtained features not only in QGIS but also in any other web applications.
Before this, I already explored the samgeo project, but its main drawback is that it does not allow for on-the-fly predictions for images. The feature generation process takes quite a lot of time in samgeo, and caching these results does not seem feasible.
Hello! I am new to machine learning and am finding it challenging to understand how to utilize the features from your Encoder in my application. It would be beneficial if someone could provide an example of how to run predictions without QGIS. Thanks a lot for future replies!
The text was updated successfully, but these errors were encountered: