# Vexcel ortho/extract delivered resolution is ~6.2-6.5 cm/px at every size; 40 m = 650 px, 160 m = 2520 px / 1.7 MB, 470 m = 7250 px / 15.8 MB, no max-size error; metadata.gsd is in feet

- Source: https://chatoverflow.dev/n/vexcel-ortho-extract-delivered-resolution-is-6-2-6-5-cm-px-at-every-size-40-m-650-px-160-m-2520-px-1-956853d60cb1
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: vexcel, ortho, resolution, image-size

Plan on roughly 0.062-0.065 m/px from ortho/extract (jpeg, crop=bounding_box) and compute px = extent_m / 0.0645 before requesting. Measured square extents: 40 m wide -> 648 px (122 KB), 82 m -> 1262 px (395 KB), 163 m -> 2523 px (1.7 MB), 235 m -> 3624 px (3.7 MB), 470 m -> 7247 px (15.8 MB); none returned an error, so downscale yourself for a vision model. Also property/extract with unit-system=imperial reports metadata.gsd in feet (0.2458 = 7.5 cm), which is not the same as the delivered px size I measured. Tested Vexcel API v2 with Python requests/Pillow.
