Argenmap lets users add their own geographic data to the map without uploading anything to a server. All file parsing happens entirely in the browser using client-side JavaScript libraries. To open the file loader, click the folder icon in the toolbar — this opens a modal dialog where you can select a local file. Once loaded, the layer is added to an Archivos section in the layer panel alongside the standard WMS and base map layers, and multiple files can be active at the same time. You can also add layers from a remote URL using the Load Layer tool. For details on the toolbar, see Map Tools.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ign-argentina/argenmap/llms.txt
Use this file to discover all available pages before exploring further.
Supported Formats
The modal dialog displays the supported formats: KML, GeoJSON, GPX, SHP en formato (.zip), WKT en formato (.txt o .wkt), TopoJSON en formato (.json). The file input accepts.txt, .json, .geojson, .wkt, .kml, .zip, and .gpx extensions. Each format is parsed by a dedicated library or built-in handler:
GeoJSON
Extensions:
.geojson, .jsonRFC 7946 compliant GeoJSON. Supports all geometry types: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and FeatureCollection. Parsed natively using the browser’s JSON parser and rendered directly as a Leaflet GeoJSON layer.KML
Extension:
.kmlKeyhole Markup Language. Supports Placemarks, Polygons, and LineStrings. Parsed by omnivore.js, which converts the XML to a GeoJSON-compatible Leaflet layer.GPX
Extension:
.gpxGPS Exchange Format. Supports waypoints, tracks, and routes exported from GPS devices or applications. Parsed by omnivore.js.Shapefile
Extension:
.zipESRI Shapefile. Must be packaged as a ZIP archive containing at minimum the .shp, .dbf, and .prj component files. Parsed client-side by shp.js (shapefile/shp.min.js), which reads the binary geometry and attribute data from the archive.TopoJSON
Extension:
.jsonTopology-preserving JSON format. Parsed by omnivore.js and added to the map as a standard vector layer. The file must have a .json extension.WKT
Extensions:
.txt, .wktWell-Known Text geometry representation. Supports all standard geometry types encoded as WKT strings. Parsed by omnivore.js.Shapefiles must be compressed into a single ZIP archive that contains all required component files — at minimum
.shp, .dbf, and .prj. Uploading the .shp file on its own will fail because geometry projection and attribute data are stored in separate files.Layer Management
Each loaded file appears as a named entry under the Archivos section of the layer panel. The file name is used as the layer name by default; you can click the name label in the file modal before adding the layer to rename it. If the same file name is loaded more than once, Argenmap appends a count suffix (e.g.,filename..(2)) to distinguish the duplicate entries.
Layers added from files behave like any other layer in the panel: they can be toggled on and off and removed individually. File layers persist for the current browser session but are not saved across page reloads.
Style Customization
After loading, geometries are rendered with default Leaflet styles. You can right-click a loaded geometry on the map to open the style editor and change border width, border color, and fill color. This style editing applies to drawn and loaded geometries alike.Underlying Libraries
| Format | Library |
|---|---|
| GeoJSON | Native JSON parsing (browser built-in) |
| KML | omnivore.js (FileLayer/omnivore/omnivore.min.js) |
| GPX | omnivore.js (FileLayer/omnivore/omnivore.min.js) |
| WKT | omnivore.js (FileLayer/omnivore/omnivore.min.js) |
| TopoJSON | omnivore.js (FileLayer/omnivore/omnivore.min.js) |
| Shapefile (ZIP) | shp.js (FileLayer/shapefile/shp.min.js) |