A stable and fast converter that transforms OpenStreetMap (OSM) data into GeoJSON format with proper polygon detection.
osmtogeojson is a Node.js library and command-line tool that converts OpenStreetMap (OSM) data into GeoJSON format. It solves the problem of transforming OSM's XML or JSON data into a standardized, widely-used geospatial data structure, enabling integration with mapping libraries and GIS applications. The tool handles complex OSM features like polygons and multipolygons with high accuracy.
Developers and geospatial analysts working with OpenStreetMap data who need to convert it to GeoJSON for web mapping, data analysis, or integration into geographic information systems (GIS).
Developers choose osmtogeojson for its stability, accurate polygon detection, and full support for OSM's multipolygon and Overpass API geometries. It is well-tested, fast, and maintained by the overpass turbo project, ensuring reliability and compatibility with OSM standards.
convert osm to geojson
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements real OSM polygon detection based on OpenStreetMap's specification, ensuring correct geometry handling for polygons and multipolygons as highlighted in the README.
Optimized for speed and capable of processing large datasets efficiently, though the README notes memory considerations for files over 100MB.
Extensive test suite ensures robustness, and it's maintained by the overpass turbo project, proven in real-world usage as stated in the features.
Supports all extended Overpass API geometry modes, making it comprehensive for handling various OSM data queries as per the README.
The README explicitly warns that processing files over 100MB requires significant memory (4-5 times input size), which can be a limitation in resource-constrained environments.
Primarily a command-line tool and library, lacking a built-in graphical interface, which may not suit users unfamiliar with terminal commands or seeking point-and-click solutions.
Options like uninterestingTags and polygonFeatures require callback functions or JSON objects, adding complexity for custom use cases beyond basic conversion.