Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Observatorio-GC/Nodos/llms.txt
Use this file to discover all available pages before exploring further.
Each dataset in scripts/ is a GeoJSON FeatureCollection stored as a JavaScript variable assignment. Features carry a properties object whose keys vary by dataset category. This page documents the property schemas for the major layer types, drawn directly from the source files loaded in index.html.
How data files are structured
Every file in scripts/ follows this pattern:
var DatasetName = {
"type": "FeatureCollection",
"name": "DatasetName",
"crs": {
"type": "name",
"properties": { "name": "urn:ogc:def:crs:OGC:1.3:CRS84" }
},
"features": [
{
"type": "Feature",
"properties": { /* dataset-specific properties */ },
"geometry": { /* Point, MultiPoint, Polygon, MultiPolygon, LineString, MultiLineString */ }
}
]
};
[longitude, latitude] order.
Nodos (District Nodes)
Files: Centro1.js, Centro2.js, Trapiche1.js, Benegas2.js, Monte2.js, Hipodromo2.js, Marini.js, Parque2.js, Tortugas2.js, NodosPropuestos.js
Geometry: MultiPolygon
These files define the boundary polygons for each graded district node (Grado 1 and Grado 2) as well as proposed nodes. The DESCRIPTIO field lists categories of services currently absent from that node area.
| Property | Type | Description |
|---|
NOMBRE | string | Node name (e.g., "Centro", "Nuevo Nodo Trapiche 1") |
DESCRIPTIO | string | Description of missing services (e.g., "Administración. Servicios (Cajeros y puntos Wifi)…") |
Distrito | string | District name (e.g., "Trapiche", "Las Tortugas") |
id | number | Numeric feature identifier |
Walkability (Caminabilidad)
Files: Indice.js, Traza.js
Geometry: MultiLineString
Street segments are classified by walkability score. The PROMEDIO_P value drives the colour rendering of each segment in the map, ranging from "1" (worst) to "4" (best). The Name field holds a human-readable label that is displayed in popups.
| Property | Type | Description |
|---|
PROMEDIO_P | string | Walkability score: "1" = Malo, "2" = Regular Malo, "3" = Regular Bueno, "4" = Óptimo |
Name | string | Full score label (e.g., "Regular Malo: Disminuye la caminabilidad del espacio…") |
Corridors (Corredores)
File: Corredores.js
Geometry: MultiLineString
Proposed territorial connection corridors, each identified by the street or avenue name they follow.
| Property | Type | Description |
|---|
Name | string | Corridor name (e.g., "SAN MARTIN", "RIVADAVIA", "CORREDOR DEL OESTE") |
Cycling Infrastructure
Files: CicloviasExistentes.js, CicloviasProyectadas.js, Ciclovias Proyectadas (DAMI II).js, Ciclovias Proyectadas (Municipalidad).js, Ciclovias en Ejecucion (DAMI II).js, Ciclovias en Ejecucion (Municipalidad).js
Geometry: LineString / MultiLineString
Each feature represents a cycling route segment. The Distancia field combines a street name and distance label in a single string (e.g., "JUAN TERRADA (1,37 Km)"). The TIPO_2 field distinguishes infrastructure type.
| Property | Type | Description |
|---|
TIPO_2 | string | Infrastructure type label (e.g., "CICLOVIA", "SENDERO PEATONAL", "BICISENDA SOBRE CALZADA", "CIRCUITO CERRADO") |
Distancia | string | Route name and length in km (e.g., "BULEVAR TERRADA (0,40 Km)") |
Id | number | Numeric feature identifier |
metros | number | Length of the segment in metres |
Health Facilities
Files: Centrosdesalud.js, ClinicasPrivadas.js, Hospital.js
Geometry: MultiPoint (health centres) / Point (clinics and hospitals)
Centrosdesalud.js uses Nombre_1 (not Name) for the facility name, consistent with the naming convention in other administrative boundary files. The jurisdicci field distinguishes municipal from provincial facilities.
| Property | Type | Description |
|---|
Nombre_1 | string | Full facility name (e.g., "C. Salud Provincial Ramon Carrillo") |
jurisdicci | string | Jurisdiction: "Municipal" or "Provincial" |
Direccion | string | Street address |
tel | string | Telephone number (may be null or placeholder) |
encargado | string | Name of the facility director or responsible person |
horario | string | Operating hours (e.g., "7 a 20 hs.") |
qc_id | number | Internal quality-control identifier |
Pharmacies
File: Farmacias.js
Geometry: Point
| Property | Type | Description |
|---|
Nombre | string | Pharmacy name (e.g., "Farmacia HORIZONTE") |
Direccion | string | Street address (e.g., "Carril Sarmiento 2101") |
Telefono | string | Phone number (e.g., "Tel. 261 452-1237") |
Distrito | string | District name (e.g., "Distrito San Francisco del Monte") |
Municipal Boundaries
Files: Barrios.js, BarriosConsolidados.js, DistritosDepartamentales.js
Geometry: Polygon / MultiPolygon
Barrios.js carries richer heritage metadata per neighbourhood (year of construction, land use, owner, photo filename), while BarriosConsolidados.js and DistritosDepartamentales.js use the simpler Nombre_1 key.
Barrios.js properties
| Property | Type | Description |
|---|
Nombre | string | Neighbourhood name (e.g., "Barrio GENERAL ESPEJO (bancario)") |
Categor. | string | Feature category (e.g., "Barrios") |
AÑO | string | Year of construction (e.g., "Construcción año 1949") |
UBICACION | string | Bounding streets description |
DISTRITO | string | District name |
USO | string | Land use (e.g., "Residencial") |
PROPIETARI | string | Owner (may be null) |
Fotos | string | Photo filename in the img/ directory (e.g., "barrioBancario.jpg") |
BarriosConsolidados.js and DistritosDepartamentales.js properties
| Property | Type | Description |
|---|
Nombre_1 | string | Neighbourhood or district name (e.g., "Villa del Parque", "Gobernador Benegas") |
Urban Zone Laws
Files: Zonificacion.js, ZonaLey4886.js
Geometry: Polygon / MultiPolygon
These files encode zoning category boundaries derived from municipal ordinances. Properties typically contain zoning category codes and the legal ordinance reference. Exact property names vary by file; inspect features directly to confirm field names for a given version.
Gastronomy POIs
Files: Bares.js, Restaurantes.js, cafe.js, Heladerias.js
Geometry: Point
| Property | Type | Description |
|---|
Nombre | string | Establishment name |
Direccion | string | Street address |
Tourism and Heritage
Files: Bodegas.js, Informador.js, Esculturas.js, Edificios.js, SitiosyConjuntosEdilicios.js
Geometry: Point
Heritage and tourism features often include a photo reference that the popup system reads to display an image from the img/ subdirectory.
| Property | Type | Description |
|---|
Nombre | string | Name of the winery, sculpture, building, or site |
Ubicacion / UBICACION | string | Location description or address (key casing varies by file) |
Fotos | string | Filename of the associated photo in img/ (e.g., "bodegaLopez.jpg") |
To inspect any dataset’s actual property keys in a live session, open the browser DevTools console after the page has loaded and run:console.log(DatasetName.features[0].properties);
DatasetName with the JavaScript variable name for that dataset (e.g., Farmacias, Corredores, centrosdesalud).