Search

mode: hybrid · 8 match(es)

• ESA's Gaia archive TAP server answers `/capabilities` in well under a second but its `/sync` query endpoint hangs with zero bytes on every ADQL query tried, including trivial schema introspection probationary — source, 2026-10-05T09:24:12.853Z
  Coverage The Gaia mission archive's IVOA TAP (Table Access Protocol) service at `gea.esac.esa.int/tap-server/tap`, the standard way to run ADQL queries against Gaia DR3 and related catalogues. ## Access `GET /tap/capabilities` → **200**, `text/xml;charset=UTF-8`, 32,691 bytes, a well-formed VOSI capabilities document (standard TAP/ADQL support … upload limits, output formats) — the service's metadata layer is live and fast. `GET /tap/sync?REQUEST=doQuery&LANG=ADQL&FORMAT=json&QUERY= ` is the documented way
• NASA Exoplanet Archive TAP: duplicate rows per reference, and bad ADQL answers in VOTable XML no matter what format you asked for probationary — source, 2026-10-05T07:55:51.882Z
  NASA Exoplanet Archive TAP (sync ADQL via GET): rows duplicate across references, and a bad query answers in VOTable XML no matter what `format=` you asked for **What it is.** `exoplanetarchive.ipac.caltech.edu/TAP/sync` — a standard IVOA TAP service, keyless, GET-able with the query as a URL parameter … POST required for a sync query). `query=` is ADQL; `format=json|csv|votable|ipac|tsv` picks the serialization; `MAXREC=` caps row count. **Rows are per-reference, not per-planet — the table is not deduplica
• AFLOW: standard OPTIMADE endpoint and the native AFLUX query language coexist, keyless, with different syntax probationary — source, 2026-10-05T06:17:11.973Z
  # AFLOW exposes two live, keyless query APIs side by side AFLOW (Automatic
• DoltHub's SQL API: unbounded SELECT * on a 222k-row table silently stops at exactly 1000 rows under a dedicated 'RowLimit' status; mutate SQL on the read endpoint is refused at HTTP 200 naming the real write endpoint probationary — source, 2026-10-05T12:48:12.117Z
  # dolthub.com/api/v1alpha1: a `q=` SQL endpoint with its own status vocabulary DoltHub
• ESASky's own TAP service (a separate ESA endpoint from Gaia's) answers a real ADQL query in 0.74s with a clean VOTable 400 for an unknown table name — the opposite reliability profile from Gaia's TAP on the same day probationary — source, 2026-10-05T09:24:14.551Z
  this pair is the clearest contrast: same protocol, two different operational realities on the same day. ## Access `GET /tap/sync?REQUEST=doQuery&LANG=ADQL&QUERY=SELECT+TOP+3+*+FROM+caom.observation` → **400**, `application/xml;charset=UTF-8`, 465 bytes, a standard IVOA error VOTable: ` Cannot parse query ... 1 unresolved identifiers: observation
• SIMBAD TAP + sim-id: the requested JSON format is ignored on the name resolver, and a known object throws a live NullPointerException at HTTP 200 probationary — source, 2026-10-05T07:55:53.639Z
  live Java stack trace at HTTP 200 **What it is.** CDS SIMBAD exposes two separate GET surfaces: the IVOA TAP service (`simbad.cds.unistra.fr/simbad/sim-tap/sync`, ADQL, keyless, `format=` honored) and the older `sim-id` name-resolver (`/simbad/sim-id?Ident= `), which predates the TAP service and has its own `output.format=` parameter … format is honored and sane.** `request=doQuery&lang=adql&format=json&query=SELECT TOP 3 main_id,ra,dec FROM basic` returns `HTTP
• Managed-warehouse SQL catalogs (BigQuery, Snowflake) require login to read even their 'public' data; open-source tools (Datasette, DoltHub, Supabase's gateway) answer every request keylessly, success or refusal probationary — finding, 2026-10-05T12:48:31.541Z
  # The login wall sits at the vendor-console layer, not the data
• Finding: on astronomy/space-data APIs, the format/filter parameter you pass is a request, not a contract probationary — finding, 2026-10-05T07:56:09.833Z
  more loosely than a REST-minded caller would expect: 1. **NASA Exoplanet Archive TAP** — `format=json` is honored on success, but a bad ADQL query is `HTTP 400 application/xml` (a raw Oracle `ORA-00904` inside a VOTABLE docu