FAQ
Answers are open by default where they are short. Longer ones expand.
What is a "full" render versus a "small" one?
The proposal is to define the boundary in the billing unit itself:
Small render
≤ 4096 px on the longer side of the output raster — at most 16.8 megapixels.
Full render
> 4096 px on the longer side — above 16.8 megapixels, up to the 16384² / 268-megapixel ceiling.
Why that line and not another
- It is the base of the unit you are billed in. The boundary is an output megapixel count, computable from your own request before anything runs, without reference to how the service works internally. A threshold expressed in any other terms would need explaining every time. Note that it describes the picture, not the price: supersampling and transmitter count multiply what you pay without moving a render across this line.
- It is where the terrain stops being the limit. 4096 px is the terrain-matched grid for a map about 41 km wide on 1/3 arc-second data — which covers the overwhelming majority of single-site work. Below the line you are generally studying a single site and the elevation data is the constraint. Above it you are producing a regional or multi-site deliverable and the pixel count is the constraint.
- It divides the observed range sensibly. Real work runs between 512 and 8192 px per side. 4096 sits one doubling below the top of that band, so "small" is a category that real requests fall into, and "full" does not cover everything.
The cost difference
| Grid | Class | Credits (1 TX, ×1) |
× a 4096² small render |
|---|---|---|---|
| 1024 × 1024 | small | 2 | 0.06× |
| 2048 × 2048 | small | 5 | 0.25× |
| 4096 × 4096 | small (the largest one) | 17 | 1× |
| 8192 × 8192 | full | 68 | 4× |
| 16384 × 16384 | full (the largest one) | 269 | 16× |
A full render therefore costs between 4 and 16 times as much as a small one, and the step across the boundary is a single doubling of the grid. That is why the distinction is worth naming: a single doubling of the grid does not obviously appear to be a 4× increase in cost.
Credits above assume one transmitter at supersample ×1, and are rounded up to whole credits. Both multipliers apply on top of any row and neither changes which class a render is in — a 4096² raster is a small render whether it is one transmitter or eighteen.
Before you order a full render
Check that the terrain supports it. Is my request too fine? gives the one line of arithmetic. Many "full" renders are, in effect, small renders with interpolation purchased at four times the price.
The model
What propagation model is this?
Longley–Rice, the Irregular Terrain Model (ITM), run over real elevation data. Terrain diffraction is computed along each path rather than approximated, landcover attenuation and tree-canopy loss are applied, and building footprints enter as solid knife edges.
The ITM time-variability term is applied, so you can ask for a confidence level — the map for "signal 50% of the time" and the map for "signal 99% of the time" are different maps.
What terrain data does it use?
USGS 3DEP. Two tiers matter in practice: 1 m LiDAR where it has been flown, and 1/3 arc-second — about 10 m — across CONUS everywhere else. The tiers are blended across their boundary rather than switched, so a resolution change does not show up as a seam in the coverage.
Which tier you are on is the single biggest control on how fine a render is worth paying for. See Resolution & cost.
How accurate is it?
It is a prediction. Longley–Rice is a statistical model with published uncertainty, and that uncertainty is a property of the model, not of this implementation; running it faster does not make it more certain. In addition, it inherits any errors in the underlying terrain and clutter data.
We do not publish an accuracy figure for this service, because we have not measured one we would be willing to defend. If your field measurements disagree with the map, the field measurements are right.
Can I use the output for FCC coordination or a licence application?
No. This performs no coordination, produces no study anyone is obliged to accept, and makes no claim about interference to or from any licensed facility. It is a planning tool. Anything with a regulatory consequence requires a process designed for that purpose, and this service is not one.
Does it model indoor coverage?
No. It models outdoor path loss over terrain and ground cover. Buildings are obstructions in the path, not volumes with an inside. There is no building-penetration term and no floor height.
Does it support antenna radiation patterns?
Yes, from a built-in catalogue of named patterns. You pick one by name and give the antenna an orientation; you do not upload a pattern.
What is in the catalogue:
- Generic shapes — omnidirectional, cardioid (for suppressing radiation toward a protected direction), Yagi–Uda at a range of forward gains, and corner reflector.
- Named commercial LMR models, spanning low band, VHF, 220, UHF, 700, 800 and 900 MHz — exposed-dipole and folded-dipole arrays, collinear verticals, offset and directional types.
Both planes are applied. The azimuth (H-plane) pattern and the elevation (E-plane) pattern are both applied for the chosen antenna, so vertical beamwidth and null-fill affect the result rather than being ignored.
What is not supported: importing your own
.PAT or .NEC pattern files. If your
antenna is not in the catalogue, select the closest match. Sectorized panel antennas of the kind used
in cellular and microwave point-to-point work are out of scope.
Credits and cost
What is a render credit?
Credits are counted from the finished image and from two things you choose about how it is made:
credits = ceil( output megapixels × supersample² × transmitters )
All three are fields in your own request, so the cost is computable by you before anything runs, and unaffected by how the service divides the work internally. The reasoning, and why supersampling and transmitter count are in there, is on the pricing page.
What does a credit cost in money?
NOT SET. The price per credit has not been decided, and this site deliberately contains no figure that could be mistaken for one. The pricing page lists every open parameter.
Why prepaid credits instead of a monthly subscription?
Prepayment means there is no bill after the fact: a job is priced and checked against your balance before it is accepted. You also do not pay for months in which you do not render.
The cost of this arrangement to you is that we hold your payment before the processing is performed. Credits do not expire, so the balance remains available until you use it. That trade-off is set out in full on the pricing page.
Does a bigger range cost more?
Range is not a factor in the formula as it stands, so at a fixed output size a 100 km map and a 10 km map are the same number of credits. Treat that as NOT FINAL rather than a promise — whether range gains a factor is open, and it is listed with the other undecided parameters on the pricing page.
What range does change is the ground sample: the same pixels spread over ten times the distance. That is a resolution decision, and it is the one most worth considering.
Does supersampling cost more?
Yes — as the square of the setting. Supersample ×2 is four times the credits, ×3 is nine times.
The reason is that supersampling is passes: the scene is rendered that many times and the result is resolved into an output image of unchanged size. Because the image dimensions do not change, the extra work does not show up in a megapixel count, which is why the megapixel count alone is not a fair unit and why supersample² is in the formula.
When you want a smoother-looking map rather than more detail, supersampling is still the right setting to use in place of a finer grid. It is simply not free.
Why is cost measured on output pixels and not on time?
Because elapsed time is not a property of your request. The same job finishes at different speeds depending on current demand on the service, and a price that cannot be quoted in advance is not a price.
How big can a render be?
The largest we have measured is 16384 × 16384 — 268 megapixels, taking a mean of 152 seconds across 29 such renders. Typical work is between 512 and 8192 pixels per side.
A render of that size is only worthwhile if the terrain supports it. Check the terrain first.
Is there a minimum purchase?
Yes. The minimum purchase is $30.
Do larger purchases cost less per credit?
Yes. Larger purchases receive a lower rate per credit. The volume tiers are still being finalised, and are listed as open on the pricing page.
Is there free credit for new accounts?
Yes. Every new account receives $20 of free credit.
How is a part of a credit charged?
Credits are charged per render, and any part of a credit is rounded up to a whole credit. A 4096 × 4096 render at supersample ×1 is 16.8 megapixels and is charged 17 credits.
Do credits expire? Can I get a refund?
Credits do not expire. Unspent credit is not refundable at this time.
Is sales tax charged?
Yes. Texas sales tax applies to this service, and the amount is shown at purchase, before you pay.
What happens if I run out of credit part-way through a render?
The intended behaviour is that this cannot happen: a job is priced and checked before it is accepted, and either runs to completion or is declined up front with the shortfall shown. Renders are not stopped part-way to enforce a balance, because a partly finished render would be work you were charged for that never produced an image.
A render that fails for any other reason is not charged, and can be run again.
Output
What do I actually get back?
- A georeferenced map overlay for a web basemap.
- A tile pyramid, so the result can be panned and zoomed without re-rendering.
- KMZ, for Google Earth and any other application that reads it.
Can I combine several transmitters?
Yes, in two ways, which answer different questions. Best server takes the strongest signal at each pixel, which is the right method for a trunked or roaming system where a radio selects one site. Sum of power adds the signal from all sites, which is the right method for simulcast, or for determining the total RF energy reaching a location.
Choosing the wrong method produces a plausible map that answers a different question.
Is the coverage a contour or a field?
A field. You get predicted signal strength across the area and choose your own threshold afterwards, rather than accepting a predetermined definition of where "coverage" ends. A contour is a decision; this gives you the data the decision is made from.