Bridge and Truck Restrictions Import

From OpenStreetMap Wiki
Jump to navigation Jump to search

Bridge and Truck Restrictions Import

Bridge and Truck Restrictions Import enhances OSM by adding missing bridge data from the National Bridge Inventory (NBI). Once that is done, the import will add truck restrictions data to all the bridges including missing bridges added as part of this import. The import is currently ongoing as of 5/30/2024 and is in the planning stage.

Goals

The overall goal is to enhance OSM bridge data and then add truck restriction information to the bridge data already included in OSM. This will be a two-phase process. In the first phase, we will add all the missing bridge data. In the second phase, we will add truck restriction data to all the bridges. The actual data to be imported and some of the code used for pre-processing is available on GitHub.

Schedule

The import process will commence in June 2024 and is expected to proceed in phases, starting with the addition of missing bridge data followed by the inclusion of truck restrictions. Once done, we will periodically update OSM with NBI data at regular intervals, at least once every quarter.

Import Data

Background

This import involves the addition of approximately 600,000 bridges across the USA using NBI data. The data is publicly available under a public domain license, suitable for use with OSM. Additionally, we used water stream data from the National Hydrography Dataset (NHD).

Data source site

National Bridge Inventory and National Hydrography Dataset

Type of license

Public domain license (unrestricted public use).

OSM Data Files

The processed data files for this import will be available here: Processed Bridge Data

Import Type

This is an ongoing import of bridge and truck restrictions data. We will be using JOSM scripting to automate the process of adding bridge nodes and splitting ways.

Data Preparation

Data Reduction & Simplification

We cross-referenced with existing OSM bridges to identify missing bridges (not marked as bridge=yes). We used two methods. Method 1- buffer and join method in QGIS along with the National Hydrography Dataset (NHD) to match bridge locations to the correct OSM ways.

Method 2 - We also employed geometric projection and interpolation methods to further align bridge coordinates with OSM ways.

We compared the data developed between the two methods to give better results.

Tagging Plans

We will be adding the "bridge=yes" tag to the identified ways connecting the start and end nodes of the bridges. We are getting the bridge span distance from the NBI database. Also, all such bridge entries will be tagged with source=nbi_bridge_inventory.

Changeset Tags

Changeset tags will include: #osm-bridges-mapup

Data Transformation

We downloaded OSM road layer data from Geofabrik. Using bridge data from the National Bridge Inventory (NBI) and river data from the National Hydrography Dataset (NHD), we accurately associated NBI bridges with OSM ways where bridges are actually located. These OSM ways will be tagged as “bridge=yes” in OSM.

Once the data is manually verified, we add it to OSM using a Python script. This script locates two points equidistant from the bridge midpoint along a specified path or way. The script identifies the closest point on the path, calculates forward and backward points, and converts these points to standard coordinates, which will be further used to create ways on OSM and tag them as “bridge=yes” for accurate integration into OSM.

Data Transformation Results

The final file used for the import can be viewed here: Processed Bridge Data

Data Merge Workflow using JOSM

Team Approach

The work will be divided into manageable cells among the following team, ensuring collaborative and efficient data integration.

username role
aayudhi-choudhary-mapup Project Manager
ajay-padwal-mapup Coordinator
atharv-diwan Editor
deepak-bisht-mapup Editor
Maneesh-Mahlawat Project Manager
saifuddin-ahmed-mapup Editor
nitin-khandagale Editor
varun-andhra Editor
naveenn098 Editor
pushpak-gote Editor
sharmatanishq Editor

References

Workflow

  • Data Preparation
    • Collect data: Collect the data from credible sources like Geofabrik, National Bridge Inventory and National Hydrography Dataset.
    • Get Accurate Bridge Coordinate on OSM Way: Using methods like Buffer and join, projections and interpolations on data to get the correct bridge location on the OSM way.
  • Use JOSM to add bridges
    • Import Classes: Import necessary Java classes and types for JOSM and OSM data.
    • Define Coordinates: List bridge coordinates with OSM way IDs.
    • Retrieve Dataset: Get the OSM dataset from the JOSM layer manager.
    • Process Each Bridge
      • Retrieve the corresponding OSM way.
      • Calculate the closest point on the way.
      • Create and add a new node.
      • Update the existing way with the new node.
    • Split Way
      • Select and split the way at the new node.
    • Tag Bridge
      • Identify and tag the way as `bridge=yes`.
    • Finalize
      • Repaint map view.
      • Print success/failure messages.

Conflation

The conflation process will merge new bridge location data with existing OSM ways using the buffer and join method in QGIS along with the National Hydrography Dataset (NHD). This will involve matching bridge locations to the correct OSM ways, avoiding duplicates, and maintaining data accuracy. Geometric projection and interpolation techniques will be employed to precisely align the bridge coordinates with the OSM ways and position them accurately along the existing ways.

QA

Any issue will be addressed as soon as possible. Feel free to message Maneesh Mahlawat with any concerns.

See Also

The email to the Imports mailing list will be available once sent and a topic on the Community Forum is already posted.

For further information and updates, refer to the project page on the OSM Wiki.

Retrieved from "https://wiki.openstreetmap.org/w/index.php?title=Bridge_and_Truck_Restrictions_Import&oldid=2718461"