JSON Scalar Array Duplicate Spans
Report contiguous repeated typed-scalar array spans; do not conflate numeric/string values or nonadjacent duplicates.
Description
Report contiguous repeated typed-scalar array spans; do not conflate numeric/string values or nonadjacent duplicates.
Repeated adjacent values can reveal duplicated rows or repeated samples inside a JSON array. Contiguous duplicate spans describe where repetition occurs without combining separated occurrences.
When to use this tool
Report contiguous repeated typed-scalar array spans; do not conflate numeric/string values or nonadjacent duplicates.
- Prepare the supplied arrayJson fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter arrayJson. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.runs. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require a JSON array of scalar values. Serialize each scalar to a typed comparison key, group consecutive equal keys, and return only runs longer than one with their original value and half-open start/end indexes.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| arrayJson | JSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file. | Text |
For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.
[
{
"field": "arrayJson",
"decoded": [
1,
1,
"1",
null,
null
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.runs | The runs list in the ordering and representation described above. |
{
"input": {
"arrayJson": "[1,1,\"1\",null,null]"
},
"output": {
"result": {
"runs": [
{
"start": 0,
"end": 2,
"value": 1
},
{
"start": 3,
"end": 5,
"value": null
}
]
}
}
}Limitations and assumptions
- This is a run audit, not global deduplication. Number 1 and string "1" differ; JSON serialization makes negative zero and positive zero share a key. Containers are rejected.
- Decoded JSON is bounded to 20,000 nodes and 32 nesting levels; record arrays have at most 128 records. Parsed number values use JavaScript floating point rather than arbitrary-precision decimal arithmetic.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
For document-wide requirements, combine these structural inventories with an explicit JSON Schema. Preserve the distinction between missing properties and null values, and between numbers and numeric-looking strings when building joins or indexes.
References
Similar or alternative tools
- JSON Array Homogeneity Audit
Audit immediate element-type homogeneity for every JSON array; an empty array is vacuously homogeneous, not evidence of a particular type.
- json array length policy check
Audit all JSON array lengths against inclusive bounds; no inferred schema or scalar-array coercion.