filecoin-plus-large-datasets
filecoin-plus-large-datasets copied to clipboard
[DataCap Application] <OpenData> - <Digital Earth Africa>
Data Owner Name
Digital Earth Africa
What is your role related to the dataset
Other
Data Owner Country/Region
South Africa
Data Owner Industry
Environment
Website
https://www.digitalearthafrica.org/
Social Media
https://www.youtube.com/watch?v=FVmcEaemfmA
Total amount of DataCap being requested
12PiB
Expected size of single dataset (one copy)
1118.3TiB
Number of replicas to store
10
Weekly allocation of DataCap requested
512TiB
On-chain address for first allocation
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
Data Type of Application
Public, Open Dataset (Research/Non-Profit)
Custom multisig
- [ ] Use Custom Multisig
Identifier
No response
Share a brief history of your project and organization
DE Africa will provide a routine, reliable and operational service, using Earth observations to deliver decision-ready products enabling policy makers, scientists, the private sector and civil society to address social, environmental and economic changes on the continent and develop an ecosystem for innovation across sectors.
Is this project associated with other projects/ecosystem stakeholders?
No
If answered yes, what are the other projects/ecosystem stakeholders
No response
Describe the data being stored onto Filecoin
https://registry.opendata.aws/deafrica-mangrove/
https://registry.opendata.aws/deafrica-landsat/
https://registry.opendata.aws/deafrica-chirps/
https://registry.opendata.aws/deafrica-wofs/
https://registry.opendata.aws/deafrica-geomad/
https://registry.opendata.aws/deafrica-coastlines/
https://registry.opendata.aws/deafrica-sentinel-1/
https://registry.opendata.aws/deafrica-alos-jers/
https://registry.opendata.aws/deafrica-crop-extent/
https://registry.opendata.aws/deafrica-fractional-cover/
Where was the data currently stored in this dataset sourced from
AWS Cloud
If you answered "Other" in the previous question, enter the details here
No response
If you are a data preparer. What is your location (Country/Region)
Singapore
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
The data is first stored locally for collation, then the car file is generated through boostx and the corresponding deal is executed through boost.
If you are not preparing the data, who will prepare the data? (Provide name and business)
No response
Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution.
The object I'm serving wants to store a copy of this data.
Please share a sample of the data
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-input-datasets/gmw/
Total Objects: 14
Total Size: 3.1 GiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-landsat/
Total Objects: 32932921
Total Size: 717.6 TiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-input-datasets/rainfall_chirps_daily/
Total Objects: 31166
Total Size: 15.6 GiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-services/coastlines/
Total Objects: 29
Total Size: 4.7 GiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-services/gm_s2_annual/
Total Objects: 422837
Total Size: 58.6 TiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-services/wofs_ls/
Total Objects: 7040142
Total Size: 3.4 TiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-sentinel-1/
Total Objects: 11313854
Total Size: 254.6 TiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-input-datasets/alos_palsar_mosaic/
Total Objects: 12648
Total Size: 3.7 TiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-services/crop_mask/
Total Objects: 19284
Total Size: 195.0 GiB
aws s3 ls --region af-south-1 --no-sign-request s3://deafrica-services/fc_ls/
Total Objects: 14457313
Total Size: 87.5 TiB
Confirm that this is a public dataset that can be retrieved by anyone on the Network
- [ ] I confirm
If you chose not to confirm, what was the reason
No response
What is the expected retrieval frequency for this data
Yearly
For how long do you plan to keep this dataset stored on Filecoin
1.5 to 2 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China, Africa, North America, South America, Europe, Australia (continent)
How will you be distributing your data to storage providers
Cloud storage (i.e. S3)
How do you plan to choose storage providers
Slack, Big Data Exchange, Partners
If you answered "Others" in the previous question, what is the tool or platform you plan to use
No response
If you already have a list of storage providers to work with, fill out their names and provider IDs below
f02838518 akcd4040 [email protected] bitwind Russia
f02832475 Lee [email protected] HS88 Thailand
f02859053 miaozi [email protected] chainup USA
f02830321 OriginStorage [email protected] OriginStorage Vietnam
f02837226 Jerry [email protected] kinghash Britain
How do you plan to make deals to your storage providers
boost
If you answered "Others/custom tool" in the previous question, enter the details here
No response
Can you confirm that you will follow the Fil+ guideline
Yes
If you are a data preparer. What is your location (Country/Region) None
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details? No response
If you are not preparing the data, who will prepare the data? (Provide name and business) No response
Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution. No response
How do you plan to make deals to your storage providers No response
If you answered "Others/custom tool" in the previous question, enter the details here No response
Please add the answers of questions listed above in the application.
This is a multi-set, we agreed as a community not to allow this. Second to that its already stored.
If you are a data preparer. What is your location (Country/Region) Singapore If you are a data preparer, how will the data be prepared? Please include tooling used and technical details? The data is first stored locally for collation, then the car file is generated through boostx and the corresponding deal is executed through boost. If you are not preparing the data, who will prepare the data? (Provide name and business) No response Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution. The object I'm serving wants to store a copy of this data. How do you plan to make deals to your storage providers boost If you answered "Others/custom tool" in the previous question, enter the details here No response @Sunnyiscoming
Hello, per the https://github.com/filecoin-project/notary-governance/issues/922 for Open, Public Dataset applicants, please complete the following Fil+ registration form to identify yourself as the applicant and also please add the contact information of the SP entities you are working with to store copies of the data.
This information will be reviewed by Fil+ Governance team to confirm validity and then the application will be allowed to move forward for additional notary review.
SP List provided: [{"providerID": "f02838518","City": "XYZ", "Country": "Russia", "SPOrg","bitwind"}, {"providerID": "f02832475","City": "XYZ", "Country": "Thailand", "SPOrg","HS88"}, {"providerID": "f02859053","City": "XYZ", "Country": "USA", "SPOrg","chainup"}, {"providerID": "f02830321","City": "XYZ", "Country": "Vietnam", "SPOrg","OriginStorage"}, {"providerID": "f02837226","City": "XYZ", "Country": "Britain", "SPOrg","kinghash"},]
KYC has been completed.
Deleting comment
@Sunnyiscoming hasn't the permissions to post this comment.
Please, contact the assignee of this issue.
Datacap Request Trigger
Total DataCap requested
12 PiB
Expected weekly DataCap usage rate
512 TiB
Client address
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
DataCap Allocation requested
Multisig Notary address
f02049625
Client address
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
DataCap allocation requested
256TiB
Id
ec265ddf-61b0-490f-a244-31c03daaa7be
This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open.
-- Commented by Stale Bot.
The project is currently in progress.
SP List provided: [{"providerID": "f02838518","City": "XYZ", "Country": "Russia", "SPOrg","bitwind"}, {"providerID": "f02832475","City": "XYZ", "Country": "Thailand", "SPOrg","HS88"}, {"providerID": "f02859053","City": "XYZ", "Country": "USA", "SPOrg","chainup"}, {"providerID": "f02830321","City": "XYZ", "Country": "Vietnam", "SPOrg","OriginStorage"}, {"providerID": "f02837226","City": "XYZ", "Country": "Britain", "SPOrg","kinghash"},] Support for the first round, and will check the SP seal information later.
Request Proposed
Your Datacap Allocation Request has been proposed by the Notary
Message sent to Filecoin Network
bafy2bzaceat74q6tp5mlroimkbrwcwzfznkbhqqw4csqq5e4zb765bumvwp42
Address
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
Datacap Allocated
256.00TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
ec265ddf-61b0-490f-a244-31c03daaa7be
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceat74q6tp5mlroimkbrwcwzfznkbhqqw4csqq5e4zb765bumvwp42
Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network
bafy2bzaceb6726pgidxcdkkshcrcprosazyuig5t3h4vgiswn2emyqg3hrqus
Address
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
Datacap Allocated
256.00TiB
Signer Address
f1tfg54zzscugttejv336vivknmsnzzmyudp3t7wi
Id
ec265ddf-61b0-490f-a244-31c03daaa7be
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb6726pgidxcdkkshcrcprosazyuig5t3h4vgiswn2emyqg3hrqus
This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open.
-- Commented by Stale Bot.
The project is currently in progress.
This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open.
-- Commented by Stale Bot.
in progress.
@clriesco Hi,dear administrator,there seems to be something wrong with the robot, it does not jump out normally, please help to deal with it.
@dos2un1x Issue number 2301 datacap remaining / datacap allocated: 36.18% - doesn't need more allowance
checker:manualTrigger
DataCap and CID Checker Report Summary[^1]
Storage Provider Distribution
✔️ Storage provider distribution looks healthy.
Deal Data Replication
✔️ Data replication looks healthy.
Deal Data Shared with other Clients[^3]
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Full report
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard.
@dos2un1x
Issue number 2301 datacap remaining / datacap allocated: 36.18% - doesn't need more allowance
Is there a problem? The report looks normal. @clriesco
There is no problem. Our records show that you have 101842264522752 bytes left for your address f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli. If you have consumed all your current allowance, it means that records are outdated and they will refresh soon.
DataCap Allocation requested
Request number 3
Multisig Notary address
f02049625
Client address
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
DataCap allocation requested
1PiB
Id
fc02ce67-0421-4fe7-9b97-c4e5a7d33e0d
Request Proposed
Your Datacap Allocation Request has been proposed by the Notary
Message sent to Filecoin Network
bafy2bzacedmnnd6slbmnuglw4l5qrg2q3c6waoxrkp6zhhom2wnu2nsgdloqe
Address
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
Datacap Allocated
1.00PiB
Signer Address
f1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i
Id
fc02ce67-0421-4fe7-9b97-c4e5a7d33e0d
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedmnnd6slbmnuglw4l5qrg2q3c6waoxrkp6zhhom2wnu2nsgdloqe
Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network
bafy2bzaceb5ikoirqtuwpwdyaabcahtvugs577i5koksriw7nyhz7fozfhwlc
Address
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
Datacap Allocated
1.00PiB
Signer Address
f1jyvhxp4kmwreo22ke4itspraznpudw3uqaink5i
Id
fc02ce67-0421-4fe7-9b97-c4e5a7d33e0d
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb5ikoirqtuwpwdyaabcahtvugs577i5koksriw7nyhz7fozfhwlc
DataCap Allocation requested
Request number 3
Multisig Notary address
f02049625
Client address
f1zqri4vfrqpqennwtn2naqloftv3lqurlvad2vli
DataCap allocation requested
1PiB
Id
3325efd1-0182-4032-81fd-a5279aeb549b
checker:manualTrigger
DataCap and CID Checker Report Summary[^1]
Storage Provider Distribution
✔️ Storage provider distribution looks healthy.
Deal Data Replication
⚠️ 100.00% of deals are for data replicated across less than 4 storage providers.
Deal Data Shared with other Clients[^3]
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Full report
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard.