Working with data that no longer fits in a spreadsheet — property tax rolls, census records, sensor feeds, a state's full parcel layer — and asking spatial questions of it in the database rather than exporting it first.
What you will be able to answer
A city's property tax roll and its parcel layer are two files nobody can open together, and the commissioner wants collection by ward. How do you answer that without exporting anything?
Load both into the database with column types that match the data, join the roll to the parcels on the property key, then combine a spatial predicate with grouping so collection is summed per ward in a single query rather than by hand. A left join is the deliberate choice — it keeps the tax records that match no parcel, and those unmatched rows are usually the finding rather than an error to discard. A spatial index on the parcel geometry is what keeps the join workable at that size, and QGIS can read the query result as a live layer instead of another exported shapefile.
One payment
₹99
The videos are free
Course outline
Concept 1
Concept 1 · When a spreadsheet stops being the right tool
Concept 2
After: when-a-spreadsheet-breaks
Video title and channel appear once unlocked.
Concept 3
After: what-sql-is
A foreign key linking an employee table to a department table, with referential integrity visible in the data.
Video title and channel appear once unlocked.
Concept 4
After: tables-and-keys
SELECT, multi-condition WHERE, ORDER BY and LIMIT executed live with output on screen.
Video title and channel appear once unlocked.
Concept 5
After: select-where
GROUP BY with HAVING, filtering the groups rather than the rows.
Video title and channel appear once unlocked.
Concept 6
After: aggregation
A LEFT JOIN executed so unmatched rows survive as NULLs you can actually see.
Video title and channel appear once unlocked.
Concept 7
After: joins
One complex query decomposed into named stages, set against the nested version it replaces.
Video title and channel appear once unlocked.
Concept 8
After: joins
Execution plans before and after an index, plus what that index costs on writes.
Video title and channel appear once unlocked.
Concept 9
After: tables-and-keys
A table created with matching column types, then a CSV imported into it.
Video title and channel appear once unlocked.
Concept 10
After: loading-data, select-where
ST_SRID and ST_AsText run against a geometry column to see what is actually stored.
Video title and channel appear once unlocked.
Concept 11
After: postgis-geometry
ST_Intersects joining boundary polygons to a hex grid in a single query.
Video title and channel appear once unlocked.
Concept 12
After: spatial-predicates, aggregation
ST_Contains combined with GROUP BY to count points inside each polygon.
Video title and channel appear once unlocked.
Concept 13
After: spatial-predicates
A PostGIS connection created in QGIS, and a spatial layer pushed straight into the database.
Video title and channel appear once unlocked.
10 candidates did not meet the course criteria.
Spatial-data and analytics roles — building GIS systems, remote-sensing pipelines, urban dashboards, and data products for planning clients, authorities, and tech/geospatial firms. Strong demand where planning meets data. Specialisation tags: Urban, Regional, Environmental (cross-cutting).
9 mapped employers
Explore path →Central-government planning at the Town & Country Planning Organisation (under MoHUA) and bodies like the National Capital Region Planning Board. You work on national urban policy, regional plans, model guidelines, and inter-state coordination. Seats are very limited, UPSC/TCPO notifications are intermittent, and entry is prestigious. Specialisation tags: Urban, Regional, Infrastructure.
10 mapped employers
Explore path →