Skip to content
GEOSAT
← Toro

Published land classification in Toro

The verified TORO_LADM_COL query returned four records: one Perímetro Urbano, two Perímetro Suelo de Expansión and one Perímetro Municipal. These are source labels, not parcel authorizations or permitted uses. They do not establish a complete inventory. Municipal perimeter OBJECTID 4 differs from the ORGOT reference boundary; it is retained without clipping or replacing that boundary. OBJECTID 2 is a small triangle and is also retained. The instrument, adopting act, current validity, cartographic date, scale and specific license have not been established. The 1899 version date does not establish adoption; original metrics and Z=0 must not be interpreted as areas, distances or heights or used to certify parcel accuracy. Original geometries are retained without repair; full topological validity has not been established. Up to 500 features and 2 MiB per query; other views may be partial or fail. An empty result or failure does not establish absence of classification or rules.

1 layer · service queried by area · Gobernación del Valle del Cauca · TORO_LADM_COL · pot_ue_clasificacionsuelo

Open this query ↗

Toro · Public query

Published land classification

Open the map with its prepared layers and select a feature to inspect its attributes.

Open Toro map →

What it includes

How to use it

  1. Open “Published land classification” at zoom 18 and select OBJECTID 1 from Results. Read the “Perímetro Urbano” label, the “Toro” namespace and the source link. Compare the published legend categories as context separate from the primary POT query; do not assign the IGAC register act to these polygons.
  2. The verified TORO_LADM_COL query returned four records: one Perímetro Urbano, two Perímetro Suelo de Expansión and one Perímetro Municipal. These are source labels, not parcel authorizations or permitted uses. They do not establish a complete inventory. Municipal perimeter OBJECTID 4 differs from the ORGOT reference boundary; it is retained without clipping or replacing that boundary. OBJECTID 2 is a small triangle and is also retained. The instrument, adopting act, current validity, cartographic date, scale and specific license have not been established. The 1899 version date does not establish adoption; original metrics and Z=0 must not be interpreted as areas, distances or heights or used to certify parcel accuracy. Original geometries are retained without repair; full topological validity has not been established. Up to 500 features and 2 MiB per query; other views may be partial or fail. An empty result or failure does not establish absence of classification or rules.

Frequently asked questions

How can I explore the published land classification?

Open “Published land classification” at zoom 18 and select OBJECTID 1 from Results. Read the “Perímetro Urbano” label, the “Toro” namespace and the source link. Compare the published legend categories as context separate from the primary POT query; do not assign the IGAC register act to these polygons.

What coverage and terms does the source have?

The verified TORO_LADM_COL query returned four records: one Perímetro Urbano, two Perímetro Suelo de Expansión and one Perímetro Municipal. These are source labels, not parcel authorizations or permitted uses. They do not establish a complete inventory. Municipal perimeter OBJECTID 4 differs from the ORGOT reference boundary; it is retained without clipping or replacing that boundary. OBJECTID 2 is a small triangle and is also retained. The instrument, adopting act, current validity, cartographic date, scale and specific license have not been established. The 1899 version date does not establish adoption; original metrics and Z=0 must not be interpreted as areas, distances or heights or used to certify parcel accuracy. Original geometries are retained without repair; full topological validity has not been established. Up to 500 features and 2 MiB per query; other views may be partial or fail. An empty result or failure does not establish absence of classification or rules.

Open this query ↗