A lightweight JavaScript library for parsing Well-Known Text (WKT) into GeoJSON and stringifying GeoJSON back to WKT.
wellknown is a JavaScript library that parses Well-Known Text (WKT) into GeoJSON and stringifies GeoJSON back to WKT. It solves the problem of converting between these two common geospatial data formats, enabling interoperability in mapping and GIS applications. The library supports various geometry types and works in both Node.js and browser environments.
Developers building geospatial applications, mapping tools, or GIS software that need to handle WKT and GeoJSON data interchange, particularly those using JavaScript stacks like Leaflet, Mapbox, or OpenLayers.
Developers choose wellknown for its lightweight, focused implementation, comprehensive geometry support, and ease of integration across environments, offering a reliable alternative to heavier or less-maintained WKT parsers.
GeoJSON-emitting WKT parser for browsers and node
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Handles all common geometry types including 2D, 3D, and 4D versions of Point, LineString, Polygon, and their multi-variants, as listed in the README's feature set.
Works seamlessly in Node.js, browsers via Browserify, and as a standalone script, with CLI tools for command-line usage, making it versatile for different development setups.
Designed as a minimal utility with no external dependencies, ensuring easy integration and low overhead in projects, as emphasized in the philosophy section.
Offers simple parse and stringify functions with clear documentation, reducing learning curve and facilitating quick adoption for basic conversion tasks.
Returns null on parse failure or throws errors for unsupported inputs like FeatureCollections, which may not be sufficient for production applications with unpredictable data quality.
Relies on older systems like Travis CI and Bower, and the README's rant suggests limited updates or engagement with modern OGC standards, potentially indicating slower maintenance.
Lacks support for SRID and other WKT extensions mentioned in the OGC standard, limiting its usefulness for professional GIS workflows that require precise spatial references.