Convert coordinates
convert_coordinatesConverts up to 1,000 points between decimal degrees (dd), degrees-minutes-seconds (dms) and UTM, and returns each point in the requested output formats, in the input order. To change the coordinate reference system of a GeoJSON use reproject_geojson. Takes up to 1,000 points per call (WGS84 latitude and longitude, or UTM zone, hemisphere, easting and northing). Costs US$0.001 per unit (up to 1,000 points) from prepaid credits; with the default 3 s it is charged only when it succeeds, and invalid input is never charged. Set dry_run to true to get the price without charging and max_cost_usd to refuse a call that would cost more; for heavier inputs set max_seconds from 4 to 30, where each second over the 3 included costs US$0.0005, the full time is held up front and the unused part refunded, and the price and the time used are charged if the call runs out of time or memory, or is cancelled while running.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"from": "<from>",
"to": "<to>",
"points": "<points>"
},
"name": "convert_coordinates"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Output formats to return for every point (1 to 3 of dd, dms, utm). | |
| from | Yes | Format of the input points: dd (decimal degrees), dms (degrees-minutes-seconds text) or utm. | |
| points | Yes | Up to 1000 points. Each is {lat, lon} for dd, a text for dms, or {zone, hemisphere, easting, northing} for utm, matching `from`. | |
| dry_run | No | When true, return the price (cost_usd) and units of this call without running it or charging anything. | |
| max_seconds | No | Compute time limit in seconds, 1 to 30 (default 3; 1 to 3 all use the standard 3 s). The price includes 3 s of compute. From 4 to 30 (extended time) the call runs on a separate lane, where buffer accepts larger inputs, and each second over 3 costs the geo_compute_second price: the price plus all those seconds is held at the start (that is what dry_run reports and max_cost_usd is compared with), the seconds not used are refunded, and the response adds compute_ms and max_seconds. With extended time the price and the time used are charged if the call runs out of time or memory, or is cancelled while running: 422 operation_too_complex keeps the whole hold, 422 operation_too_large or 413 result_too_large (a result over 8 MiB) or 499 cancelled keep the price and the seconds used, and those errors carry cost_usd. Any other failure is refunded in full. | |
| max_cost_usd | No | The most this call may cost, in USD, as a number or decimal text with at most 6 decimals (e.g. 0.01 or "0.01"). A call that would cost more is refused with 402 max_cost_exceeded and nothing is charged. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| units | Yes | Price units the input measured. | |
| result | No | The operation's result; absent with dry_run. | |
| call_id | No | Server-issued id of the call; absent with dry_run. | |
| dry_run | No | True when nothing was run or charged. | |
| cost_usd | Yes | What the call cost (or would cost, with dry_run), US dollars as decimal text. | |
| compute_ms | No | Extended time only: the compute time the call was billed on, in milliseconds. | |
| balance_usd | No | Credit balance after the charge, US dollars as decimal text; absent with dry_run. | |
| max_seconds | No | Extended time only: the max_seconds the call ran (or would run) with. |