WKB 🧮

Well-Known Binary (OGC)

Open Beta
.wkb · application/vnd.ogc.wkb

WKB (Well-Known Binary) is the binary representation of vector geometry from the OGC Simple Features standard (1999), the foundation of almost every GIS database: each geometry inside PostGIS, MySQL Spatial or GeoPackage is WKB. The format is several times more compact than textual WKT because coordinates are packed into doubles without ASCII. Our exporter writes the geometries of the selected OSM layers into a .wkb file: every object is standard OGC WKB, but the file is a container — an 8-byte header (a WKB marker plus the number of objects), then geometries with a length prefix, while the coordinate system lies in a companion .prj file. Honestly: to parse the file you have to read the header and the lengths — this is not a single "bare" blob for a direct ST_GeomFromWKB. Attributes are not preserved, and all the selected layers are merged into one stream of geometries (up to 500,000 objects).

今すぐWKBをエクスポート ✨ オープンベータ — 無料、制限なし

主な機能

Each feature's geometry is standard OGC WKB
Container: an 8-byte header + length-prefixed geometries
Coordinate system in a companion .prj (WKT) file
Several times more compact than text WKT (doubles without ASCII)
Single layer — a .wkb file, multiple layers — a ZIP archive

WKBフォーマットについて

WKB is the binary encoding of geometry from the OGC Simple Features standard: byte order, a shape type code and coordinates as double-precision numbers. Inside PostGIS, GeoPackage and SpatiaLite geometry is stored exactly like this, which is why WKB is read and written by every spatial library — Shapely, GEOS, JTS, GDAL.

This export is taken by people writing their own pipeline: parsing without going through text, loading into a database, testing their own implementation of the standard, compact transfer of geometry between services.

You need to know how the file is arranged in advance. This is not one "bare" geometry but a container: eight bytes of header (a WKB marker and the number of objects), then geometries one after another, each preceded by its length. The geometries themselves are standard OGC WKB and can be fed into ST_GeomFromWKB one by one once the container is parsed. The coordinate system lies in a neighboring .prj file in text form.

The limits: OpenStreetMap attributes are not preserved — geometry only, and all the selected layers are merged into a single stream with no separation. The ceiling is 500,000 geometries. If you need names, tags and layers, take GeoPackage, FlatGeobuf or GeoJSON.

WKBファイルを開けるプログラム

次のプログラムおよびアプリケーションは、OSM2CDRからエクスポートしたWell-Known Binary (OGC)(.wkb)ファイルを開き、編集し、利用できます:

💻PostGIS 💻Shapely (Python) 💻GDAL/OGR 💻JTS / GEOS 🌎QGIS

Format specifications

WKB地図を利用するユーザー

🏗
Building a custom GIS pipeline on Shapely, JTS, or GEOS without parsing GeoJSON
Geometry is read straight into Shapely, JTS or GEOS — with no intermediate text parsing.
💻
Loading geometry into PostGIS or MySQL after parsing the container header
Parsed geometries are fed into ST_GeomFromWKB and land in PostGIS or MySQL.
📊
Checking your implementation against the OGC Simple Features standard
Convenient material for testing your own implementation of the OGC standard on real city data.
🎨
Compact geometry transfer between services as a binary exchange
Compact binary exchange of geometry between services, where text is excessive.

WKBのエクスポート方法

1
範囲を選択
osm2cdr.ruのインタラクティブ地図上で長方形またはポリゴンを描画します
2
WKBを選択
利用可能な127種類のエクスポートフォーマットの一覧からWell-Known Binary (OGC)を選択します
3
エクスポート
「エクスポート」をクリックすると、1〜5分で.wkbファイルを受け取れます
4
ダウンロード
完成したWKBファイルをダウンロードし、PostGISで開きます

エクスポート後の開き方

WKBの人気地図

フリー

Well-Known Binary (OGC)の地図エクスポートを入手

OpenStreetMapからプロフェッショナルなWKB地図をダウンロード。即時生成、任意の範囲に対応。

無料 /エクスポート
今すぐWKBをエクスポート →

よくある質問

Can I INSERT it directly via ST_GeomFromWKB?
Where is the coordinate system stored?
How does WKB differ from WKT?
How do I read WKB in Python?
Are OSM names and tags preserved?
How do I tell one layer from another?
How many objects fit into the file?

関連フォーマット

よく一緒にエクスポートされるフォーマット

Related Articles