Skip to content

Ask Qwen Task#406

Open
annehaley wants to merge 12 commits into
masterfrom
first-hf-task
Open

Ask Qwen Task#406
annehaley wants to merge 12 commits into
masterfrom
first-hf-task

Conversation

@annehaley

Copy link
Copy Markdown
Collaborator

This PR adds a new analytics task called "Imagery: Ask Qwen". The task accepts three inputs: 1) an imagery raster, 2) a text prompt, and 3) a max_tokens value (1k - 10k). The task leverages our first Huggingface inference endpoint, sending a lower resolution version of the imagery to the endpoint along with the question and returning the response to the user.

The screenshots below show some example runs on the boston orthoimagery layer:
geodatalytics_imagery_ask_qwen_task
geodatalytics_imagery_ask_qwen_2

To support the large markdown responses, this PR makes a slight change to the Analytics Panel in the client, using vue-markdown-render for a new output type "markdown".

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 18, 2026

Copy link
Copy Markdown

Deploying geodatalytics with  Cloudflare Pages  Cloudflare Pages

Latest commit: c9ad678
Status: ✅  Deploy successful!
Preview URL: https://894360ba.geodatalytics.pages.dev
Branch Preview URL: https://first-hf-task.geodatalytics.pages.dev

View logs

Comment thread uvdat/settings/base.py Outdated
Co-authored-by: Brian Helba <brian.helba@kitware.com>
Comment thread uvdat/settings/base.py
Comment thread uvdat/core/tasks/analytics/imagery_ask_qwen.py Outdated
Comment thread uvdat/core/tasks/analytics/imagery_ask_qwen.py Outdated
Comment thread uvdat/core/tasks/analytics/imagery_ask_qwen.py Outdated
Comment thread uvdat/core/tasks/analytics/imagery_ask_qwen.py Outdated
Comment thread uvdat/core/tasks/analytics/imagery_ask_qwen.py
Comment thread uvdat/core/tasks/analytics/imagery_ask_qwen.py Outdated
Comment thread uvdat/core/tasks/analytics/imagery_ask_qwen.py
Comment thread uvdat/core/tasks/analytics/imagery_ask_qwen.py Outdated
Comment thread pyproject.toml Outdated
from .analysis_type import AnalysisInputError, AnalysisTask, AnalysisType

ENDPOINT_NAMESPACE = "Kitware"
ENDPOINT_NAME = "qwen3-5-9b-gguf-ulh"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although I previously suggested that we didn't have to keep this a secret, now that I see it hardcoded here, I'm worried that future open source users or developers will try to use our deployment-specific endpoint (I've seen this happen before).

I think we should make this a deployment-specific env var.

To avoid proliferation of multiple env vars, we could potentially pack this into a single URL.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you elaborate on what you mean by packing this information into a single URL? My first assumption is that you mean to create a JSON mapping of task names to HF endpoint names and serve it from somewhere else, but I wouldn't know where to put it.

@annehaley annehaley force-pushed the first-hf-task branch 2 times, most recently from 568bba8 to c0eb8b3 Compare June 25, 2026 17:15
Co-authored-by: Brian Helba <brian.helba@kitware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants