Skip to main content

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.

Argenmap organizes all map content — base maps, WMS overlays, and WMTS services — inside a collapsible layer panel on the left side of the screen. When the application starts, it reads every service defined in data.json and fetches its capabilities document automatically; users never need to enter a URL by hand. Layers appear as grouped sections that can be expanded, searched, and activated with a single click.

Base Maps

Base maps provide the background tile layer for the map. Only one base map can be active at a time; selecting a new one replaces the current one immediately. Base maps are configured with the type: "basemap" property in data.json and support both TMS and XYZ tile services. The default Argenmap configuration ships with five base maps:

Argenmap

IGN’s official street and topographic map of Argentina, served as a TMS layer from IGN’s GeoServer. Selected by default on startup.

Argenmap Gris

Grayscale variant of the IGN base map, useful as a neutral background when overlaying thematic WMS layers.

Imágenes Satelitales Esri

Esri World Imagery satellite tiles. Maximum native zoom level is 17.

Mapa Topográfico Esri

Esri World Physical Map. Best suited for overview scales; native zoom tops out at level 8.

Imágenes Satelitales Here

Here satellite imagery, supporting zoom levels 3–20.
Each base map entry in data.json carries zoom.min, zoom.max, zoom.nativeMin, and zoom.nativeMax values that Argenmap uses to show a warning when the user zooms beyond the layer’s native resolution.

WMS Layers

WMS overlay sections are added by including an object with "type": "wmslayer" in data.json. On startup, Argenmap calls GetCapabilities on the configured host URL, parses the returned layer list, and builds a collapsible section in the panel — one section per WMS service. Each discovered layer is listed with its title and can be toggled on or off independently. The default configuration includes two WMS groups:
  • Industria y servicios — Industries, agricultural production, mining, energy, communications, and related themes.
  • Modelos digitales de elevaciones — Digital elevation models.
{
  "type": "wmslayer",
  "peso": 70,
  "nombre": "Industria y servicios",
  "short_abstract": "Industrias, producción agropecuaria, minería, energía, comunicaciones, etc.",
  "seccion": "industria-servicios",
  "servicio": "wms",
  "version": "1.3.0",
  "host": "https://wms.ign.gob.ar/geoserver/industria-servicios/wms"
}
Key configuration properties for WMS entries:
host
string
required
The base URL of the WMS service. Argenmap appends ?service=WMS&request=GetCapabilities automatically.
version
string
default:"1.3.0"
WMS protocol version. Also used to set the VERSION parameter in GetMap and GetFeatureInfo requests.
nombre
string
required
Display name for the layer group shown as the section header in the layer panel.
short_abstract
string
Short description of the service, displayed as a subtitle below the section header.
seccion
string
required
Internal identifier for the section, used as the DOM element ID.
peso
number
Sort order value. Lower numbers appear higher in the layer panel.

WMTS Layers

WMTS services work similarly to WMS but follow the WMTS capabilities schema. Set "servicio": "wmts" and "version": "1.0.0" in the data.json entry. Argenmap fetches the GetCapabilities document, enumerates the available layers, and presents them in the same collapsible panel style.
{
  "type": "wmslayer",
  "nombre": "Mi servicio WMTS",
  "servicio": "wmts",
  "version": "1.0.0",
  "host": "https://example.com/geoserver/gwc/service/wmts"
}

Hillshade Overlay

A hillshade relief overlay can be added on top of compatible base maps. It is configured in the hillshade block of preferences.json:
{
  "hillshade": {
    "addTo": ["argenmap", "argenmap_gris"],
    "attribution": "sombra de montaña <a target='_blank' href='https://www.arcgis.com/home/item.html?id=1b243539f4514b6ba35e7d995890db1d'>©Esri</a>",
    "icon": "src/styles/images/mountains.svg",
    "name": "hillshade",
    "switchLabel": "Agregar sombra de montaña Esri",
    "url": "https://services.arcgisonline.com/arcgis/rest/services/Elevation/World_Hillshade/MapServer/tile/{z}/{y}/{x}.png"
  }
}
The addTo array lists the nombre values of base maps that should show the hillshade toggle switch. In the default configuration, hillshade is available for "argenmap" and "argenmap_gris". When the toggle is enabled on a compatible base map, the hillshade tile layer is composited on top. The toggle disappears automatically when the user switches to a base map not listed in addTo. The layer panel includes a search box that filters visible layer names in real time. This is controlled by the showSearchBar field in preferences.json, which shows or hides the filter input inside the layer panel:
{
  "showSearchBar": true
}
This is distinct from the geocoder search bar (the location search box at the top of the map), which is controlled separately by searchbar.isActive in preferences.json:
{
  "searchbar": {
    "isActive": true,
    "top": "5px",
    "left": "40%"
  }
}
showSearchBar filters the layer panel contents; searchbar.isActive controls the geocoder/location search bar used to search for places on the map.

Querying Layers (GetFeatureInfo)

Clicking on an active WMS layer fires a GetFeatureInfo request at the clicked map coordinate. You can also use a drawn geometry as a spatial filter to query data across active layers. The response is displayed either as a floating popup or as a tabular results panel depending on the table.isActive setting in preferences.json:
{
  "table": {
    "isActive": false,
    "rowsLimit": 5
  }
}
When table.isActive is false, query results appear in a standard Leaflet popup. When true, results open in a dedicated table panel below the map with a maximum of rowsLimit rows per response.
For full details on every property accepted by base map, WMS, and WMTS entries — including peso (sort order), legendImg, and zoom constraints — see the Data JSON configuration reference.

Build docs developers (and LLMs) love