Skip to content
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

WRI-CAIT - S3 - Mapping #95

Open
S-AI-F opened this issue May 17, 2021 · 2 comments
Open

WRI-CAIT - S3 - Mapping #95

S-AI-F opened this issue May 17, 2021 · 2 comments
Assignees
Labels
data-mapping This issue or pull request already exists

Comments

@S-AI-F
Copy link
Member

S-AI-F commented May 17, 2021

Once mapped json file stored in github repository is validated, you can update your mapping script by replacing input/output data with s3 buckets.

You have a specific folder by data source where you can put raw data and mapped generated data (in staging folder).

Doc:

@S-AI-F S-AI-F transferred this issue from OpenGeoScales/ogs-connectors May 17, 2021
@S-AI-F S-AI-F added the data-mapping This issue or pull request already exists label May 17, 2021
@CJeannesson
Copy link
Member

This has been done, but without relying on a Python script.

@S-AI-F
Copy link
Member Author

S-AI-F commented Jun 3, 2021

Hi @CJeannesson
Can you change please the mapping script by reading raw data from S3 and writing mapped data in S3?
Since, you are the first to to make this change, can you write a small tutorial of connecting python to S3 to share with the team?
Here is the dedicated wiki page: https://github.com/OpenGeoScales/ogs-connectors/wiki/Datalake-AWS-S3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-mapping This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants