-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardization #6
Comments
Good news, GeoSlicer is now open source! Check it out https://github.com/petrobras/GeoSlicer Thanks! |
Hey @fbordignon, I'm glad to hear you find this useful! Technically I am the only maintainer of the project so "we" would be happy have input on improving the codebase including METADATA and more standardization. What do you think would be the best way, is it something you could propose through a pull request or should we have an online discussion about it first? /L |
@LukasMosser thanks for your reply. We are definitely working on this. The idea is to generate metadata to automate the listing and downloading of the datasets. I am assigning this issue to someone in our team. We will likely generate a pull request and we can discuss/work based on it. Is that good? |
Sounds good to me! |
Great work on this library! I am interested in integrating the download into GeoSlicer with an auto-generated GUI. But for that, we would propose some type of standarization of the METADATA and download process via virtual functions implemented by each dataset. Would that be something that you guys believe could be integrated? I believe we can define an easy to follow standard now that there are a few datasets.
Soon GeoSlicer will be published as opensource as well, so we can all benefit from this integration!
The text was updated successfully, but these errors were encountered: