Below is an example JSON representation of a WeaveJsonDataSet object.
This example illustrates the need to specify keyType by showing that record keys referring
to different things can have identical string representations ("25" could refer to a state or a person).
{
columns: {
"22": {"title": "State name", "keyType": "state fips", "dataType": "string"},
"23": {"title": "Population", "year": "2000", "keyType": "state fips", "dataType": "number"},
"71": {"title": "Name", "keyType": "person id", "dataType": "string"},
"72": {"title": "Age", "keyType": "person id", "dataType": "number"},
"73": {"title": "State", "keyType": "person id", "dataType": "state fips"}
},
records: {
"state fips": {
"01": {"22": "Alabama", "23": 4452000},
"09": {"22": "Connecticut", "23": 3412000},
"25": {"22": "Massachusetts", "23": 3636000},
"37": {"22": "North Carolina", "23": 8080000}
},
"person id": {
"25": {"71": "Alice", "72": 31, "73": "01"},
"22": {"71": "Bob", "72": 43, "73": "09"},
"37": {"71": "Cindy", "72": 23, "73": "01"},
"73": {"71": "Dave", "72": 60, "73": "25"},
"5": {"71": "Eugene", "72": 38, "73": "25"}
}
}
}