← Back to Index
Chapter 6

Vector Analysis

Syllabus & Marks Distribution

DetailInformation
Chapter6 — Vector Analysis
Teaching Hours6 hours
Marks Allocation10 marks
Total Course Marks80 marks
Weight12.5% of total

Syllabus Topics

  • Data management functions
  • Data analysis functions

Note: This is one of the highest-weighted chapters (10 marks). Expect at least one long-answer question (5+ marks) from this chapter covering overlay, buffer, or network analysis.

Importance & Frequently Asked Topics HIGH

Marks Distribution by Each Exam

Asked 18 times across past exams. Total marks: 161. Average marks per exam: ~11.

ExamMarks
2071 Bhadra10
2071 Magh10
2072 Ashwin11
2072 Magh10
2073 Bhadra10
2073 Magh10
2074 Bhadra16
2074 Magh12
2075 Bhadra10
2075 Magh12
2076 Bhadra10
2078 Chaitra10
2079 Chaitra10
2080 Chaitra10
2081 Chaitra—
2082 Shrawan10

Frequently Asked Topics

TopicTimes AskedFrequency
Data Management Functions 13
Data Analysis Functions 5

Topic-wise Importance & Exam Tips

TopicImportanceKey Points / Exam Tips
Overlay operations (Union, Intersect, Identity, Erase)HighMost important topic in this chapter. Draw Venn diagrams for each operation. Know which features and attributes are preserved.
Buffer analysisHighFrequently asked. Explain point, line, and polygon buffers. Fixed vs variable-width buffers. Give application examples (river setback, road noise zones).
Network analysisHighShortest path (Dijkstra's algorithm concept), allocation, facility location. Real-world examples: ambulance routing, school catchment areas.
Point-in-polygon, Line-in-polygon operationsMediumExplain with diagrams how point/line features are overlaid with polygon boundaries.
Coordinate transformationMediumAffine transformation (6 parameters), rubber-sheeting for local adjustments.
Data management functionsLowEdge matching, conflation, map joining. Brief explanations sufficient.
Spatial joinMediumHow attributes from one layer are transferred to another based on spatial relationship.

Aronoff’s Classification of GIS Analytical Capabilities (Textbook pp.344–347)

  1. Classification, Retrieval & Measurement: Operations on a single data layer — retrieving features, classifying/reclassifying, measuring distances and areas.
  2. Overlay Functions: Combining multiple layers to derive new spatial information (intersection, union, clip).
  3. Neighbourhood Functions: Operations based on proximity — buffer zones, spatial interpolation, topographic functions (slope, aspect).
  4. Connectivity Functions: Operations on connected features — network analysis (shortest path), visibility analysis (line of sight), flow analysis.

1. Data Management Functions vs. Data Analysis Functions

PAST EXAM QUESTIONS ON THIS TOPIC:

  1. Differentiate between data management functions and data analysis functions in vector GIS [5] (2072 Ashwin, Q4a)
AspectData Management FunctionsData Analysis Functions
PurposeOrganize, maintain, refine, and prepare the spatial databaseDerive insights, solve spatial problems, create new datasets
Creates new geometry?No — works on existing dataYes — creates new spatial features (buffers, overlays)
NaturePreparatory and administrativeInvestigative and problem-solving
ExamplesData import/export, projection transformation, topology checking, attribute editing, data validation, coordinate conversionBuffer analysis, overlay (Clip, Intersect, Union), network analysis, point-in-polygon, proximity analysis
InputRaw or existing spatial datasetsCleaned and prepared spatial datasets
OutputRefined, corrected, and organized datasetsNew spatial layers, statistics, reports, decision maps
When usedBefore analysis — during data preparation phaseDuring the analytical phase of a GIS project
Data Management vs. Data Analysis Functions DATA MANAGEMENT Organize & Prepare ⇄ Convert Import/Export, Format conversion (SHP↔GDB) Edit Move vertices, reshape polygons, update fields [OK] Validate Topology checking, projection transform No new spatial geometry created DATA ANALYSIS Derive & Create Buffer Proximity zones around features (new polygons) ∩ Overlay Clip, Intersect, Union, Erase (topology ops) ≡ Query Network analysis, point-in-polygon, SQL Creates new spatial datasets
Fig 6.1 — Data Management vs. Data Analysis: Management functions prepare data (convert, edit, validate) without creating new geometry; Analysis functions derive new spatial datasets through geometric operations.

Spatial Selection & Measurement (Textbook pp.350–365)

  • Distance Measurement: Pythagorean distance: dist(p,q) = √((xp − xq)² + (yp − yq)²)
  • Minimal Bounding Box (MBR): The smallest axis-aligned rectangle enclosing a feature. Used as a quick pre-filter: if bounding boxes don’t overlap, the features cannot possibly intersect. This dramatically speeds up spatial queries.
  • Types of Spatial Selection: (1) Interactive selection (clicking on map), (2) Selection by attribute conditions (SQL WHERE), (3) Selection by topological relationships (containment, intersection, adjacency, distance-based).
  • Combining Conditions: Atomic conditions use predicates (<, >, =, ≤, ≥, ≠). Combined with Boolean operators AND, OR, NOT and brackets using propositional calculus.

2. Three Vector Data Management Functions

PAST EXAM QUESTIONS ON THIS TOPIC:

  1. Explain any three vector data management functions [6] (2072 Ashwin, Q4b)

If asked to explain strict data management operations, use these three:

  1. Data Conversion: Transforming spatial data between different models or formats, such as converting a vector shapefile into a raster grid (Rasterization) or converting CAD files into GIS shapefiles.
  2. Data Editing: Modifying existing vector features to correct errors or update outdated spatial and attribute data. This includes moving vertices, reshaping polygons, or updating the text fields in the attribute table.
  3. Topology Building/Validation: Establishing and checking the spatial relationships between adjacent or connected features to ensure data integrity. This involves applying rules like "polygons must not have gaps" or "lines must connect at nodes" to clean up digitizing errors.

3. Detailed Geoprocessing and Vector Functions

PAST EXAM QUESTIONS ON THIS TOPIC:

  1. Explain following vector functions: (a) Erase (b) Clip (c) Map join (d) Update (e) Split [10] (2073 Magh, Q6)
  2. Explain following vector functions: (a) Union (b) Clip (c) Merge (d) Intersect [10] (2072 Magh, Q8)
  3. Explain following vector functions: (a) Intersection (b) Clip (c) Dissolve (d) Union [10] (2071 Bhadra, Q5)
  4. Explain Geoprocessing tools: (a) Clip (b) Merge (c) Union (d) Intersection (e) Prove Intersection = Union + Clip [12] (2074 Magh, Q3)
  5. Explain clip, merge, union, dissolve, and intersection functions with figures and tables [16] (2074 Bhadra, Q4)
  6. Explain geoprocessing tools: (a) Intersection (b) Union (c) Dissolve (d) Buffer (e) Clip [10] (2079 Chaitra, Q6)
  7. Explain vector functions with attribute table effects: (i) Buffer (ii) Dissolve (iii) Union (iv) Intersection (2082 Shrawan)

The examiners frequently ask you to explain these specific functions along with their spatial maps and attribute table effects.

Function-wise Exam Frequency

How many times each geoprocessing / vector function has been directly asked across all past exams:

FunctionTimes AskedYears Asked (descending)Frequency
Clip 9 2080, 2079, 2075 Magh, 2075 Bhadra, 2074 Magh, 2074 Bhadra, 2073, 2072, 2071
Intersect 9 2082, 2080, 2079, 2075 Magh, 2075 Bhadra, 2074 Magh, 2074 Bhadra, 2072, 2071
Union 8 2082, 2080, 2079, 2075 Magh, 2074 Magh, 2074 Bhadra, 2072, 2071
Dissolve 6 2082, 2079, 2075 Magh, 2075 Bhadra, 2074 Bhadra, 2071
Buffer 4 2082, 2080, 2079, 2075 Magh
Merge 4 2075 Bhadra, 2074 Magh, 2074 Bhadra, 2072
Erase 1 2073
Map Join / Spatial Join 1 2073
Update 1 2073
Split 1 2073
Exam Strategy: Clip, Intersect, Union, and Dissolve are by far the most frequently asked. Prepare all four with diagrams + attribute table effects. Buffer is rising in recent exams (2079, 2080, 2082). Erase, Update, Split, and Map Join were asked only once (2073) — still know them briefly.
All 10 Geoprocessing Operations at a Glance What each operation does to geometry (left) and attributes (right) # Operation Type Geometry Effect Attribute Effect 1 Clip Analysis Cuts input to clip boundary shape Input A attrs only (B discarded) 2 Intersect Analysis Keeps only overlap (A ∩ B) Both A + B attrs joined 3 Union Analysis Keeps everything (A ∪ B), splits overlap Both joined; NULLs where no overlap 4 Dissolve Mgmt Removes internal boundaries (same attr) Rows merged; stats (SUM/AVG) optional 5 Buffer Analysis Creates proximity polygon at distance d Inherits base attrs + BUFF_DIST col 6 Merge Mgmt Keeps both geometries unchanged Rows stacked vertically (appended) 7 Erase Analysis Removes overlap from input (A ∖ B) Input A attrs only 8 Spatial Join Analysis Geometry unchanged (target layer) Join attrs transferred by location 9 Update Mgmt Replaces base geometry in overlap zone Update layer attrs replace base attrs 10 Split Mgmt Divides input into separate files by boundary Each output inherits original attrs Analysis = creates new spatial geometry Mgmt = reorganizes existing data Key: ∩=overlap, ∪=all, ∖=subtract
Fig 6.2 — Quick Reference: All 10 geoprocessing operations summarized — what each does to geometry and attribute tables, categorized by Analysis vs. Management type.

A. Clip Asked 9 times

Years: 2080, 2079, 2075 Magh, 2075 Bhadra, 2074 Magh, 2074 Bhadra, 2073, 2072, 2071

Input Clip boundary cookie-cutter Output: only inside clip
Fig 6.3 – Clip: Cookie-cutter extracts input features within clip boundary

Exam Example

Exam Example: You are given a massive geographic dataset of the entire national river network, but your final year project only focuses on a specific watershed model. You use the Clip tool, with your specific watershed boundary as the "cookie-cutter," to extract only the streams and rivers that flow within your study area. The resulting layer contains only the relevant river segments, keeping the original river attributes intact.

🇳🇵 National Rivers Watershed boundary Clip [OK] Study Area Only Only rivers inside watershed Attribute Table • River_ID: Koshi_Trib_03 • Length_km: 12.4 • Order: 3 Input attrs only — no clip attrs
Ex A – Clip: National river network clipped to watershed study area

Attribute Table Example — Clip

Input Layer (Land Use):

FIDLU_TypeArea_ha
1Forest120.5
2Agriculture85.3
3Urban45.0

Clip Layer (Study Area):

FIDNameDistrict
1Watershed_AKavrepalanchok

Output (Clipped):

FIDLU_TypeArea_ha
1Forest42.1
2Agriculture38.7
Key: Only Input layer attributes are retained. Clip layer columns (Name, District) are completely discarded. Areas recalculated for clipped geometry. Features entirely outside the clip boundary (Urban) are removed.

B. Intersect Asked 9 times

Years: 2082, 2080, 2079, 2075 Magh, 2075 Bhadra, 2074 Magh, 2074 Bhadra, 2072, 2071

A B Input Layers ∩ A ∩ B (Overlap only) Attributes: A + B combined
Fig 6.4 – Intersect: Only the overlapping region is preserved, with both attribute tables joined

Exam Example

Exam Example: You are conducting a site response analysis to identify areas highly vulnerable to earthquake damage. You have one polygon layer showing "High Soil Liquefaction Potential" and another polygon layer showing "Dense Urban Settlements." By applying the Intersect tool, the output map will strictly show the overlapping zones—representing highly populated areas built on dangerous soil. The output attribute table merges the soil properties and the population data for those specific areas.

Liquefaction Zone [!] Dense Urban overlap ∩ [!]Vulnerable Zone Only overlapping area Joined Output Table Liq_Class SPT_N Ward_Pop Density High 5 32,000 4,200 V.High 3 28,500 3,800 Both layer attributes merged → Soil props + Population data
Ex B – Intersect: Liquefaction zone ∩ Dense urban = Earthquake-vulnerable areas

Attribute Table Example — Intersect

Input A (Soil Type):

FIDSoil_TypePermeability
1ClayLow
2Sandy LoamHigh

Input B (Flood Zone):

FIDZoneRisk_Level
1Floodplain_AHigh

Output (Intersected — overlap only):

FIDSoil_TypePermeabilityZoneRisk_Level
1ClayLowFloodplain_AHigh
Key: Attributes from both Input A and Input B are joined in the output. Only the spatially overlapping area is kept. Sandy Loam (FID 2) is removed because it does not overlap with the flood zone.

C. Union Asked 8 times

Years: 2082, 2080, 2079, 2075 Magh, 2074 Magh, 2074 Bhadra, 2072, 2071

A B Input Layers ∪ A only A∩B B only A ∪ B (Everything preserved) Attributes: A + B combined; NULLs where non-overlap Output Table Zone A_attr B_attr A only Agri NULL A∩B Agri Clay B only NULL Clay
Fig 6.5 – Union: All areas preserved with combined attribute table; NULLs where non-overlapping

Exam Example

Exam Example: You are calculating the Runoff Curve Number for a hydrologic model (like mHM or HEC-HMS). You need to know the unique combinations of soil type and land use. You perform a Union on a "Soil Hydrologic Group" layer and a "Land Cover" layer. The output retains all spatial boundaries from both maps. The attribute table now has every polygon classified by both its soil type (e.g., Group B) and land use (e.g., Agricultural), allowing you to assign specific curve numbers to each unique plot.

Soil Groups Grp A Grp B Land Cover Agri | Forest | Urban ∪ Union Output: Unique Combos A + Agri A + Forest A + Urban B + Agri B + Forest B + Urban → Assign CN to each combo e.g. B + Agri → CN = 72 e.g. A + Forest → CN = 36 Output Table (Both attrs joined) FID Soil LandCover → CN Area_ha 1 Grp A Agricultural 67 45.2 2 Grp B Agricultural 72 33.8 3 Grp A Forest 36 60.1 Every unique plot gets Soil + LandCover Used for HEC-HMS Curve Number modelling
Ex C – Union: Soil Groups ∪ Land Cover = Unique combinations for CN assignment

Attribute Table Example — Union

Input A (Soil):

FIDSoil_Group
1Group A
2Group B

Input B (Land Cover):

FIDLandCover
1Forest
2Agriculture

Output (Union — everything kept):

FIDSoil_GroupLandCover
1Group AForest
2Group AAgriculture
3Group BAgriculture
4Group ANULL
5NULLForest
Key: Attributes from both layers are joined. All geometry is preserved. Where polygons overlap, both attributes are filled. Where only one layer exists, the other layer’s attributes are NULL. New polygons are created at every boundary intersection.

D. Dissolve Asked 6 times

Years: 2082, 2079, 2075 Magh, 2075 Bhadra, 2074 Bhadra, 2071

Before Dissolve Res Res Comm Res Res Comm 6 parcels, 6 rows Dissolve After Dissolve Residential Comm 2 zones, 2 rows Table Summary Before: Res | Res | Comm Res | Res | Comm After: Residential Commercial 6 rows → 2 rows
Fig 6.6 – Dissolve: Internal boundaries removed for parcels sharing the same attribute

Exam Example

Exam Example: You receive a highly detailed geological map with 50 different sub-classifications of soil types. For your preliminary analysis, you only need to differentiate between "Coarse-Grained" and "Fine-Grained" soils. You add a new attribute classifying them broadly, and use the Dissolve tool based on that new attribute. The tool erases the boundaries between adjacent polygons of the same broad category, merging hundreds of small polygons into just two massive geological zones.

50 Sub-classifications Sand Gravel Cobble Sandy-Gravel Clay Silt Silty-Clay Organic ... and 42 more sub-types 50 polygons, 50 rows Dissolve 2 Broad Categories Coarse-Grained Fine-Grained 2 polygons, 2 rows Result • 50 sub-types → 2 categories • Internal boundaries removed • Dissolved on "Broad_Class" • Attribute: only Broad_Class Simplifies preliminary analysis
Ex D – Dissolve: 50 soil sub-types merged into 2 broad geological categories

Attribute Table Example — Dissolve

Input (Parcels):

FIDParcel_IDLU_TypeArea_ha
1P-101Residential2.5
2P-102Residential3.1
3P-103Residential1.8
4P-104Commercial4.2
5P-105Commercial2.9

Output (Dissolved on LU_Type, Statistics: SUM of Area_ha):

FIDLU_TypeSUM_Area_haCount
1Residential7.43
2Commercial7.12
Key: Only one input layer is used. Rows with the same dissolve field value (LU_Type) are merged into one. Individual Parcel_IDs are lost. Numeric fields can be summarized (SUM, MEAN, MIN, MAX). 5 rows → 2 rows.

E. Buffer Asked 4 times

Years: 2082, 2080, 2079, 2075 Magh

Point Buffer d Circular zone Line Buffer Parallel corridor Polygon Buffer Expanded outline
Fig 6.7 – Buffer: Proximity zones around Points, Lines, and Polygons
Single Buffer vs. Multi-Ring Buffer Single Buffer Factory 500m One distance = one zone Multi-Ring Buffer 500m 300m 100m High risk Low risk Multiple distances = concentric zones ->
Fig 6.8 — Single Buffer vs. Multi-Ring Buffer: A single buffer creates one proximity zone; multi-ring buffers create concentric zones at different distances (e.g., 100m high-risk, 300m medium, 500m low-risk around a factory).

Exam Example

Exam Example: You are tasked with environmental compliance for a new road construction project. Regulations state that no heavy machinery can operate within 100 meters of a natural water body. You use the Buffer tool on the "Rivers and Lakes" vector layer, setting a distance of 100m. This generates a new polygon representing the restricted exclusion zone along the entire water network.

Road Construction Exclusion Zone Lake River 100m buffer = — No machinery Proposed Road [!] Buffer Output • New polygon: exclusion zone • BUFF_DIST = 100m • Inherits river/lake attributes • Road segment inside buffer = VIOLATION → reroute needed Environmental compliance check
Ex E – Buffer: 100m exclusion zone around rivers/lakes for road construction compliance

Attribute Table Example — Buffer

Input (Rivers):

FIDRiver_NameLength_kmOrder
1Bagmati51.44
2Bishnumati16.83

Output (100m Buffer):

FIDRiver_NameLength_kmOrderBUFF_DIST
1Bagmati51.44100
2Bishnumati16.83100
Key: Original attributes are inherited unchanged. A new column BUFF_DIST is added showing the buffer distance. Geometry changes from line → polygon. Same number of rows (unless dissolved). Feature geometry is now a polygon corridor around the original line.

F. Merge Asked 4 times

Years: 2075 Bhadra, 2074 Magh, 2074 Bhadra, 2072

KTM Roads 3 features Lalitpur Roads 2 features Merge Valley Road Network 5 features — rows stacked No geometry altered Attribute Table (vertical stack) FID Name Source 1 Ring Road KTM 2 Ratna Park Rd KTM 3 Tripureshwor KTM 4 Pulchowk Rd Lalitpur 5 Satdobato Rd Lalitpur ↑ Table A rows + Table B rows stacked ↓
Fig 6.9 – Merge: Separate datasets combined into one file; attribute rows stacked vertically

Exam Example

Exam Example: You are analyzing traffic volume across a large region, but the road network shapefiles were provided by two different municipal governments. You use the Merge tool to combine the "Municipality A Roads" and "Municipality B Roads" into a single, continuous transportation dataset, stacking their attribute tables together so you can run a unified spatial analysis.

Mun. A Roads 120 features + Mun. B Roads 85 features Merge Unified Network 205 features stacked Table Effect Mun A: 120 rows Mun B: 85 rows Output: 205 rows (stacked vertically) No geometry change
Ex F – Merge: Two municipal road shapefiles combined for unified traffic analysis

Attribute Table Example — Merge

Input A (Kathmandu Roads):

FIDRoad_NameTypeLength_m
1Ring RoadHighway2700
2Ratna Park RdLocal850

Input B (Lalitpur Roads):

FIDRoad_NameTypeLength_m
1Pulchowk RdCollector1200
2Satdobato RdLocal980

Output (Merged):

FIDRoad_NameTypeLength_m
1Ring RoadHighway2700
2Ratna Park RdLocal850
3Pulchowk RdCollector1200
4Satdobato RdLocal980
Key: Rows are stacked vertically (appended). No geometry is altered. FIDs are renumbered. If column names don’t match, unmatched columns get NULL values. Total rows = sum of input rows (2 + 2 = 4).

G. Erase Asked 1 time

Years: 2073

Input Erase removed Output: hole punched out
Fig 6.10 – Erase: The geometric opposite of Clip — removes overlapping portions

Exam Example

Exam Example: You are finding a suitable location for a new landfill. You have a polygon layer of "Available Government Land." However, you must avoid environmentally sensitive areas. You use the Erase tool, inputting the government land and using a "Protected Forests and Watersheds" layer as the erase feature. The output is the available land with the protected areas digitally "punched out" or removed.

Govt Land + Protected Areas Govt Land Protected Forest Watershed Erase Available for Landfill removed removed Protected areas punched out Result • Green areas = safe to build • Holes = protected zones • Only Govt Land attrs kept • Protected attrs discarded Opposite of Clip
Ex G – Erase: Protected forests/watersheds removed from available government land

Attribute Table Example — Erase

Input (Government Land):

FIDLand_IDStatusArea_ha
1GL-01Available250.0
2GL-02Available180.0

Erase Layer (Protected Forest):

FIDForest_NameProtection
1Shivapuri NPNational Park

Output (Erased):

FIDLand_IDStatusArea_ha
1GL-01Available145.2
2GL-02Available180.0
Key: Only Input layer attributes are kept. Erase layer columns (Forest_Name, Protection) are discarded. GL-01’s area shrinks (250 → 145.2 ha) because the overlapping part was removed. GL-02 is unchanged (no overlap). Opposite of Clip.

H. Map Join / Spatial Join Asked 1 time

Years: 2073

Ward Polygons + Boreholes Ward 1 Ward 2 Ward 3 BH1 BH2 BH3 BH4 Spatial Join Output: Borehole table with Ward attributes joined FID BH_ID SPT_N Depth_m ← Ward_No Ward_Pop Rock 1 BH1 12 15m 1 18,400 Gravel 2 BH2 8 20m 1 18,400 Gravel 3 BH3 22 12m 2 24,100 Sand 4 BH4 5 25m 3 9,750 Clay → Geometry unchanged; Ward columns appended by spatial location Red = original BH attributes | Blue = joined Ward attributes
Fig 6.11 – Spatial Join: Ward polygon attributes transferred to borehole points by location

Exam Example

Exam Example: You have a point layer representing hundreds of individual California Bearing Ratio (CBR) soil test locations along a proposed highway alignment, and a polygon layer representing different geological wards. A Spatial Join will append the ward information (like ward number and dominant rock type) directly into the attribute table of each individual CBR point based entirely on which polygon the point physically falls inside.

Highway + CBR Points + Wards Ward 5 Ward 6 Ward 7 Red dots = CBR test locations Spatial Join CBR Points + Ward Attrs Appended FID CBR_% Depth Soil_Type ← Ward_No Rock_Type Area_km² 1 8.2 1.5m Silty Sand 5 Gravel 12.3 2 5.4 2.0m Clay 6 Sand 18.1 3 12.1 1.0m Gravel 7 Slate 8.5 Point geometry unchanged — ward cols joined by location Red = CBR attrs | Blue = Ward attrs appended
Ex H – Spatial Join: CBR test points along highway automatically get ward attributes by location

Attribute Table Example — Spatial Join

Target Layer (Borehole Points):

FIDBH_IDSPT_NDepth_m
1BH-011215
2BH-02820
3BH-032212

Join Layer (Ward Polygons):

FIDWard_NoWard_PopRock_Type
1518,400Gravel
2624,100Sand

Output (Spatially Joined):

FIDBH_IDSPT_NDepth_mWard_NoWard_PopRock_Type
1BH-011215518,400Gravel
2BH-02820518,400Gravel
3BH-032212624,100Sand
Key: Target layer geometry is unchanged (still points). Join layer columns are appended horizontally based on spatial location (which polygon each point falls in). BH-01 and BH-02 both fall in Ward 5, so they get the same ward attributes. Same number of rows as target layer.

I. Update Asked 1 time

Years: 2073

Base Land Use (2020) Agri Forest Residential New\nAirport Red = Update layer Output Agri Forest Residential Airport (replaced) Old attrs overwritten in red zone Key Difference • Outside overlap: base unchanged • Inside overlap: update replaces • Only update's attrs in that zone ≠ Union (which keeps both attrs)
Fig 6.12 – Update: Base layer replaced by update layer in the overlapping zone

Exam Example

Exam Example: You have a master land-use map of a rural municipality from 2020. Recently, a "Smart Village" initiative successfully developed a specific ward, completely changing its infrastructure and land use. You use the Update tool to overlay the new 2026 ward data onto the old 2020 master map. The old map remains intact everywhere else, but the exact footprint of the upgraded ward is completely replaced by the new geometry and attributes.

Master 2020 Map Agriculture Forest Rural Settlement [*] target Old data + update target Update [OK] Updated 2026 Map Agriculture Forest Rural Settlement Smart Village Purple = replaced zone How Update Works • Outside target: 2020 data kept • Inside target: 2026 replaces • Old Agri/Forest attrs erased • New: Smart Village attrs only Partial map revision tool
Ex I – Update: 2020 rural map updated with 2026 Smart Village data in target ward

Attribute Table Example — Update

Base Layer (Land Use 2020):

FIDLU_TypeYearArea_ha
1Agriculture202080.0
2Forest2020120.0
3Residential202045.0

Update Layer (New Development 2026):

FIDLU_TypeYearArea_ha
1Smart Village202630.0

Output (Updated):

FIDLU_TypeYearArea_ha
1Agriculture202055.0
2Forest2020120.0
3Residential202045.0
4Smart Village202630.0
Key: Outside the overlap zone, base layer is unchanged. Inside the overlap, update layer replaces base attributes and geometry. Agriculture shrinks (80 → 55 ha) as part was replaced. Forest and Residential are untouched. The update polygon becomes a new feature in the output.

J. Split Asked 1 time

Years: 2073

Input: National Rivers Dist A Dist B Dist C Split layer = 3 districts Split River_DistA.shp File 1 River_DistB.shp File 2 River_DistC.shp File 3 3 separate shapefiles created Each file has its own attribute table (subset of original rows) Rivers clipped at district boundaries → independent files
Fig 6.13 – Split: Input layer broken into separate files using split polygon boundaries

Exam Example

Exam Example: You have a complete, national-level vector layer of every bridge in the country. For administrative distribution, you need to send files to the respective provincial transport offices. You use the Split tool, using a "Provincial Boundaries" polygon layer as the split feature. The tool automatically chops the national bridge layer into seven completely separate shapefiles, one for each province.

🇳🇵 All 7 Provinces + Bridges 850 total bridges Split Prov 1 ×120 .shp Prov 2 ×95 .shp Prov 3 ×180 .shp Prov 4 ×145 .shp Prov 5 ×110 .shp Prov 6 ×105 .shp Prov 7 ×95 .shp 7 Separate Files • 850 bridges → 7 files • Each province gets own .shp • Attrs split by province Sent to 7 transport offices
Ex J – Split: National bridge layer split into 7 provincial shapefiles for distribution

Attribute Table Example — Split

Input (National Bridges):

FIDBridge_NameTypeSpan_m
1Koshi BridgeSuspension120
2Bagmati BridgeBeam85
3Karnali BridgeCable-stayed500
4Trishuli BridgeArch65

Split Layer (Provinces): 7 provincial boundary polygons

Output File 1 — Province_1_Bridges.shp:

FIDBridge_NameTypeSpan_m
1Koshi BridgeSuspension120

Output File 2 — Province_3_Bridges.shp:

FIDBridge_NameTypeSpan_m
1Bagmati BridgeBeam85
2Trishuli BridgeArch65
Key: Input table is split into separate files, one per split polygon. Each output file has the same columns as the input. FIDs are renumbered in each file. Features are divided by which split polygon they fall into. 1 input → 7 output shapefiles.

4. Differentiating Specific Functions

PAST EXAM QUESTIONS ON THIS TOPIC:

  1. Differentiate between: (a) Clip and intersect (b) Merge and dissolve (2075 Bhadra, Q6a, Q6b)

Clip vs. Intersect

AspectClipIntersect
ConceptCookie-cutter — cuts input features using clip boundaryFinds the spatial overlap between two layers
Attribute outputOnly input layer attributes retainedAttributes from BOTH layers are joined in output
Geometry outputInput features trimmed to clip boundaryOnly the overlapping area from both layers
Number of inputsInput layer + Clip layerInput layer + Intersect layer
AnalogyUsing a cookie cutter on doughFinding the common area on a Venn diagram
Use caseExtract roads within a study area boundaryFind which land use types fall within a flood zone (need attributes of both)

Merge vs. Dissolve

AspectMergeDissolve
ConceptCombines multiple separate datasets into oneRemoves internal boundaries within a single dataset based on a common attribute
InputTwo or more separate feature classesOne feature class
Features in outputAll features from all inputs retainedFewer features — adjacent features with same attribute value are merged
Attribute handlingCombined (may have NULL for non-matching columns)Dissolve field retained; other fields can be summarized (SUM, MEAN)
Geometry changeNo change — features combined as-isInternal boundaries removed; external boundary preserved
Use caseCombine district-level shapefiles into national datasetMerge all "Residential" parcels into one polygon per zone
Clip vs. Intersect — Same Geometry, Different Attributes CLIP (Cookie-Cutter) Input A Attr: Name Clip B -> Output Shape of B Output Attribute Table FID A.Name 1 Road_X Only Input A attributes kept (B's table is discarded) INTERSECT (Spatial AND) Input A Attr: Name Input B Attr: Zone -> A ∩ B Overlap Output Attribute Table FID A.Name B.Zone 1 Road_X Zone_Y Both A and B attributes joined (Tables merged in output)
Fig 6.14 — Clip vs. Intersect: Both produce the same spatial output (the overlap), but Clip only retains Input A's attributes while Intersect joins both tables.

5. Prove that Intersection = Union + Clip

PAST EXAM QUESTIONS ON THIS TOPIC:

  1. Prove that Intersection = Union + Clip [part of 12] (2074 Magh, Q3e)

This mathematical/logical proof requires you to break down the operations step-by-step:

  1. Let Layer A be the Input Layer and Layer B be the secondary layer.
  2. The Union Step: Performing a Union on Layer A and Layer B results in a combined map containing three distinct geometric areas: A unique, B unique, and the Overlap (A ∩ B). Crucially, the attribute table now contains the joined columns of both A and B.
  3. The Clip Step: Take the output of the Union and Clip it using Layer B's exact boundary as the cookie-cutter.
  4. Clipping to Layer B removes anything outside of B (deleting A unique). We are left with only the area inside B. Since the problem asks for the interaction of A and B, clipping the unioned layer strictly to the overlapping zone isolates the spatial geometry of (A ∩ B).
  5. Conclusion: The final geometry is just the overlapping area. Because the first step was a Union, the attribute table contains the joined data from both A and B. A geometric overlap that contains the joined attributes of both input layers is the exact definition of an Intersection. Therefore, Union + Clip = Intersection.
Proof: Union + Clip = Intersect Start: A & B A B Two input layers Union After Union A only A∩B B only 3 zones, joined attrs Clip (using B) After Clip to B A∩B B A-only removed! = = Intersect(A,B) A ∩ B Joined attrs Q.E.D. Why does this work? 1. Union preserves all geometry AND joins both attribute tables. 2. Clipping to B removes A-only areas, leaving only the overlap with joined attributes. 3. Overlap + joined attributes = the exact definition of Intersect.
Fig 6.15 — Visual Proof: Union + Clip = Intersect. Union creates three zones with joined attributes; Clipping to B removes A-only, leaving only the overlap — which is exactly what Intersect produces.

1. The Theory Question

PAST EXAM QUESTIONS ON THIS TOPIC:

  1. Define the term spatial analysis. Explain different types of vector overlay operations in GIS. Also explain three examples of neighborhood functions [2+4+4] (2071 Magh, Q7)

Question: Define the term spatial analysis. Explain different types of vector overlay operations in GIS. Also explain three examples of neighborhood functions. [2+4+4]

A. Definition of Spatial Analysis (2 Marks)

Spatial analysis is the core analytical process in GIS where we extract or create new information about a set of geographic features. It involves evaluating suitability, predicting outcomes, measuring proximities, and modeling relationships between spatial data to solve complex engineering and planning problems.

B. Types of Vector Overlay Operations (4 Marks)

Vector overlay involves combining two or more separate polygon layers to create a completely new layer containing both the spatial boundaries and the attribute data of the inputs.

Intersect (The "AND" Operator): Keeps only the overlapping regions of the input layers. The output attribute table combines data from both.

Union (The "OR" Operator): Keeps the entire extent of all input layers. Polygons are split wherever lines cross, and the attribute table joins all data.

Identity / Erase: Identity keeps the base map's boundaries but adds the overlay's attributes. Erase completely removes the overlapping portions from the base map.

C. Three Examples of Neighborhood Functions (4 Marks)

Neighborhood functions analyze the relationship between a target feature and its surrounding area.

  1. Buffering: Creating a zone of a specified distance around a point, line, or polygon (e.g., establishing a 100m no-build zone around a river).
  2. Near / Distance Analysis: Calculating the exact shortest distance from one feature to another (e.g., finding the distance from a proposed school to the nearest existing hospital).
  3. Thiessen Polygons (Voronoi Diagrams): Creating boundaries around a set of points so that any location inside a given polygon is closer to that polygon's central point than to any other point (e.g., mapping the service areas for different rainfall stations).
Three Neighborhood Functions 1. Buffering 100m zone d Creates proximity zone at specified distance e.g., 100m no-build zone New polygon output 2. Near / Distance School Hospital d = 2.3 km Market Calculates shortest distance between features Numeric output (meters) 3. Thiessen (Voronoi) Stn A Stn B Stn C Zone A Zone B Zone C Any point in Zone A is closer to Stn A than B or C
Fig 6.16 — Three Neighborhood Functions: (1) Buffering creates proximity polygons, (2) Near/Distance calculates shortest distances between features, (3) Thiessen (Voronoi) polygons assign service areas so every location is closest to its generating point.

Landfill Site Selection Workflow

PAST EXAM QUESTIONS ON THIS TOPIC:

10 Marks

Question: Write about the necessary tools and explain how you will perform the following analyses using GIS: Best location for landfill area so that following constraints are fulfilled: Houses > 1000m, River > 1500m, Road < 500m, Water bodies > 1500m. Provided data: Shapefile of river, land use data, point data of the houses, shapefile of roads, polygon shapefile of the study area. [10]

Here is the precise step-by-step workflow you need to write:

Step 1: Buffer the Restricted Features (Tool: Buffer)

Since a landfill is hazardous, it must be far from people and water. We buffer the restrictions:

Step 2: Combine the Restricted Zones (Tool: Union or Merge)

Use the Union tool to combine the three buffers from Step 1 into a single, massive "Restricted Area" polygon layer.

Step 3: Extract the Available Land (Tool: Erase)

Take the total "Study Area" polygon as the input feature, and use the "Restricted Area" from Step 2 as the erase feature. The output is a map of the "Available Land" where it is legally safe to build.

Step 4: Buffer the Favorable Proximity Feature (Tool: Buffer)

The site must be accessible for garbage trucks. Buffer the "Road" line shapefile by 500m to create the "Accessibility Zone".

Step 5: Isolate the Final Suitable Sites (Tool: Intersect)

Intersect the "Available Land" (from Step 3) with the 500m "Road Buffer" (from Step 4). The resulting polygons are the exact locations that meet every single distance constraint.

Step 6: Filter by Appropriate Land Use (Tool: Select by Attributes)

Using the provided "Land use data" shapefile, perform a Spatial Join with your final sites. Then, run an SQL query (e.g., SELECT * WHERE Land_Use = 'Barren') to ensure the landfill isn't placed on top of agricultural or forested land.

(Make sure to sketch a simple conceptual flowchart or a mock map showing a road with a buffer overlapping an available land polygon to secure the full 10 marks!)

Step 1: Buffer [H] Houses →1000m River →1500m Water →1500m Step 2: Union Combine all 3 buffers into one RESTRICTED ZONE — single polygon Step 3: Erase Study Area − Restricted Zone Step 4: Buffer Road ≤ 500m Accessibility Zone Step 5 Intersect Available ∩ Road Buf [OK] Suitable! Step 6: Select by Attributes — SQL query (Land_Use = 'Barren') to filter final sites Spatial Join with Land Use layer → filter out agricultural / forested land Buffer(restrictions) → Union → Erase(from study area) → Buffer(road) → Intersect → Select → [OK] Final Site
Fig 6.17 – Landfill Site Selection Workflow: Step-by-step GIS analysis using Buffer, Union, Erase, Intersect, and Select

Flood Plain Analysis Workflow

PAST EXAM QUESTIONS ON THIS TOPIC:

  1. Using GIS, perform the following analyses: (a) Locate settlements within 1 km of rivers, (b) Flood plain zoning, (c) Agricultural land in flood plain. Provided data: river shapefile, settlement point data, land use polygon shapefile, DEM, study area boundary. [10] (2073 Bhadra, Q6)

This is a multi-step vector analysis problem that uses Buffer, Intersect, and Select operations to answer three related flood-risk questions.

Part (a): Locate Settlements Within 1 km of Rivers

  1. Buffer the river line shapefile by 1,000 m (1 km) on both sides. Output: "River_Buffer_1km" polygon.
  2. Intersect (or Clip) the settlement point data with the River_Buffer_1km polygon.
  3. Output: Only the settlement points that fall inside the 1 km river buffer — these are the at-risk settlements.

Part (b): Flood Plain Zoning

Flood plain zoning classifies land adjacent to rivers into risk zones based on distance.

  1. Create multiple buffers around the river at different distances:
    • 0–500 m → High Risk Zone (Zone A — Floodway)
    • 500–1,000 m → Moderate Risk Zone (Zone B — Flood Fringe)
    • 1,000–2,000 m → Low Risk Zone (Zone C)
  2. Erase the smaller buffer from each larger one to create distinct ring-shaped zones (e.g., 1000m buffer ERASE 500m buffer = Zone B only).
  3. Alternatively, use Multiple Ring Buffer tool (available in ArcGIS/QGIS) to create all zones at once.
  4. Optionally intersect with DEM-derived low-elevation areas to refine the flood plain boundary using actual topography rather than distance alone.

Part (c): Agricultural Land in Flood Plain

  1. Take the flood plain polygon from Part (b) (e.g., the combined High + Moderate risk zones, or the 1 km buffer).
  2. Intersect the flood plain polygon with the land use polygon shapefile. The output contains all land use parcels that fall within the flood plain, with attributes from both layers.
  3. Select by Attributes: Run SQL query SELECT * WHERE Land_Use = 'Agriculture' on the intersected output.
  4. Output: Polygons showing only the agricultural land that lies within the flood plain — this is the cropland at risk of flood damage.
  5. Optionally, calculate the total area: use the Calculate Geometry tool to sum the area of all selected agricultural polygons.

Summary of Tools Used

StepGIS ToolInputOutput
(a) Settlements near riversBuffer + IntersectRiver line + Settlement pointsAt-risk settlement points
(b) Flood plain zoningMultiple Ring Buffer + EraseRiver lineZoned flood plain polygons
(c) Agriculture in flood plainIntersect + Select by AttributesFlood plain polygon + Land use polygonAgricultural land at risk

Figure-Based Question: Clip, Buffer, Intersect, Union

Figure below shows 2 roads, 7 buildings as points, and the area of interest (AOI) as polygon layers. (a) Sketch the road and building layers after clipping with the AOI polygon (assume clip-road and clip-bld are the outputs respectively). (b) Draw the 50 m buffer for each of the clipped layers along with clip-road and clip-bld layers (assume buffered layers are named as buf-road and buf-bld respectively). (c) Sketch the intersection of buf-road and buf-bld and also show the output fields. (d) Sketch the union of buff-road and buf-bld and also show the output fields.

(a) Clip to AOI AOI Red = clip-road; Blue = clip-bld (b) 50m Buffers buf-road (red) + buf-bld (blue) (c) Intersect Only where buf-road ∩ buf-bld Fields: Road_* + Bldg_* (d) Union Everything kept Fields: Road_* + Bldg_* (NULLs) (c) Intersect Output Fields [FID] [Shape] [Road_fid] [Road_name] [Road_type] [Bldg_fid] [Bldg_name] Both tables joined — only overlapping features (d) Union Output Fields [FID] [Shape] [Road_fid] [Road_name] [Bldg_fid] [Bldg_name] Same fields — NULL where no overlap Note: Intersect keeps only overlap zones; Union keeps everything with NULLs for non-overlap
Fig 6.18 – Figure-based Question: AOI with Roads + Buildings → Clip → Buffer → Intersect vs Union

(a) Sketch the clipped layers (2 Marks)

(b) Draw the 50m Buffers (2 Marks)

(c) Sketch the Intersection and show output fields (3 Marks)

(d) Sketch the Union and show output fields (3 Marks)

Chapter Summary

This chapter covers vector-based spatial analysis in GIS, divided into data management and data analysis functions. Data management functions include: coordinate transformation (affine, projective, polynomial), edge matching, rubber-sheeting, conflation, and map-to-map transformation. Data analysis functions form the core: retrieval/classification/measurement (attribute and spatial queries), overlay operations (point-in-polygon, line-in-polygon, polygon-on-polygon using Union, Intersect, Identity, Erase, Symmetrical Difference), buffer analysis (point/line/polygon buffers with fixed or variable width), network analysis (shortest path, allocation, tracing), and spatial join operations. Each overlay operation produces different output geometries and attribute combinations. Buffer analysis creates proximity zones critical for environmental impact assessment, infrastructure planning, and zoning regulations. Network analysis enables routing, service area delineation, and facility location optimization.