profile

Send a polyline as an array of [longitude, latitude] positions and it answers with elevations sampled at equal geodesic spacing along it, from the USGS 3D Elevation Program…

Send a polyline as an array of [longitude, latitude] positions and it answers with elevations sampled at equal geodesic spacing along it, from the USGS 3D Elevation Program seamless DEM, plus the cumulative gain and loss and the minimum and maximum. One call for a whole route rather than one call per point: 2000 samples cost what two cost. COVERAGE is the state of Alaska, whole, and nothing else yet; see GET /v1/elevation for the full statement, which this route shares and repeats under `coverage` on every response. Every sample is checked against the coverage before a tile is read, and a profile with any sample outside Alaska is refused with outside_coverage naming the sample. That check reads coordinates, so it runs after payment like the rest of the handler; the refusal does not settle and nothing is charged, but it costs a signature and a second round trip. Canada is not served even where USGS publishes pixels over it, for the licensing reason stated there. SAMPLING: samples are placed at equal geodesic distance (GRS 80) along the polyline, each on the great circle of its segment, the first at the first position and the last at the last. Omit `samples` to sample every 60 m, the native pixel height, up to 2000; pass it to choose the count. Each sample is bilinear over the four pixel centres around it by default, or `nearest` for the raster's own values; the response names the method. The source is the 2 arc-second product USGS publishes for Alaska, about 62 m north to south, so asking for spacing much under 60 m buys interpolation rather than information. VOIDS inside the line: gaps in the USGS footprint, the Canadian side of the border and water beyond the county limit are void. A sample whose window is entirely void is null in the list and counted in `stats.voidSamples`; gain and loss are summed over consecutive non-null samples so a crossing of void water is not a descent to zero and back. Inshore water is 0 in some USGS blocks rather than void, so a line acro

UNRATEDDelisted

Overview

Grade?

UNRATED

0 of 30 paid calls toward a letter

Price

$0.01 per call

Paid calls

none yet

delivery unknown until someone pays

More info

Seller?

0x76a51b5d…21968fce

URL

https://api.geoprimitives.dev/v1/elevation/profile

Seen

first 35 days ago · last 14 days ago

51 free handshakes

Payment

Pays through

— never asked

Offered on?

— never asked

Listed on?

Base

Handshakescomputed 8 days ago

0.000 from 51 free handshakes over 30 days · UNRATED ?

How the composite of 0.000 is made up, part by part
Component	Weight	Measured		Short ?	Uncertain ?
livenesscosts the most it answered at all	0.75	0.00		−0.750	0
latency p95 it answered as fast as its class	0.25	0.62		−0.095	−0.155
Composite	1.00		gap to 1.000 = 1.000 · 0.845 short · 0.155 uncertain	−0.845	−0.155

Not measured: correctness · nobody paid; honesty · nobody paid; schema conformance · no answer had a published shape to check; price stability · nothing to score

BURN_INFREE_TIER_ONLY

Verify it yourselfnpx teppi-check https://api.geoprimitives.dev/v1/elevation/profilecurl -s https://api.teppi.xyz/v1/trust/cap_01M1A59RXTM73AB45HJDRZK4Q2