LatLong latlong-map

[…] pass the returned file_key: {"question": "show total by pincode", "file_key": "mcp-uploads/2026/01/15/<uuid>.csv"}. "mcp-uploads/<user-id>/2026/01/15/<uuid>.csv"}. The file_key is reusable — for additional questions on the […]

[…] Supported geo types: state, district, pincode, rto, city, ac, pc. Points mode: if your file has latitude/longitude columns (e.g. from a prior geocoding step, or coordinates you already had) and your question asks to plot/pin/mark locations ("plot my stores", "show me the outlet locations", "mark these points"), the server detects the coordinate columns automatically and renders markers instead of shaded regions — no geo_column/value_column needed. The boundary lines drawn beneath the markers and how far the map zooms are chosen automatically from where the points actually fall (tightens to a state or district for a local cluster, falls back to all-India for a nationwide spread); you can also name a level explicitly ("plot by assembly constituency", "rto wise") to force it. A response may report points that fall outside every boundary (e.g. offshore or swapped lat/lon) — check for that in the warnings.

Render a geographic map from a question. Ways 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 provide data: 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. Question only (DB): {"question": "ola sales in delhi ncr"} 2. Upload id (large files): {"question": "show total by pincode", "upload_id": "<from create_upload/process_upload>", "geo_column": "pincode", "value_column": "total"} Keep passing Reuse the SAME upload_id on every follow-up about that file (e.g. 'now show it by district'). If you omit it, the server tries your most recent upload, but passing it is more reliable. 3. File path: Ways to provide data: 1. Uploaded document (preferred): {"question": "show total by pincode", "file_path": "/path/to/data.csv", "upload_id": "<from create_upload>", "geo_column": "pincode", "value_column": "total"} 4. 2. Question only (DB): {"question": "ola sales in delhi ncr"} 3. CSV inline: inline (small only): {"question": "show sales", "csv": "state,sales\nMaharashtra,500", "geo_column": "state", "value_column": "sales"} IMPORTANT: When providing data (file_path/csv/data), ALWAYS specify geo_column and value_column. 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 doesn't exist in absent from the data, all numeric columns are summed automatically. geo_column can be numeric (pincode=560049) — detected by column name. Supported geo types: state, district, pincode, rto, city, ac, pc.