Skip to content
This repository has been archived by the owner on Jul 18, 2024. It is now read-only.

[DataCap Application] NEXRAD Dataset #1062

Closed
Megan008 opened this issue Oct 10, 2022 · 27 comments
Closed

[DataCap Application] NEXRAD Dataset #1062

Megan008 opened this issue Oct 10, 2022 · 27 comments
Assignees
@simonkim0515 @galen-mcandrew @raghavrmadya @Kevin-FF-USA @Sunnyiscoming
Labels
error

Comments

@Megan008
Copy link

Megan008 commented Oct 10, 2022 •
edited
Loading

Large Dataset Notary Application

To apply for DataCap to onboard your dataset to Filecoin, please fill out the following.

Core Information

  • Organization Name: Public Data-NEXRAD dataset
  • Website / Social Media:https://registry.opendata.aws/noaa-nexrad/
  • Total amount of DataCap being requested (between 500 TiB and 5 PiB):5PiB
  • Weekly allocation of DataCap requested (usually between 1-100TiB):200TiB
  • On-chain address for first allocation:f1xi564ajokw3ocdn2kslwvwhzvvusqyijinvau7i

Please respond to the questions below by replacing the text saying "Please answer here". Include as much detail as you can in your answer.

Project details

Share a brief history of your project and organization.

I have participated in some projects and hackathon. I have experience on it.

What is the primary source of funding for this project?

Personal income.

What other projects/ecosystem stakeholders is this project associated with?

No.

Use-case details

Describe the data being stored onto Filecoin

Real-time and archival data from the Next Generation Weather Radar (NEXRAD) network.

Where was the data in this dataset sourced from?

https://registry.opendata.aws/noaa-nexrad/

Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this.

s3://noaa-nexrad-level2/1992/08/24/KMLB/KMLB19920824_224809.gz
s3://noaa-nexrad-level2/2021/01/01/KBBX/KBBX20210101_135953_V06_MDM

Confirm that this is a public dataset that can be retrieved by anyone on the Network (i.e., no specific permissions or access rights are required to view the data).


Yes, it is AWS open dataset.

What is the expected retrieval frequency for this data?

Not very often.

For how long do you plan to keep this dataset stored on Filecoin?

2 years. Then I'll extend the time if it is successful.

DataCap allocation plan

In which geographies (countries, regions) do you plan on making storage deals?

North america; Korea; China.

How will you be distributing your data to storage providers? Is there an offline data transfer process?

75% data will be distributed by offline data transfer. Other data will use online transfer for distributing with storage providers who close to me.

How do you plan on choosing the storage providers with whom you will be making deals? This should include a plan to ensure the data is retrievable in the future both by you and others.

I would let 1 sp who used to cooperate with me for this deal. Now I'm chatting with other sps.

How will you be distributing deals across storage providers?

I have communicated with 4 sp. In first time, I will divide 1/4 data to each sp. If I find out more sp, I will decrease the percentage of deals to them --- for decentralized storage.

Do you have the resources/funding to start making deals as soon as you receive DataCap? What support from the community would help you onboard onto Filecoin?

Yes.
@large-datacap-requests
Copy link

Thanks for your request!
❗ We have found some problems in the information provided.
We could not find any Web site or social media info in the information provided
We could not find any Region in the information provided

Please, take a look at the request and edit the body of the issue providing all the required information.

@large-datacap-requests
Copy link

Thanks for your request!

Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!

@large-datacap-requests
Copy link

Thanks for your request!
Everything looks good. 👌

A Governance Team member will review the information provided and contact you back pretty soon.

@raghavrmadya
Copy link
Collaborator

Please share the SPs you plan to work with

1 similar comment
@raghavrmadya
Copy link
Collaborator

Please share the SPs you plan to work with

@Megan008
Copy link
Author

Megan008 commented Oct 28, 2022 •
edited
Loading

Thanks @raghavrmadya , good to have your reply! We previously contacted 7-8 SPs from all over the world who are eager to store data. There are 5 SPs, including f023495 and f0508988, who are willing to participate in the first round of sealing. I am also continuing to contact more SPs on BDE platform in hopes of cooperating.

@simonkim0515 simonkim0515 self-assigned this Nov 28, 2022
@simonkim0515
Copy link
Collaborator

Datacap Request Trigger

