LatLong Maps
Turn CSV or Excel data into styled choropleth and categorical maps of India from plain language.
Community: Submitted by a user or imported; check the owner before granting accessOnlineAPI key requiredGlobalFreeRead-only
What it can do
What data it sees
Do you need an account
An API key from the service settings is required
Turn CSV or Excel data into styled choropleth and categorical maps of India from plain language.
Server tool list (4)
Raw names from tools/list. Only developers need these.
| create_upload | Start a client-direct file upload for large CSV/XLSX files. Returns a presigned put_url and an opaque upload_id. Steps: 1) call create_upload with file_name, 2) HTTP PUT the raw file bytes to put_url using the returned headers, 3) pass upload_id to question_to_map, parse_file, or render_map. Preferred over file_base64 for anything beyond a few KB — the bytes go straight to storage instead of riding inside the tool call. |
| get_capabilities | Return the server's capability matrix (supported map types, geo types, output formats, and classification methods). |
| process_upload | Validate and ingest a file uploaded via create_upload. Runs size, virus, and content-safety checks, parses CSV/XLSX/JSON, and returns an upload_id plus advisory intent (no raw rows). IMPORTANT: to make a map, call question_to_map and pass this upload_id — and pass the SAME upload_id on every follow-up question about this file (e.g. 'now show it by district'). The response includes a ready-to-use next_actions entry with upload_id already filled in; prefer firing that. Rejects infected or injected files (nothing is kept in that case). |
| question_to_map | Render a geographic map from a question. TO MAP A FILE (CSV/XLSX/JSON) — you MUST upload it first, in this order: 1) call create_upload {file_name} -> returns { upload_id, put_url } 2) HTTP PUT the raw file bytes to put_url (use the returned headers) 3) call process_upload {upload_id, ...your intent} -> validates the file 4) call question_to_map {question, upload_id, geo_column?, value_column?} Do NOT call question_to_map with a file path or the raw bytes for an uploaded document — pass the upload_id from step 1. Reuse the SAME upload_id on every follow-up about that file (e.g. 'now show it by district'). Ways to provide data: 1. Uploaded document (preferred): {"question": "show total by pincode", "upload_id": "<from create_upload>", "geo_column": "pincode", "value_column": "total"} 2. Question only (DB): {"question": "ola sales in delhi ncr"} 3. CSV inline (small only): {"question": "show sales", "csv": "state,sales\nMaharashtra,500", "geo_column": "state", "value_column": "sales"} INTENT (all optional; if you know them, pass them — your values win over auto-detection): geo_column, value_column, geo_level (state|district|pincode|rto|city|ac|pc), map_type, state_hint. If you omit upload_id, the server falls back to your most recent upload; passing it is more reliable. If value_column is 'total' and absent from the data, all numeric columns are summed automatically. Supported geo types: state, district, pincode, rto, city, ac, pc. |