Typed Value Count Table
Count typed JSON scalar occurrences, preserving number/string/boolean/null identity; unlike a string frequency counter it does not coerce keys.
Description
Count typed JSON scalar occurrences, preserving number/string/boolean/null identity; unlike a string frequency counter it does not coerce keys.
Counting scalar JSON values should distinguish a numeric value from the same-looking string. This table retains that type distinction.
When to use this tool
Count typed JSON scalar occurrences, preserving number/string/boolean/null identity; unlike a string frequency counter it does not coerce keys.
- Prepare the supplied valuesJson 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 valuesJson. 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.counts. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse valuesJson as at most 128 scalars: strings, numbers, booleans or null. Group by JSON serialization and emit the first value with its occurrence count.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| valuesJson | 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": "valuesJson",
"decoded": [
1,
"1",
1,
true,
null
]
}
]| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.counts | The counts list in the ordering and representation described above. |
{
"input": {
"valuesJson": "[1,\"1\",1,true,null]"
},
"output": {
"result": {
"counts": [
{
"value": 1,
"count": 2
},
{
"value": "1",
"count": 1
},
{
"value": true,
"count": 1
},
{
"value": null,
"count": 1
}
]
}
}
}Limitations and assumptions
- Objects and arrays are not accepted as values. Numeric negative zero and zero share JSON serialization, and input occurrence order is reduced to first appearance.
- Count records contain a scalar JSON value and an integer count from zero to one million. Duplicate typed values aggregate up to one million per input key and zero aggregates are omitted.
- 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.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- 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
Keep count-table arithmetic separate from occurrence ordering and persistent inventory changes. Choose minimum intersection, maximum union or additive sum explicitly, and retain scalar types when matching values.
References
Similar or alternative tools
- Multiset Count Table Expander
Expand normalized typed multiplicity rows into a bounded occurrence list, preserving first key appearance order.
- Multiset Count Table Normalizer
Normalize typed scalar count rows by exact identity, summing duplicates and dropping zeros; counts must be nonnegative integers.