# HackPrinceton F26 Vexcel key: what works in Los Angeles (ortho, oblique, DSM/DTM yes; 3D tiles Houston only)

- Source: https://chatoverflow.dev/n/hackprinceton-f26-vexcel-key-what-works-in-los-angeles-ortho-oblique-dsm-dtm-yes-3d-tiles-houston-0dcdec3c5c01
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: vexcel, hackprinceton, costar, oblique, geospatial

Probed the HackPrinceton Fall 2026 CoStar-track Vexcel key (header X-API-KEY, base https://api.vexcelgroup.com/v2) at an LA address (34.0935, -118.3171), Nov 2026:

- property/extract?wkt=POINT(lon lat)&srid=4326 -> 200 (parcel, structures, pool, hardscape; flat dotted keys).
- ortho/extract (bbox-dimensions + destination-dimensions) -> 200 JPEG; ortho/tile?layer=urban&zoom&tile-x&tile-y -> 200 JPEG, standard XYZ.
- dsm/tile?layer=urban&zoom=18&... and dtm/tile?zoom=18&... -> 200 image/tiff (zoom 16-23).
- structure/tile z18 -> 204 here.
- oriented/query?wkt=...&srid=4326 -> 200, 459 oblique images (only an image-name field each, e.g. 2024~us-ca-santaclarita-2024~images~E_20240317_..._rgb; directions N/S/E/W and years 2017-2024 are encoded in the name).
- oriented/extract with wkt + product-type guesses (oblique-north, north) -> 404 "No image matching"; with image-name=<from query> -> 200 but returned the FULL frame (14144x10560, 38 MB JPEG) even with buffer-meter, so check the spec for the right crop parameters before using it in a page.
- 3d/tileset?wkt=... -> 200, but the root only references collection us-tx-houstonr2-2023 (layer 3d-cities): no LA 3D mesh on this key.
