{
  "id": "geospatial-vector-data",
  "title": "Geospatial Vector Data",
  "lang": "en",
  "source_lang": "en",
  "summary": "Geospatial vector data represent geographic features as coordinate-based points, lines, and polygons linked to descriptive attributes, supporting mapping, spatial analysis, and geographic information management.",
  "category": "geography",
  "subcategory": "",
  "type": "concept",
  "aliases": [
    "Vector geospatial data",
    "vector geographic data",
    "geographic vector data",
    "GIS vector data"
  ],
  "generated_at": "2026-11-03",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/geospatial-vector-data/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/geospatial-vector-data/",
      "json": "https://aiwiki.page/zh/geospatial-vector-data.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "Geospatial vector data are a digital representation of geographic features using coordinate-defined geometries, principally points, lines, and polygons, together with descriptive attributes. A road may be represented by a line, a building by a polygon, and a monitoring station by a point. Vector data are a principal data model in a geographic information system (GIS), alongside geospatial raster data, which represent space through an array of cells. The word vector here refers to coordinate-based geometry, not necessarily to a quantity with magnitude and direction."
    },
    {
      "heading": "Data model",
      "text": "A vector dataset usually contains identifiable geographic features. Each feature combines several components:\n\n- Geometry: its position, shape, and spatial extent.\n- Attributes: descriptive values such as a name, road class, population, or observation date.\n- Identifier: a value used to distinguish the feature and connect it to other records.\n- Spatial reference information: the framework needed to interpret its coordinates.\n\nFeatures are often organized into layers or feature classes with a common purpose and schema, such as buildings, road centerlines, or administrative areas. Many formats and applications restrict a layer to one broad geometry type, although others permit mixed geometries.\n\nA feature is not necessarily equivalent to a physical object. A polygon may represent a legal jurisdiction, a statistical reporting area, or a modeled flood extent. Conversely, one real-world object may be represented by several features—for example, a road divided into segments wherever its name, speed limit, or connectivity changes.\n\nGeometry types\n\nGeometry | Representation | Typical uses\nPoint | A single coordinate position | Wells, sampling sites, addresses\nLine string | An ordered sequence of vertices joined by segments | Roads, streams, pipelines\nPolygon | An area bounded by an exterior ring and, optionally, interior rings | Parcels, lakes, administrative areas\nMultipart geometry | Several components of the same geometric type stored as one geometry | Island groups, discontinuous jurisdictions\nGeometry collection | A grouping that may contain different geometry types | Composite spatial records\n\nA line string is often called a polyline. A polygon's interior rings usually represent holes, such as an island excluded from a lake polygon. Multipart features allow disconnected areas to share one identity and attribute record.\n\nMany vector datasets use straight segments between vertices. Curved geometry types also exist, but support varies across formats and software. A curve may therefore be approximated by a sufficiently dense sequence of straight segments during exchange.\n\nAttributes and relationships\n\nAttributes are commonly stored in tables, with one row corresponding to a feature and columns defining fields. Field types may include text, integers, decimal values, dates, and Boolean values. Database relationships can connect a feature to multiple records without duplicating its geometry: a monitoring station, for example, may be linked to thousands of observations.\n\nGeometry and attributes are distinct. Changing a road's classification need not alter its coordinates, while correcting its alignment need not change its name. Maintaining stable identifiers helps preserve these relationships through updates."
    },
    {
      "heading": "Coordinates and spatial reference",
      "text": "Coordinates are meaningful only in relation to a coordinate reference system (CRS). Geographic coordinate systems commonly express positions using latitude and longitude, while projected coordinate systems use planar coordinates, often in metres or feet.\n\nA CRS includes more than units. Its definition may involve a geodetic datum, coordinate axes, and a map projection. Vertical coordinates may require a separate height reference. Axis order also matters: systems and interfaces do not universally agree on whether latitude or longitude comes first.\n\nA point in two dimensions can be written as \\(P=(x,y)\\). Some data include a third coordinate \\(z\\), usually representing elevation or another vertical position. Certain geometry models also support a measure \\(m\\), such as distance along a route.\n\nA dataset with elevation values is not automatically a full three-dimensional model. A building footprint with a height attribute differs from a solid building model, and many GIS operations evaluate only horizontal coordinates even when \\(z\\)-values are present.\n\nMeasurement and transformations\n\nDistances and areas depend on the coordinate system and computational method. For projected coordinates, a basic planar distance is\n\n\\[d=\\sqrt{(x_2-x_1)^2+(y_2-y_1)^2}.\\]\n\nThis formula produces a distance in the coordinate system's units; it does not by itself correct projection distortion. Applied directly to longitude and latitude, it produces an angular-coordinate difference rather than a ground distance. Earth-surface measurements may instead use geodesic calculations on a reference ellipsoid or an appropriate projected CRS.\n\nAssigning a CRS and transforming coordinates are different operations. Assigning a CRS declares how existing coordinate values should be interpreted; transformation calculates coordinates in another reference system. An incorrect assignment can place otherwise well-formed geometry in the wrong location."
    },
    {
      "heading": "Geometry and topology",
      "text": "Geometry describes coordinates and shape. Geospatial topology describes relationships such as connectivity, adjacency, containment, and shared boundaries.\n\nIn a simple-feature representation, neighboring polygons may each store their own copy of a common boundary. In a topological representation, shared edges and nodes can be stored explicitly and referenced by multiple features. Explicit topology can support consistent editing and reduce duplication, although many spatial relationships can also be calculated from independently stored geometries.\n\nTopological requirements depend on the dataset:\n\n- Parcels intended to form a complete subdivision may be required to have no gaps or overlaps.\n- Road segments may be required to connect at designated junctions.\n- A drainage network may need consistent downstream connectivity.\n- Points representing entrances may be required to lie on building boundaries.\n\nGeometric intersection does not necessarily imply real-world connection. Two road lines may cross in plan view while passing over and under one another. Network analysis therefore requires information about connectivity, grade separation, direction, and travel restrictions, not just visible line crossings.\n\nGeometric validity is also distinct from application-specific topology. A self-intersecting polygon ring is invalid under common simple-feature rules. Two individually valid parcel polygons may nevertheless violate a rule prohibiting overlap."
    },
    {
      "heading": "Creation and historical development",
      "text": "Vector geographic data developed through the convergence of digital cartography, computer-assisted drafting, land surveying, and spatial database systems. Early GIS applications used coordinate-based boundaries and networks for tasks such as land inventory and resource management. Subsequent developments expanded support for attribute queries, topology, database storage, and interoperable exchange.\n\nCommon production methods include:\n\n- Digitizing features from paper maps, scanned plans, or aerial imagery.\n- Collecting positions through field surveys and satellite navigation.\n- Importing engineering drawings or administrative records.\n- Extracting roads, buildings, and other objects from imagery.\n- Converting raster regions or contours into vector geometry.\n\nGeoreferencing establishes the spatial relationship between an image or source document and a coordinate framework before features are traced from it.\n\nAutomated extraction, including methods based on machine learning, can accelerate production but may introduce omissions, misclassification, irregular boundaries, or disconnected networks. Human interpretation and validation remain important where semantic meaning or positional reliability matters."
    },
    {
      "heading": "Storage, standards, and delivery",
      "text": "Vector data can be stored in files, databases, and network services. Formats differ in their handling of geometry, attributes, coordinate systems, transactions, and metadata.\n\n- Shapefile: a widely supported, multi-file format with restrictions such as short attribute-field names and limited support for some data types.\n- GeoJSON: a JSON-based exchange format. The standardized format uses WGS 84 longitude and latitude in that order, with an optional height coordinate.\n- GeoPackage: a SQLite-based container that can hold vector feature tables, tile data, and related information in one file.\n- Spatial databases: database systems with geometry storage, spatial indexes, and spatial query operations, often used for shared datasets and transaction-based editing.\n\nThe Open Geospatial Consortium develops standards for geometry models, encodings, and geospatial services. These standards improve interoperability, but software implementations can still differ in supported geometry types, coordinate handling, and validation behavior.\n\nVector tiles divide geographic content into spatial tiles for efficient delivery and display. Tile generation commonly includes clipping, simplification, and coordinate quantization, so tiled data may not preserve every detail of the source dataset.\n\nA Web Map Service, by contrast, ordinarily delivers rendered map images rather than the underlying editable feature geometries."
    },
    {
      "heading": "Spatial operations and applications",
      "text": "Vector representations support both attribute-based queries and spatial analysis. Common operations include:\n\n- Spatial selection: finding features that intersect, touch, contain, or lie within another geometry.\n- Spatial joins: transferring or summarizing attributes according to location.\n- Buffering: constructing areas within a specified distance of features.\n- Overlay: intersecting, uniting, or subtracting geometries to combine spatial information.\n- Clipping: retaining the portions of features inside a selected area.\n- Dissolving: merging features according to shared attribute values.\n- Nearest-neighbor queries: locating nearby objects.\n- Network analysis: calculating routes, service areas, or movement through connected systems.\n\nThese operations support land administration, urban planning, transport management, utility inventories, environmental assessment, and emergency mapping. In hydrology, vector networks can represent streams and drainage connections. In terrain modeling, a triangulated irregular network represents a surface with connected triangular facets.\n\nVector features also provide boundaries for summarizing raster values—for example, calculating average elevation within a watershed or land-cover proportions within a municipality."
    },
    {
      "heading": "Scale, accuracy, and quality",
      "text": "Vector geometry can be displayed at many zoom levels without the pixelation associated with enlarging a raster image. This does not mean it has unlimited accuracy or detail.\n\nA coastline traced from a small-scale map remains generalized even when displayed at a much larger map scale. Coordinate values with many decimal places may convey numerical precision without corresponding positional accuracy. Representation also changes with scale: a town may appear as a point on a national map and as a collection of building polygons on a local map.\n\nCartographic generalization includes simplification, aggregation, displacement, and selective omission. These operations make maps legible but can change geometric relationships unless carefully controlled.\n\nQuality assessment addresses several separate dimensions:\n\n- Positional accuracy: agreement with an accepted reference position.\n- Attribute accuracy: correctness of descriptive values.\n- Completeness: missing or excess features.\n- Logical consistency: compliance with geometry, topology, and schema rules.\n- Temporal quality: currency and consistency of observation dates.\n- Lineage: how the data were collected, processed, and revised.\n\nFinite numerical precision can cause nearly coincident boundaries to produce narrow sliver polygons during overlay. Snapping and tolerance rules can help resolve such problems but may also merge features that should remain separate."
    },
    {
      "heading": "Comparison with raster data and analytical limitations",
      "text": "Vector data are especially suitable for discrete objects, explicit boundaries, networks, and feature-level attributes. Raster data are often more direct for continuous fields, imagery, and repeated neighborhood calculations. Neither model is universally superior: storage requirements and processing performance depend on feature complexity, cell size, indexing, and the operation involved.\n\nRasterization converts vector features into cells, potentially losing narrow features or boundary detail. Vectorization converts raster patterns into geometries, but the resulting boundaries may inherit the source grid's stair-step structure. Conversion does not create spatial accuracy absent from the source.\n\nVector boundaries can also make uncertain phenomena appear exact. Ecological transitions, historical territories, and modeled hazard zones may have gradual or disputed limits even when encoded as sharply bounded polygons. Metadata, dates, and uncertainty information are therefore important for interpretation.\n\nStatistical results aggregated to vector zones may change when zone boundaries or scales change, a problem known as the modifiable areal unit problem. Vector geometry alone does not resolve this dependence. Likewise, precise location records can expose sensitive information; access restrictions, aggregation, and other data privacy measures may be necessary when datasets describe identifiable people or sensitive sites."
    }
  ],
  "links": [
    "geographic-information-system",
    "geospatial-raster-data",
    "coordinate-reference-system",
    "latitude-and-longitude",
    "map-projection",
    "geospatial-topology",
    "cartography",
    "georeferencing",
    "machine-learning",
    "geopackage",
    "open-geospatial-consortium",
    "web-map-service",
    "spatial-analysis",
    "urban-planning",
    "hydrology",
    "map-scale",
    "cartographic-generalization",
    "data-privacy"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}