data trove submarine cable map
Reading
This dataset is a GeoJSON FeatureCollection describing global submarine cables, stored as a single-row JSON file where the entire dataset is packed into nested fields. The top-level metadata columns ('name' and 'type') each contain exactly one value — 'submarine_cables' and 'FeatureCollection' respectively — confirming this is a wrapper structure rather than a flat table. The real analytical content is buried inside the 'features' and 'crs' columns, which were skipped during profiling because they contain complex nested objects (geometries, cable properties, coordinates). To get meaningful insight, the 'features' array needs to be unpacked into individual cable records before any visualization or analysis can begin.
citing: row_count · column_count · columns[name].top_value · columns[type].top_value · columns[features].alerts · columns[crs].alerts
Charts the summary said to look at first
Show data table
| value | count | share |
|---|---|---|
| submarine_cables | 1 | 100.0% |
Show data table
| value | count | share |
|---|---|---|
| FeatureCollection | 1 | 100.0% |
Schema
4 columns| Alerts | ||||
|---|---|---|---|---|
| type | categorical | 0.0% | 1 |
long_tail
imbalance
|
| name | categorical | 0.0% | 1 |
long_tail
imbalance
|
| crs | unknown | 0.0% | — |
skipped
|
| features | unknown | 0.0% | — |
skipped
|
type
categorical metadata long_tail imbalanceThis column is a GeoJSON type discriminator field, holding the constant value 'FeatureCollection' across all rows. With n=1, cardinality=1, top_rate=1.0, and entropy of 0.0, it is entirely invariant — it carries zero information. The 'long_tail' and 'imbalance' alerts are technically correct but misleading given the trivial dataset size. Treatment: Drop before modelling; zero-variance constant column adds no predictive signal.
- n
- 1
- nulls
- 0 (0.0%)
- unique
- 1
- top_value
- FeatureCollection
- top_rate
- 1
- cardinality
- 1
- entropy
- 0
- entropy_ratio
- 0
name
categorical metadata long_tail imbalanceThis column appears to be a dataset or layer name/identifier, containing exactly one row with the single value 'submarine_cables'. With n=1, cardinality=1, null_rate=0.0, and top_rate=1.0, this column carries zero variance and no discriminative information whatsoever. The alerts for long_tail and imbalance are technically correct but trivially explained by the single-row, single-value nature of the data. Treatment: Drop this column entirely — zero entropy and a single constant value provide no modelling signal.
- n
- 1
- nulls
- 0 (0.0%)
- unique
- 1
- top_value
- submarine_cables
- top_rate
- 1
- cardinality
- 1
- entropy
- 0
- entropy_ratio
- 0
crs
unknown other skippedThis column ('crs', likely a Coordinate Reference System or Course identifier) contains only a single row with no null values and no computable statistics, making meaningful profiling impossible. The 'skipped' alert indicates saturn bypassed full analysis, almost certainly due to the trivially small sample size (n=1). No distributional, uniqueness, or type information is available beyond the single observation. Treatment: Withhold from modelling until more rows are available; re-profile with a full dataset to determine actual type and role.
- n
- 1
- nulls
- 0 (0.0%)
- unique
- —
features
unknown other skippedThis column contains only a single row (n=1) and was skipped during profiling, yielding no computable statistics. With n=1 and null_rate=0.0, there is exactly one non-null value present, but its content, type, and distribution are entirely unknown from this evidence. No meaningful characterisation is possible beyond confirming the column is not empty. Treatment: Inspect raw value manually; re-profile on a larger sample before deciding on encoding or dropping.
- n
- 1
- nulls
- 0 (0.0%)
- unique
- —