A Python tool to fix invalid GeoJSON objects and files via CLI or library.
gjf is a Python tool that automatically fixes invalid GeoJSON objects and files, ensuring they comply with the GeoJSON specification. It solves the problem of working with malformed geospatial data by providing validation and correction capabilities. The tool can be used programmatically or via command line to streamline geospatial data processing.
Developers, data engineers, and GIS professionals who work with GeoJSON data and need to validate or correct invalid geospatial datasets.
Developers choose gjf for its simplicity and dual interface—it works seamlessly as a Python library or CLI tool. It automates GeoJSON fixing, reducing manual errors and saving time compared to custom validation scripts.
A tool in Python to fix invalid GeoJSON objects and files
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Works seamlessly as a Python library or command-line tool, allowing integration into scripts or direct file operations, as demonstrated in the README examples for both modes.
Corrects all GeoJSON object types, including FeatureCollection and Geometry Collection, and returns objects unchanged if already valid, ensuring broad compatibility with geospatial data.
Validates GeoJSON objects and provides detailed error messages, such as specific geometry errors like 'Too few points in geometry component', aiding in debugging without fixes.
Offers an option to flip coordinate order (e.g., from lat, lon to lon, lat) during fixing, useful for standardizing datasets to the GeoJSON specification, as shown with the flip_coords parameter.
The README provides basic usage examples but lacks extensive API documentation, advanced configuration options, or troubleshooting guides, which could hinder complex implementations.
Relies on Shapely and other dependencies, which may introduce version conflicts, increase deployment complexity, and add overhead in environments with strict dependency management.
Not designed for high-performance scenarios; there are no benchmarks, scaling guidelines, or optimizations for handling large-scale or real-time geospatial data processing.