OSM-Wikidata Map Framework

From OpenStreetMap Wiki
Jump to navigation Jump to search
OSM-Wikidata Map Framework
Wikiraduno Bologna marzo 2023 - Screenshot Certosa di Bologna - Open Burial Map - nodo Tomba Borghi-Mamo abc2.png
Author: User:Danysan
License: GNU GPL (free of charge)
Platform: Web
Status: Active
Language: multiple languages
Source code: GitLab (primary)

GitHub (mirror) GitHub

Programming languages: Python, TypeScript, HTML, and CSS

Merge data from OpenStreetMap and Wikidata to map information about entities and points of interest

Features
Feature Value
Map Display
Display map yes
Map data vector
Source online;cache
Rotate map yes
3D view yes
Shows website yes
Shows phone number no
Shows operation hours no
Routing
Routing no
Create route manually
Calculate route
Create route via Waypoints
Routing profiles
Turn restrictions
Calculate route without Internet (Offline routing)
Routing providers
Avoid traffic
Traffic Provider
Navigating
Navigate no
Find location
Find nearby POIs
Navigate to point
Navigation with voice / Voice guidance
Keep on road
Lane guidance
Works without GPS
Navigate along predefined route
Tracking
Make track no
Customizable log interval
Track formats
Geotagging
Fast POI buttons
Upload GPX to OSM
Monitoring
Monitoring no
Show current track
Open existing track
Altitude diagram
Show POD value
Satellite view
Show live NMEA data
Show speed
Send current position
Editing

(Not set)

Rendering

(Not set)

Accessibility

(Not set)

Framework for creating interactive thematic maps that combine details about geographic features from OpenStreetMap and Wikidata and optionally associated entities.

Available back-ends

APIs updated minutely:

APIs updated weekly:

Updated manually:

  • Custom vector tiles
    • the only back-end that also allows to view data at low zoom
    • initialized and updated semi-automatically with Apache Airflow, served through PMTiles

Available presets

Each preset available to be used in the framework is specified in a JSON file in this folder. Each file must be a JSON object whose keys are documented in this file.

If you would like to have a new preset don't hesitate to open an issue (or pull request) on GitHub or GitLab.

architect

Displays the architects who created buildings and structures

Keys and properties used to find the associated entities which represent the architect/organization which designed the feature:

Elements from OSM that have only linked architects through wikidata=* are shown only if they also have one of the following tags:

See it in action on Open Architect Map

artist

Shows the artists who designed artworks and memorials.

Keys and properties used to find the associated entities which represent the artist(s) which realized the feature:

Elements from OSM that have only linked artist through wikidata=* are shown only if they also have one of these tags:

See it in action on Open Artist Map or Wiki.NYC map

base

Shows all geographic features with a link between OpenStreetMap and Wikidata, without filters or linked entities.

See it in action on OSM-Wikidata Map

burial

Displays details about burial places and notable people buried in them

Keys and properties used to find the associated entities which represent who is buried inside the feature:

Elements from OSM that have only buried people through subject:wikidata=* or wikidata=* are shown only if they also have one of the following tags:

Images of burial places are also obtained with P1442 (image of grave) on linked entities.

See it in action on Open Burial Map or Wiki.NYC map

etymology

Displays the etymology of names of streets and points of interest.

Keys and properties used to find the associated entities which represent what the feature is named after:

Elements from OSM that have only etymologies through subject:wikidata=* or wikidata=* are shown only if they also have the name=* key.

See it in action on Open Etymology Map or Wiki.NYC map

green_spaces

All green spaces from OpenStreetMap and Wikidata, without linked entities.

Elements from OSM are shown only if they include one of the following tags:

Entities from Wikidata are shown only if they are instance of (P31) one of the following classes or one of their immediate subclasses (P279):

See it in action on Wiki.NYC map

holy_well_etymology

Displays the etymology of names of holy wells (see this video for some context).

Keys and properties used to find the associated entities which represent what the feature is named after:

Elements from OSM are shown only if they include the tag place_of_worship=holy_well.

Entities from Wikidata are shown only if they are instance of (P31) one of the following classes or one of their immediate subclasses (P279):

holy_wells

All holy wells from OpenStreetMap and Wikidata, without linked entities (see this video for some context).

Elements from OSM are shown only if they include the tag place_of_worship=holy_well.

Entities from Wikidata are shown only if they are instance of (P31) one of the following classes or one of their immediate subclasses (P279):

protected_areas

All protected areas from OpenStreetMap and Wikidata, without linked entities.

Elements from OSM are shown only if they include one of the following tags:

Entities from Wikidata are shown only if they are instance of (P31) one of the following classes or one of their immediate subclasses (P279):

Example instances

Open Architect Map

Used preset: architect

Examples:

Open Artist Map

Used preset: artist

Examples:

OSM-Wikidata Map

Used preset: base

Open Burial Map

Used preset: burial

Examples:

Open Etymology Map

Used preset: etymology

Examples:

  • Moers (Germany), with source statistics: link
  • Moers (Germany), with gender statistics: link
  • Moers (Germany), with type statistics: link
  • San Francisco (USA), with occupation statistics: link
  • San Francisco (USA), with birth century statistics: link
  • San Francisco (USA), with death century statistics: link

Wiki.NYC map

Used presets: etymology, burial, artist, green_spaces

Configuration

The types of geographic features and related entities to show are choosen by editing a configuration file and automatically handled by the framework.

The available configurations are documented in .env.example. Instantiation, configuration and Database initialization instructions can be found in this presentation.

Other links