d3 celestial stars.14
Reading
This dataset is a single GeoJSON-style record loaded from stars.14.json, with just 2 columns and 1 row. The 'type' column holds the constant value 'FeatureCollection', and the 'features' column was skipped because it is a nested/unknown structure. There is essentially no tabular signal here — the file is a JSON document that needs to be unpacked (likely by exploding the 'features' array) before meaningful analysis is possible.
citing: row_count · column_count · columns · kinds
Charts the summary said to look at first
Show data table
| value | count | share |
|---|---|---|
| FeatureCollection | 1 | 100.0% |
Schema
2 columns| Alerts | ||||
|---|---|---|---|---|
| type | categorical | 0.0% | 1 |
long_tail
imbalance
|
| features | unknown | 0.0% | — |
skipped
|
type
categorical metadata long_tail imbalanceThis column holds a single GeoJSON object-type tag, with the only observed value being "FeatureCollection" across the lone row. Cardinality is 1 and entropy is 0, so it carries no discriminative information. The long_tail and imbalance alerts simply reflect that the column is a constant. Treatment: Drop; constant column with no signal.
- n
- 1
- nulls
- 0 (0.0%)
- unique
- 1
- top_value
- FeatureCollection
- top_rate
- 1
- cardinality
- 1
- entropy
- 0
- entropy_ratio
- 0
features
unknown other skippedThe column is named "features" but saturn skipped profiling it, so its type and contents are unknown. Only one row was observed (n=1) with no nulls, and no unique count or other statistics were computed. Without further evidence the role of this column cannot be determined. Treatment: Re-profile with a larger sample and an appropriate parser before deciding how to use it.
- n
- 1
- nulls
- 0 (0.0%)
- unique
- —