How to export Istanbul Metro station coordinates

Exporting station coordinates from the Istanbul Metro Map turns a transport diagram into usable geographic data. The resulting points can support an interactive map, route-planning prototype, field guide, or custom transit display. A reliable file needs more than copied pin positions: each record must identify its station, preserve its source, and state the coordinate reference system.

Begin by deciding what a point represents—entrance, concourse, platform, or interchange cluster—and by checking the current official network. The process below covers native map exports, browser inspection, open map data, and the coordinate conventions used in Australian GIS and transit projects.

Choose a reliable coordinate source

The Metro Istanbul map maintained by IETT is the best starting point for station names, line assignments, and the current shape of the network. However, a schematic metro diagram often displays stations as symbols rather than geographically accurate markers. Its spacing may prioritise readability over real-world distance.

A geographic map based on OpenStreetMap, Google Maps, or another navigation service is more useful for extracting coordinates. Google Maps may identify a station entrance rather than its platform, while OpenStreetMap can represent several entrances or platforms belonging to the same interchange. OpenStreetMap data also needs local review because tagging styles vary between contributors.

Use the official network map to confirm which places qualify as stations and the operator’s English and Turkish names. Use a geographic map or open transport dataset to obtain the point coordinates. Recording the source and retrieval date prevents later confusion when lines, extensions, or station names change.

Use the map’s export and data tools

If the interactive map provides an Export, Download, Share, or Data option, use it before attempting manual extraction. CSV is convenient for spreadsheets and database imports, while GeoJSON is widely supported by web mapping libraries and preserves point geometry. KML can also be opened in Google Earth, QGIS, and ArcGIS. Download the untouched original file first, then work on a copy.

When no export button is available, inspect the map data in a desktop browser. In Chrome or Edge, open Developer Tools, select Network, reload the page, and look for Fetch or XHR responses containing JSON, GeoJSON, or station objects. Search the response for a familiar station name and record its latitude and longitude. Do not convert screen pixels into coordinates without first identifying the map projection and viewport.

OpenStreetMap’s Overpass Turbo service provides a repeatable alternative for geographic points. A broad Istanbul-area query can be refined to metro stations:

[out:csv(::type,::id,name,operator,::lat,::lon;";",true)];
(
  nwr["railway"="station"]["station"="subway"](40.90,28.80,41.25,29.15);
  nwr["railway"="station"]["public_transport"="station"](40.90,28.80,41.25,29.15);
  nwr["railway"="halt"]["station"="subway"](40.90,28.80,41.25,29.15);
);
out center;

Run the query, inspect the results, remove non-metro records, and export the remaining data as CSV. OpenStreetMap is collaborative data, so validate important entries against the official Metro Istanbul source.

Fields worth retaining in every export

Define the record structure before combining files from different sources. A useful station export normally contains the following information:

Keep Turkish characters such as İ, ş, ğ, and ü intact by saving the file as UTF-8. English names should be treated as display labels, while the original names help distinguish similarly translated or transliterated stations.

Coordinate order must be explicit. GeoJSON expects [longitude, latitude], while many CSV templates place latitude first. Use clearly named columns such as latitude and longitude, and declare EPSG:4326 in accompanying metadata. Australian projects generally use a decimal point, so values such as 41.0100, 28.9600 should not be reformatted with comma separators.

Decide how to handle duplicated entrances and multiple platforms. They may be retained as separate features with a shared station_id, or reduced to one representative interchange point. Whichever method is used should be applied consistently across the entire dataset.

Align coordinates with Australian mapping systems

Australian mapping projects commonly use the Geocentric Datum of Australia 2020, or GDA2020. WGS84 and GDA2020 agree closely for general web mapping, but projected coordinates still require an appropriate Australian Map Grid of Australia zone. For example, Sydney and Brisbane use MGA zone 56, Melbourne and Canberra use zone 55, Adelaide uses zone 54, and Perth uses zone 50.

This matters when the Istanbul dataset is combined with records from Transport for NSW and Sydney Trains, Transport Victoria and Metro Trains Melbourne, Translink in southeast Queensland, or Transperth in Perth. These systems commonly exchange GTFS data with stable service and stop identifiers, so preserving a clear source ID makes future matching more dependable.

Keep the original WGS84 file for web maps and global analysis. Create a projected copy when integrating the stations with Australian council datasets, engineering plans, delivery zones, or custom transit applications. For GDA2020 MGA zone 56, GeoPandas can perform the conversion:

stations = gpd.read_file("istanbul_stations.geojson")
projected = stations.to_crs("EPSG:7855")
projected.to_file(
    "istanbul_stations_mga56.gpkg",
    layer="stations",
    driver="GPKG"
)

GeoPackage is useful for the projected output because GeoJSON is intended primarily for geographic coordinates. Keep both versions and document the transformation in a short metadata file.

Checks that protect the final dataset

A final validation pass should test the export independently of the source map. Use these checks before publishing or importing the coordinates:

Six decimal places may suggest precision to within centimetres, but the underlying source might be accurate only to several metres. Retain the original values rather than adding false precision. Exporting to a new format can also alter field names or character encoding, so reopen the converted file and inspect a sample of Turkish and English records.

The domain currently shows FastComet’s default placeholder rather than the finished guide. After the coordinate file is complete, create the article through the cPanel file manager, upload the final page and any supporting assets, and test the public URL. Visitors should reach the metro-coordinate guide instead of the hosting notice.

The enduring result is a source-documented WGS84 CSV or GeoJSON file whose station names, coordinate order, and geographic positions have all been verified.