[PR #809] [MERGED] [NEW PLUGIN] add geo_encoder_decoder opencage based #ieeesoc #1191

New Issue

2026-02-22T17:50:53-05:00

yindo commented

2026-02-22 17:50:53 -05:00

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/809
Author: @Ayush3941
Created: 6/28/2025
Status: ✅ Merged
Merged: 7/3/2025
Merged by: @crazywoola

Base: main ← Head: adds-geo_encoder_decoder

📝 Commits (1)

371363e add geo_encoder_decoder opencage based plugin version 0.0.1

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ geo_encoder_decoder/geo_encoder_decoder.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

Plugin Author: Ayush3941
Plugin Name: geo_encoder_decoder
Repository URL: https://github.com/Ayush3941/geo_encoder_decoder

2. Submission Type

New plugin submission
Version update for existing plugin

3. Description

The geo_encoder_decoder plugin leverages the [OpenCage Geocoding API](https://opencagedata.com/) to provide two primary tools inside Dify:

encode_coordinates: Converts a human-readable address into geographic coordinates (latitude and longitude).
decode_coordinates: Performs reverse geocoding to convert coordinates into a readable place name.

This plugin enables accurate location intelligence, mapping, and reverse-lookup workflows within Dify-powered chatflows, all without needing server-side infrastructure.

4. Checklist

I have read and followed the Publish to Dify Marketplace guidelines
I have read and comply with the Plugin Developer Agreement
I confirm my plugin works properly on both Dify Community Edition and Cloud Version
I confirm my plugin has been thoroughly tested for completeness and functionality
My plugin brings new value to Dify

5. Documentation Checklist

Step-by-step setup instructions
Detailed usage instructions
All required APIs and credentials are clearly listed
Connection requirements and configuration details
Link to the repository for the plugin source code

6. Privacy Protection Information

Data Collection

No user personal data is collected by this plugin. The tools process user-provided input (coordinates or location name) on demand and return geocoded results. All request/response data is handled in-memory and not stored.

Privacy Policy

I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/809 **Author:** [@Ayush3941](https://github.com/Ayush3941) **Created:** 6/28/2025 **Status:** ✅ Merged **Merged:** 7/3/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `adds-geo_encoder_decoder` --- ### 📝 Commits (1) - [`371363e`](https://github.com/langgenius/dify-plugins/commit/371363eb533ec93bd3a22637e9c94fa4f91c3241) add geo_encoder_decoder opencage based plugin version 0.0.1 ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `geo_encoder_decoder/geo_encoder_decoder.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata * **Plugin Author**: Ayush3941 * **Plugin Name**: geo\_encoder\_decoder * **Repository URL**: [https://github.com/Ayush3941/geo\_encoder\_decoder](https://github.com/Ayush3941/geo_encoder_decoder) --- ## 2. Submission Type * [x] New plugin submission * [ ] Version update for existing plugin --- ## 3. Description The `geo_encoder_decoder` plugin leverages the [[OpenCage Geocoding API](https://opencagedata.com/)](https://opencagedata.com/) to provide two primary tools inside Dify: * `encode_coordinates`: Converts a human-readable address into geographic coordinates (latitude and longitude). * `decode_coordinates`: Performs reverse geocoding to convert coordinates into a readable place name. This plugin enables accurate location intelligence, mapping, and reverse-lookup workflows within Dify-powered chatflows, all without needing server-side infrastructure. --- ## 4. Checklist * [x] I have read and followed the Publish to Dify Marketplace guidelines * [x] I have read and comply with the Plugin Developer Agreement * [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version * [x] I confirm my plugin has been thoroughly tested for completeness and functionality * [x] My plugin brings new value to Dify --- ## 5. Documentation Checklist * [x] Step-by-step setup instructions * [x] Detailed usage instructions * [x] All required APIs and credentials are clearly listed * [x] Connection requirements and configuration details * [x] Link to the repository for the plugin source code --- ## 6. Privacy Protection Information ### Data Collection * No user personal data is collected by this plugin. The tools process user-provided input (coordinates or location name) on demand and return geocoded results. All request/response data is handled in-memory and not stored. ### Privacy Policy * [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

yindo added the pull-request label 2026-02-22 17:50:53 -05:00

yindo closed this issue

2026-02-22 17:50:59 -05:00

yindo referenced this issue

2026-02-22 17:58:09 -05:00

[PR #1191] [MERGED] add nano_banana #1446

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1191