astropy / astropy/pyvo

ENH: siav2 implementation doesn't allow "contain coordinate" queries

Open
#692 4 comments 0 reactions 0 assignees View on GitHub
component: dal enhancement
Dominant language
Python
Stars
88
Forks
64
Avg merge
38m
Merged PRs (30d)
1

Description

The first use case in the SIAv2 document is a simple contain or not question

> find data that includes specified coordinates (e.g. for some object)

Yet, with POS it's not possible to query for this, one always have to pass on a search radius or define a range/polygon.

Would you think there could be/should be a way to work around this? E.g. in pyvo could default to very small radius when only a skycoord is passed along for a coordinate?

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue does not name files or tests. Start by tracing pyvo's SIAv2 POS handling and the query path used when a SkyCoord is passed without a radius, then compare it with the SIAv2 containment use case. Done requires an agreed query behavior and corresponding coverage for coordinate-only containment queries.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.