Decimal Coordinate Pair List Parser
Parse a semicolon-separated list of strict comma numeric coordinate pairs; no whitespace, CRS, geodesy or dimensional inference.
Description
Parse a semicolon-separated list of strict comma numeric coordinate pairs; no whitespace, CRS, geodesy or dimensional inference.
A compact coordinate list can encode pairs separated by commas and points separated by semicolons. Its grammar does not establish a geographic coordinate system.
When to use this tool
Parse a semicolon-separated list of strict comma numeric coordinate pairs; no whitespace, CRS, geodesy or dimensional inference.
- Prepare the supplied text 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 text. 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.points. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Treat empty text as no points; otherwise split on semicolons, require exactly two comma-separated numeric tokens per point and parse each as a finite decimal/exponent number.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.points | The points list in the ordering and representation described above. |
{
"input": {
"text": "1,2;-3,4.5"
},
"output": {
"result": {
"points": [
[
1,
2
],
[
-3,
4.5
]
]
}
}
}Limitations and assumptions
- Whitespace is not trimmed and coordinate ranges, units, axes and reference system are not inferred. At most 128 points are accepted.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use a parser for the actual target format when the task requires CSV, shell, URL, calendar or filesystem semantics. These tools implement the specific small grammars stated here, without adding those surrounding conventions.
References
Similar or alternative tools
- Numeric Pair Token Parser
Parse an exact 2-component comma-separated finite numeric token with strict decimal/exponent grammar; no missing components or whitespace.
- Balanced Parenthesis Token Splitter
Split a literal delimiter only outside balanced parentheses; parentheses are retained, quotes and escapes have no special meaning.