Download Kihunga map in PostGIS SQL format

A map built from OpenStreetMap data, ready to download

Customize the map

Open this place's area in the constructor and adjust everything to your needs

Open in constructor →

Map passport

Area2.0 km²
Buildings86
Roads51 km
Points of interest1

What this map contains by default

This is how the map is built as-is — every setting can be changed in the constructor.

FormatPostGIS SQL .sql
LayersRoads, Buildings, Greenery, Points of interest change
Stylestandard change
Detailauto change
House numbersall change
Points of interestall but cafés, shops and services — the editor adds those change
Coordinate systemWGS 84 (auto) change
Sheet sizeauto change
Relief & gridoff change

About PostGIS SQL

Map of Kihunga in PostGIS SQL — an export of real OpenStreetMap data for the selected area.

PostGIS SQL is a text SQL script that creates a table with a geometry column and fills it with data, ready to load into any PostgreSQL database with the PostGIS extension. It is a convenient way to hand an OSM selection to a team already on the PostgreSQL stack: apply the script and you immediately have a geometry table for queries through ST_* functions. Our exporter generates a self-contained .sql: CREATE TABLE with a geom column and attributes, then one INSERT per feature where geometry is given via ST_GeomFromText(WKT, SRID) (SRID 4326 by default). Multiple layers become separate tables, and values are escaped (SQL-injection safe). Honestly: this is a simple human-readable dump via ST_GeomFromText, not a binary pg_dump archive and not the full osm2pgsql schema with planet_osm tables and spatial indexes.

Which layers are in the file

This file for the selected area contains:

Coordinate systems

WGS 84 (EPSG:4326), selectable in the wizard

Units

Meters (projected in the chosen coordinate system)

CategoryGIS
File extension.sql
TierOpen Beta

How to use PostGIS SQL for Kihunga

  1. psql — create the database, run CREATE EXTENSION postgis, then psql -d your_database -f dump.sql; the layer tables appear right away together with the indexes.
  2. DBeaver or pgAdmin — open the file as a script and run it as a whole, if working in a terminal is inconvenient.
  3. Before applying it — look through the beginning of the file: it shows which tables will be dropped and created anew.

Programs that open PostGIS SQL

PostgreSQL + PostGISpsqlQGISGeoServerDBeaver

FAQ: PostGIS SQL for Kihunga

Is this a pg_dump dump?

No. We generate a human-readable SQL script with CREATE TABLE and INSERT via ST_GeomFromText, applied through psql -f. It is not a binary custom-format pg_dump archive.

Will this be the osm2pgsql schema with planet_osm tables?

No. We create simple per-layer tables with a geom column and attributes. The full osm2pgsql schema (planet_osm_polygon/line/point/roads with GiST spatial indexes) is not reproduced here.

How do I apply the script?

Create a database with CREATE EXTENSION postgis, then psql -d your_db -f dump.sql. The geometry tables appear immediately, ready for ST_* queries.

Which coordinate system is the geometry in?

SRID 4326 (WGS84) by default. It is written into ST_GeomFromText and into the geometry column definition.

Are indexes created?

Yes, for every table the script adds a GiST spatial index on the geom column — queries by area work fast right after it is applied. Indexes on attribute fields you create yourself if you need them.

Other formats for Kihunga

All 128 formats for Kihunga →

PostGIS SQL for nearby places

All formats for Kihunga