Comments (10)
Yes that's me [jumping up and down]!
from coronadatascraper.
I'm looking into whether to make this an ISO 19115:2013 metadata record or use metadata-json.
This is after all, Vector Spatial Data --> ISO 19115:2013
from coronadatascraper.
@hyperknot, thoughts on this?
from coronadatascraper.
I'm heavily swayed by data.gov Open Data Standards:
Project Open Data Metadata Schema v1.1
I'm somewhat spinning my wheels trying to find a good metadata-json editor. I'd rather not have to edit in raw. I'm looking...
from coronadatascraper.
This is exactly what I was looking for and need!
mdEditor
Let's just say it's in the works after being stalled for the day. :-(
from coronadatascraper.
@lazd I've validated the workflow with mdEditor:
- Import the mdeditor metadata file
- merge
- edit
- export
Think this workflow will work as a collaborative metadata project.
My question: should I upload the metadata.json file to the coronadatascraper repository?
I would think so, just want to check with you, since that's not exactly where the data is.
Should another repository be created just for the data?
(organization: CoronaVirusDataTeam)
from coronadatascraper.
@DavidGeeraerts how often will this metadata file change, what does it look like, and how should we provide it?
from coronadatascraper.
Getting an official metadata record for data.gov is going to take (me) a while. Went back to creating the metadata.md file so you can post on [your] website. I've started a Github organization called "CoronaVirusDataTeam" --that was before the whole Coronavirus Response Data Team)-- and have a repo for docs. In there is the draft for metadata.md. This is a lot of work and I can only do it in chunks as time permits.
Can you provide me with (or update the document):
featureId:
description:
aggregate:
description:
I think I can do the rest of the CSV entries in the format I've laid out. Not sure about the JSON files, haven't looked closely at them.
from coronadatascraper.
featureId
- The ID of the feature this location references (index infeatures.json
's FeatureCOllection)aggregate
- Whether this data source provides aggregate information (i.e. this county-level data was scraped from a state-level source)
from coronadatascraper.
I recommend keeping this simple for now, that's the key for adaptation and future contributors.
I think the ideal timeseries would look like this:
{
"id2:ITX": {
"dates": {
"2020-03-17": {
"cases": 2,
"deaths": 0,
"recovered": 0
},
"2020-03-18": {
"cases": 2,
"deaths": 0,
"recovered": 0
}
},
"source_url": "https://github.com/CSSEGISandData/COVID-19",
"population": 68414135
}
}
Where each date string is a ISO 8601 date and each id is a Country Level ID.
Addressing counties, etc with an id is not a simple task, but I'll think about it. Maybe we can do something like id4:"US-CA-ABCDE" or something. I don't think there is a consistent system for county short codes.
from coronadatascraper.
Related Issues (20)
- tested number is all NA today HOT 4
- Data for Indian States not found HOT 5
- "tested" data for Washoe County, NV is impossible HOT 4
- JHU time series stopped updating 5/9 HOT 1
- Liège in name column in CSV (Tidy Format) file HOT 2
- Add scraper for Orleans Parish, Louisiana (i.e. New Orleans) HOT 6
- France data is off HOT 3
- Some administrative districts(Nenets and Chukotka) are missing in the Russia data, 5/16/2020 HOT 1
- Add scraper for San Francisco HOT 2
- Deaths in Pennsylvania seem to have been updated with tested (?) counts. HOT 11
- timeseries-byLocation.json issue
- IMPORTANT - We are moving to Li -- https://github.com/covidatlas/li HOT 1
- Data not Refreshed - last MAX(date) = 2020-05-27 HOT 2
- 2020.07.03 data missing several featureIds HOT 2
- didn't see data on 07/13 and 07/14 HOT 7
- Change CDS build to pull down reports from Li v1 folder HOT 5
- Issue with Florida Data Numbers HOT 2
- IMPORTANT - We are moving to Li -- https://github.com/covidatlas/li HOT 1
- We have moved to Li -- please open issues over there!
- Updated data in CDS
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from coronadatascraper.