Total DataCap requested

5PiB

Expected weekly DataCap usage rate

200TiB

Client address

f1xi564ajokw3ocdn2kslwvwhzvvusqyijinvau7i

@large-datacap-requests
Copy link

large-datacap-requests bot commented Nov 28, 2022 •
edited
Loading

DataCap Allocation requested

Multisig Notary address

f02049625

Client address

f1xi564ajokw3ocdn2kslwvwhzvvusqyijinvau7i

DataCap allocation requested

100TiB

Id

34edeb10-6602-4f7d-af23-33bea47acf0f

@galen-mcandrew galen-mcandrew added the cg:stale Client Growth, No recent activity label Jan 31, 2023
@cryptowhizzard cryptowhizzard mentioned this issue Feb 1, 2023
Closed
@cryptowhizzard
Copy link

#1013 -> Abuse ( CID sharing )

@MEIYAN666
Copy link

checker:manualTrigger

@filplus-checker-app
Copy link

DataCap and CID Checker Report Summary1

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients2

⚠️ CID sharing has been observed. (Top 3)

Full report

Click here to view the full report.

Footnotes

  1. To manually trigger this report, add a comment with text checker:manualTrigger ↩

  2. To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ... ↩

@large-datacap-requests
Copy link

Thanks for your request!

Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!

1 similar comment
@large-datacap-requests
Copy link

Thanks for your request!

Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Jul 22, 2023
@Megan008
Copy link
Author

OK, I know.

@cryptowhizzard
Copy link

checker:manualTrigger

@filplus-checker-app
Copy link

DataCap and CID Checker Report Summary1

Retrieval Statistics

⚠️ All retrieval success ratios are below 1%.

  • Overall Graphsync retrieval success rate: 0.00%
  • Overall HTTP retrieval success rate: 0.00%
  • Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients2

⚠️ CID sharing has been observed. (Top 3)

Full report

Click here to view the CID Checker report.
Click here to view the Retrieval Dashboard.
Click here to view the Retrieval report.

Footnotes

  1. To manually trigger this report, add a comment with text checker:manualTrigger ↩

  2. To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ... ↩

@github-actions github-actions bot removed the Stale label Jul 26, 2023
@Megan008
Copy link
Author

Megan008 commented Aug 4, 2023

checker:manualTrigger

@filplus-checker-app
Copy link

DataCap and CID Checker Report Summary1

Retrieval Statistics

  • Overall Graphsync retrieval success rate: 0.00%
  • Overall HTTP retrieval success rate: 1.30%
  • Overall Bitswap retrieval success rate: 0.00%

Storage Provider Distribution

✔️ Storage provider distribution looks healthy.

Deal Data Replication

✔️ Data replication looks healthy.

Deal Data Shared with other Clients2

⚠️ CID sharing has been observed. (Top 3)

Full report

Click here to view the CID Checker report.
Click here to view the Retrieval Dashboard.
Click here to view the Retrieval report.

Footnotes

  1. To manually trigger this report, add a comment with text checker:manualTrigger ↩

  2. To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ... ↩

@cryptowhizzard
Copy link

Scherm­afbeelding 2023-08-04 om 11 19 08

As per the CID checker , most SP's are involved in Abuse / CID sharing. Those who are not have retrieval disabled.

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Aug 15, 2023
@github-actions
Copy link

This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2023
@large-datacap-requests Large datacap requests
Copy link

Thanks for your request!
❗ We have found some problems in the information provided.
We could not find Website / Social Media field in the information provided
We could not find Total amount of DataCap being requested (between 500 TiB and 5 PiB) field in the information provided
We could not find Weekly allocation of DataCap requested (usually between 1-100TiB) field in the information provided
We could not find On-chain address for first allocation field in the information provided
We could not find Data Type of Application field in the information provided

Please, take a look at the request and edit the body of the issue providing all the required information.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@simonkim0515 simonkim0515

@galen-mcandrew galen-mcandrew

@raghavrmadya raghavrmadya

@Kevin-FF-USA Kevin-FF-USA

@Sunnyiscoming Sunnyiscoming

Labels
error
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@cryptowhizzard @fabriziogianni7 @simonkim0515 @galen-mcandrew @raghavrmadya @Kevin-FF-USA @Sunnyiscoming @BobbyChoii @MEIYAN666 @Megan008