docs: add Available Plugins section with providers and outputs#1211
docs: add Available Plugins section with providers and outputs#1211ajturner wants to merge 1 commit into
Conversation
Adds a comprehensive Available Plugins section to README.md listing all known Koop providers and outputs (officially supported, experimental, and third-party) with links to their repositories and npm packages, mirroring the content maintained at koopjs.github.io/docs/available-plugins. https://claude.ai/code/session_014cdJL2uJmQB9qfPbKQKrow
|
There was a problem hiding this comment.
Pull request overview
Adds an “Available Plugins” section to the root README to make provider/output plugin discovery easier directly from the repo, aligning the README with the website’s maintained plugin list.
Changes:
- Updates the introductory plugin-architecture paragraph/linking language.
- Adds a new “Available Plugins” section with categorized tables for Providers and Outputs (official/experimental/third-party), including GitHub + npm links.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Koop is a JavaScript toolkit for making requests to spatial APIs. It exposes a Node.js web server that faciliates on-the-fly transformations of geospatial data from one format to another and delivers it to clients by HTTP. Koop allows you to keep your data in its native format, while making it accessible in any format required. Out-of-the-box, Koop can translates your data into the GeoServices specification supported by ArcGIS products. It's plugin architecture supports output in other formats including vector-tile, WMS, and plain old GeoJSON. Learn more at [https://koopjs.github.io](https://koopjs.github.io). | ||
|
|
||
| Koop's plugin-architecture facilates custom deployments specific to your needs. "Provider" plugins to connect to novel data formats and translate to a common format (GeoJSON), while "output" plugins then transform that GeoJSON to other specifications. See a list of plugins already authored and maintained [here](https://koopjs.github.io/docs/available-plugins). If you have a novel datasource or require an as-yet unsupported output format, new plugins can be easily developed and integrated. See the [development section of the Koop docs](https://koopjs.github.io/docs/development). | ||
| Koop's plugin-architecture facilates custom deployments specific to your needs. "Provider" plugins to connect to novel data formats and translate to a common format (GeoJSON), while "output" plugins then transform that GeoJSON to other specifications. See a full list of plugins [here](https://koopjs.github.io/docs/available-plugins). If you have a novel datasource or require an as-yet unsupported output format, new plugins can be easily developed and integrated. See the [development section of the Koop docs](https://koopjs.github.io/docs/development). |
There was a problem hiding this comment.
Spelling: "facilates" should be "facilitates" (and consider using the same spelling consistently wherever this paragraph appears).
| | [GitHub](https://github.com/koopjs/koop-provider-github) | [](https://www.npmjs.com/package/koop-github) | | ||
| | [Google Analytics](https://github.com/koopjs/koop-provider-google-analytics) | [](https://www.npmjs.com/package/@koopjs/provider-google-analytics) | | ||
| | [Google Sheets](https://github.com/koopjs/koop-provider-google-sheets) | [](https://www.npmjs.com/package/@koopjs/provider-google-sheets) | | ||
| | [Marklogic](https://github.com/koopjs/koop-provider-marklogic) | [](https://www.npmjs.com/package/@koopjs/provider-marklogic) | |
There was a problem hiding this comment.
The provider name appears to be mis-capitalized as "Marklogic"; the product/repo name is typically "MarkLogic". Updating the display text will improve readability and consistency.
| | [Google Analytics](https://github.com/koopjs/koop-provider-google-analytics) | [](https://www.npmjs.com/package/@koopjs/provider-google-analytics) | | ||
| | [Google Sheets](https://github.com/koopjs/koop-provider-google-sheets) | [](https://www.npmjs.com/package/@koopjs/provider-google-sheets) | | ||
| | [Marklogic](https://github.com/koopjs/koop-provider-marklogic) | [](https://www.npmjs.com/package/@koopjs/provider-marklogic) | | ||
| | [Socrata](https://github.com/koopjs/koop-provider-socrata) | [](https://www.npmjs.com/package/koop-socrata) | |
There was a problem hiding this comment.
The Socrata npm badge and npm link reference different package names (badge uses "@koopjs/provider-socrata" while the link goes to "koop-socrata"). Please align these so the badge and link point to the same npm package.
|
|
||
| ### Outputs | ||
|
|
||
| Koop uses **outputs** to transform GeoJSON from providers into open specification formats. |
There was a problem hiding this comment.
This sentence says outputs transform GeoJSON into "open specification formats", but the list includes GeoServices which is not an open specification. Consider rewording to something like "other formats/specifications" so the description matches the entries below.
| Koop uses **outputs** to transform GeoJSON from providers into open specification formats. | |
| Koop uses **outputs** to transform GeoJSON from providers into other formats and specifications. |
Adds a comprehensive Available Plugins section to README.md listing
all known Koop providers and outputs (officially supported, experimental,
and third-party) with links to their repositories and npm packages,
mirroring the content maintained at koopjs.github.io/docs/available-plugins.