Measure a House From Google Street View? The Rules

No, not the way an installer means it. Google's Maps Platform Terms of Service, last modified August 26, 2026, say a customer "will not create content based on Google Maps Content" and name tracing building outlines from the satellite base map as the first example (section 3.2.3). Street View is display only: no storing, no caching, no tracing. So GlowBid shows Street View live and measures only from photos you own. This is not legal advice.

I am an installer, not a lawyer. I built GlowBid around these rules because I did not want a measuring method that a terms update could take away in October. Read the terms at the links at the bottom, and ask a lawyer if your business depends on the answer.

What do the rules say, in one table?

Three Google documents matter, and they bind different people. The consumer terms bind you at your desk in Google Maps or Google Earth. The permissions page says what you may do with the imagery. The Maps Platform terms bind the software companies that build on Google's APIs, which is every tool that traces satellite or draws on Street View.

Can I trace a roofline on Google Maps or Google Earth?

You can measure a straight line on the map, because Google built that feature. Google Maps Help describes it: right-click a starting point, choose Measure distance, click along the path. Google Earth has a ruler. Using Google's own tool inside Google's own product for a rough number is the feature working as designed.

What the consumer terms restrict is what you do with the content: no copying it, no bulk downloading it, no building a mapping dataset from it. A rough check of an eave before a site visit is one thing. Saving the satellite image to the customer file, tracing it into a drawing you keep, or building a library of traced houses is a different thing, and the terms speak to it directly.

The bigger problem is that the number is wrong in a predictable way. Satellite is a plan view. It sees the horizontal run of a sloped edge, never the slope. Strandr's measuring guide says it plainly: satellite "reads a sloped rake as its horizontal run," and tells you to apply pitch factors to every gable. On their example house, uncorrected Google Earth read 2.9 percent short overall, with the eaves reading true.

Can I measure from Street View?

No, on the terms and on the physics.

The terms first. Google's permissions page lists what you may not do with Street View imagery: capture it as a screenshot or take it out of an embedded source for any purpose; create data from it, "such as digitizing or tracing information from the imagery"; use "applications to analyze and extract information" from it; or use it in print, "advertisements or promotional materials of any kind." Embedding a live Street View on a web page needs no permission. Everything an installer would want to do with the image beyond looking at it is on the list.

Now the physics. A Street View frame has no scale in it. Camera height, distance to the house, lens and angle vary from one panorama to the next, and the frame is stitched from several exposures. Even if the terms allowed it, a length traced on Street View is a guess with no reference you can trust, and the frame may be years old; Strandr's guide warns to confirm nothing has been added or removed before quoting from it.

What Street View is good for is recognising the house. That is what GlowBid uses it for: type the address, see the front elevation live with Google's attribution, know which photo to take. Nothing about that view is stored, cached, traced or measured, and the Street View Static API policy allows a tool to keep only the panorama ID.

What do the Maps Platform terms say to the software you use?

That the software may show Google's content and may not keep it or build from it. Section 3.2.3 of the Maps Platform Terms, Restrictions Against Misusing the Services, has three parts that matter, and "Customer" in each is the software company:

• (a) No Scraping. "Customer will not export, extract, or otherwise scrape Google Maps Content for use outside the Services. For example, Customer will not: (i) pre-fetch, index, store, reshare, or rehost Google Maps Content outside the services; (ii) bulk download Google Maps tiles, Street View images..."
• (b) No Caching. "Customer will not cache Google Maps Content except as expressly permitted under the Maps Service Specific Terms." The Service Specific Terms permit the panorama ID from the Street View Static API and, for most APIs, latitude and longitude for up to 30 days. Imagery is not on the list.
• (c) No Creating Content From Google Maps Content. "Customer will not create content based on Google Maps Content. For example, Customer will not: (i) trace or digitize roadways, building outlines, utility posts, or electrical lines from the Maps JavaScript API Satellite base map type; (ii) create 3D building models from 45° Imagery...; (v) construct an index of tree locations within a city from Street View imagery..."

