A Camera Can Measure a Roof. It Cannot Find a Property Line — and Your Product Ships Both.

A picture, not a determination

A stitched, georeferenced image is a representation of what the camera saw. It becomes a determination only when someone annotates a line on it and calls the line a boundary.

Data, pending interpretation

Delivering the coordinates the sensors produced, with the processing parameters, is closer to handing over instrument output. The regulated act is interpreting it into a statement about the land.

Usually fine, until it names a property line

Measuring a structure for a materials estimate is generally treated as quantity take-off rather than surveying. The moment the report includes setbacks, lot dimensions or an overhang relative to a boundary, it has crossed.

Depends on what it is relied on for

Volume computed from a surface for internal operations is a management number. The same figure used for payment quantities on a construction contract is the kind of measurement several states treat as within the practice, and it is routinely sealed for that reason.

Inside the perimeter in more states than vendors assume

Determining and depicting the relative positions and elevations of points on the earth's surface appears verbatim in many statutory definitions. That the points came from a model rather than a total station is not an exception any of them wrote.

This is a survey

Any dimension referenced to a property line asserts where that line is. Nothing in a photogrammetric pipeline can determine a boundary, because boundaries are established from record documents, monuments and legal principles rather than from imagery.

Reserved without qualification

These are the named products of the profession. Producing one without a licensee in responsible charge is the paradigm case of unlicensed practice, whatever the automation.

A boundary opinion in a notification

Telling a user that a fence crosses a line, or that a structure violates a setback, is a professional conclusion about the location of a boundary delivered as a product feature. It is the highest-exposure output in this category and the one most likely to be built without anyone noticing what it is.

It contradicts the artefact. A document showing dimensions to a lot line is a statement about where the lot line is, and a sentence denying that the statement was made does not remove it. Boards look at what was produced and what a reasonable recipient would rely on it for.

Approximation is not the issue — the practice is defined by the act of determining and reporting positions, not by the tolerance achieved. This wording also concedes that professional verification is the appropriate standard for the output, which is an unhelpful admission on the record.

Better, because it names the provenance and the limitation of the parcel layer, which is genuinely not a survey product. It still fails if the interface invites the user to measure to that line, or if any feature computes a setback or encroachment from it.

This one holds because it is true and the product matches it. The scope statement describes data delivery, the artefact contains no professional conclusion, and the customer's licensee performs the interpretation. Scope discipline in the product is what makes the sentence work — not the sentence.

Our product only reports measurements. Is that the practice of surveying?

Sometimes, and the distinction is not measurement versus no measurement — it is measurement of what, reported to whom, for reliance on what. Most state definitions cover determining the position of points, lines, boundaries and elevations on or near the earth's surface and reporting or platting the result. Read literally that is broad enough to capture a great deal of ordinary geospatial software, and boards do not in practice pursue every distance tool. What they pursue is output that functions as a professional determination: a document a third party relies on for a decision about land, particularly where money, permitting or a property right turns on it. The practical line to hold is between the measurement of a physical object and the location of a legal one. A structure's dimensions are facts about an object. A property line is a legal conclusion drawn from record documents, monuments, evidence of occupation and rules of construction — none of which are visible to a camera, which is exactly why the profession exists.

Does the parcel layer we license make boundary features safe?

It makes them worse in one specific way. Public parcel geometry is maintained for assessment and administrative purposes, is generally accompanied by an explicit statement that it is not survey-grade and is not a boundary determination, and is routinely off by amounts that dwarf the differences people litigate over. Building a feature that measures from that geometry produces conclusions with a precision the underlying data does not support, presented in an interface that implies otherwise. Two consequences follow. First, on the licensing question, using an unreliable source does not move the output outside the practice — you have still reported where a boundary is, less accurately. Second, on the liability question, the parcel provider's own disclaimer becomes an exhibit: it establishes that the limitation was disclosed to you and that you built a reliance feature on top of it anyway. If you carry a parcel layer, carry its disclaimer through to the surface where users see the line, and do not compute distances, setbacks or encroachments from it.

Can a licensed surveyor seal output that a model generated?

Yes, and this is the workable path for products that need to produce regulated deliverables — but responsible charge is a substantive requirement, not a signature workflow. The licensee must have direct control over and detailed professional knowledge of the work, which generally means personal involvement in decisions about method, data sufficiency and the reasonableness of the result, plus enough of the underlying data to form an independent professional judgement. Rubber-stamping work performed by others is a distinct violation with its own penalties, and a queue of generated plans approved at a rate of one per minute is what that looks like in a log file. Build for the licensee rather than around them: surface the processing parameters, the control points and their residuals, the accuracy statement, the source of every referenced record document, and the specific determinations the automation made so each can be reviewed and overridden. Retain the review record per deliverable. Also confirm firm registration in the state, since in many jurisdictions the entity offering the service must be registered independently of the individual's licence.

How does this apply to a marketplace or a data-only platform?

Two exposures, and the second is the one that surprises platforms. The first is offering: many statutes make it a violation to offer or hold oneself out as able to perform surveying services without the appropriate licensure or firm registration, so a landing page promising site plans, as-builts or boundary information in a state where you hold neither is a violation completed at the marketing layer, before any work is performed. The second is the aggregation problem. If the platform receives sealed deliverables from licensed providers and then processes, merges, re-renders or derives new conclusions from them, the derived output is unsealed work that carries the visual authority of the sealed source. A dashboard that overlays three sealed surveys and computes a new distance has generated a determination no licensee made. Keep sealed artefacts intact and attributed, keep derived analytics visibly separate from them, and geo-gate the features whose deliverables are regulated in states where you lack coverage.

What happens in practice if we get this wrong?

Board action first, and it is faster and cheaper than litigation, which is why it is the common route. Complaints overwhelmingly come from licensed surveyors who encounter the product in the market, and boards can issue cease-and-desist orders, impose civil penalties, and in many states refer unlicensed practice for criminal prosecution as a misdemeanour. The commercial consequences usually arrive before the penalty does: a cease-and-desist in one state stops the feature nationally in practice, because the engineering cost of state-by-state gating after the fact exceeds the cost of turning it off. Then there is the contract layer. Unlicensed practice can render the service contract unenforceable in some jurisdictions, which means fees for work already performed may be uncollectable, and professional-liability policies commonly exclude claims arising from services the insured was not licensed to perform — so the incident that produces the claim is the same one that voids the coverage.

Where should a product team draw the line internally?

At the point where an output answers a question about a legal object rather than a physical one, and the useful part is that this is testable without a lawyer in the room. Take every field in every deliverable and ask what a recipient would do with it. Roof area feeds a materials order — physical. Stockpile volume feeds an internal production report — physical. Distance from a structure to a lot line feeds a permit application, a purchase decision or a dispute with a neighbour — legal. Elevation relative to a flood datum feeds an insurance or permitting decision — legal, and heavily regulated in its own right. Sort the fields into those two buckets and the product splits cleanly: the physical bucket ships everywhere, the legal bucket ships only where a licensee in responsible charge is in the loop and the firm is registered. The failure mode to watch for is a legal-bucket field arriving quietly inside a physical-bucket product because it was easy to compute once the data was already there.