I am quoting the terms, not ruling on anyone's product. LightQuoter's satellite measurement page and LightMaster's QuickMeasure page both describe click-to-trace satellite measuring; neither names its imagery provider or mentions these terms. Whether a given tool's provider and licence make it fine is a question for that vendor. Ask which imagery they use, what they store, and whether a traced roofline is content created from it.

How far off is a satellite trace, and why?

By the pitch factor on every sloped edge, plus everything a plan view cannot see. The factor is geometry: a rake is the square root of (1 plus (rise over 12) squared) times its horizontal run.

LightQuoter's page says the same from the other side: on a 10/12 gable "the real edge can be 30% longer than it appears from above," which is the 1.302 factor. The better tools ask for the pitch and multiply. That fixes the arithmetic and leaves the guess: 8/12 and 10/12 look alike from orbit and price 8 percent apart. Then there is what a plan view hides entirely: the jump from the bottom of each gable to the eave, the returns on a bump-out, the sides of a dormer, anything under a tree. LightMaster's page shows a +8 percent waste buffer on its example and Strandr recommends 10 to 15 percent; a buffer on the order is good practice with any method, but a buffer on the price to cover an unknown pitch is a guess dressed as a number.

Eaves, to be fair, read well from above. If your market is bungalows with hip roofs, a satellite trace of the gutter line is not far off. It is the gables, and the houses with four of them, where the money is.

What does GlowBid use instead?

A photo you own, a known length, and a label on every number.

Owned photo. Taken by you from across the street, or sent by the homeowner. Whole roofline in frame, square on, daylight. No Google imagery ever touches the measuring canvas.

Reference scale. Mark a known length in the photo, usually the 16 ft double garage door, and every run drawn in the same plane is scaled from it. The method is in how to measure a roofline from a photo.

Source and confidence on every run. Each measurement carries a source tag (reference-scaled or manual) and a confidence level, and they print on the quote. A run that angles away from the camera gets a foreshortening warning so you type its length from a tape or laser.

Pitch from the photo, not from orbit. A square-on photo shows the rake at close to its true length, so the peak footage comes off the drawing without a pitch guess. Where the pitch matters for the crew, read it on site with a level.

The disclaimer and the buffer. Every quote says photo-based measurements are estimates confirmed on site. An optional materials buffer, default 10 percent, goes on the order and never on the price, and it is the installer's choice.

Street View, live only. The address search shows the house through the Street View Static API with attribution, fetched when you open the estimate. We keep the panorama ID the policy allows and nothing else.

Worked example: what a plan view costs on one house

Take the two-storey from our permanent pricing guide: two front gables at 10/12, four peak runs, three jumps, priced on GlowBid's default track line at $28 per foot of peak plus 15 percent for pitch and 10 percent for the second storey, so $35 per peak foot.

The full quote on that house is $5,687, so the plan view is about 10 percent light before anyone corrects for pitch, and the missing jumps are not a pitch problem at all. With pitch correction the peaks come back, if you guessed 10/12 and not 8/12. The jumps and the channel still come from the drawing. Price this house in the free tool with a photo of your own and compare it with the number you would have traced.

Mistakes that cost money

• Saving the satellite view into the customer file. It looks harmless. It is on the list in section 3.2.3(a) for software, and the consumer terms bar copying the content. The imagery is often years old as well.
• Guessing the pitch from orbit. 8/12 and 10/12 look identical from above and price 8 percent apart on the peaks. Read the pitch from a square-on photo or a level on site, and confirm on site.
• Forgetting that a plan view has no jumps. Every gable has a jump at the bottom. From above it is a dot.
• Quoting permanent track from any remote number without the on-site line. Strandr says the same, and so do we: the price is a remote estimate that can move after the site check, and the customer should read that before they sign.

Not legal advice, and what to do with it

Everything above is quoted from Google's published terms as of September 7, 2026, with the links below, and describes how GlowBid was built. It is not legal advice. Terms change; check the "last modified" line on each document. If your quoting depends on satellite or Street View imagery, ask the vendor what they store and what licence covers it, and ask a lawyer if the answer matters to you.

If you would rather not depend on it at all, the free roofline tool measures from your own photo today, and the full product with the rate card, quote PDF, e-signature and deposit opens November 1, 2026 at the founding price.