A curb can be correct in a database and wrong on the street. The paint can match an old rule while a newer notice is already effective. A loading zone can be visibly clear in one frame and oversubscribed ten minutes later. Those are not three versions of the same fact. They are three different truths with different owners, clocks, and standards of evidence.
That distinction matters in San Francisco because the curb is becoming both physical infrastructure and machine-readable instruction. The U.S. Department of Transportation describes the City’s Digital Curb Program as an effort to create a citywide, location-specific, current inventory of curb regulations and disseminate it through an open data feed. The linked project report is still shown as pending, so the program should not be described as a completed citywide result. Its stated goal nevertheless reveals the maintenance problem: a digital rule remains useful only when changes are captured, published, and reconciled with the place people and vehicles encounter.
Limited aerial and ground imagery can help that work, but only in a carefully bounded role. It can preserve a dated relationship among a curb segment, travel lane, loading approach, intersection, transit zone, bike facility, or accessible route. It can show that paint or a sign was visible, obscured, absent from a planned view, or different from an owner-supplied record. It cannot decide which rule legally controls, infer typical demand from a still, certify accessibility, declare safety or compliance, or silently edit the official dataset.
The useful product is therefore not a beautiful overhead map. It is a curb reconciliation ticket: a small source package and routing record that identifies the official segment and change trigger, pairs aerial context with necessary ground companions, classifies any mismatch, assigns the question to the correct owner, and records how it was closed. This guide is for a San Francisco transportation, curb-management, data, or public-works lead deciding whether that visual layer belongs in a particular update. It does not claim that San Francisco Drone Footage has performed work for the City, SFMTA, USDOT, an autonomous-vehicle operator, or the location in the featured image.
Featured image: “Aerial photo of San Francisco’s Mission Bay, ballpark, and Caltrain area” by Firstcultural, dedicated under CC0 1.0; cropped and converted to WebP. The February 2024 high aerial photograph is licensed geographic context—not verified drone capture, a current curb record, City assignment, client project, official dataset, condition finding, or endorsement.
Start with three truths, not one source
Regulation truth belongs to the official record
The regulation layer answers what rule applies to an identified segment and when. Its authority comes from the City’s governing process and record—not from pixels, a map label, a photographer’s caption, or a model’s object classification. Before commissioning imagery, the public owner should supply the durable segment identifier, geometry or reference limits, current record version, stated effective date, source system, and contact authorized to resolve ambiguity.
San Francisco’s own Digital Curb material explains why that step cannot be skipped. The SFMTA project profile published by USDOT describes curb regulations residing in separate datasets and frames the project around a citywide inventory, maintenance, and open feed. SFMTA board material similarly describes a sequence of surveying, integrating, publishing, and maintaining the information. Those are data-governance activities. A camera can contribute dated source material to one part of the sequence; it does not inherit authority over the rest.
Freeze the owner-supplied record used for comparison. Store its version or retrieval date with the ticket rather than pasting an untraceable screenshot into a slide. If a public notice, legislation, work order, or approved change package initiates the assignment, link that trigger as a separate source. Do not rewrite its effective date from the day a crew happens to arrive. If the segment limits are unclear, resolve them before capture or mark the ticket unable to compare.
This separation also protects future automation. A computer-vision routine may flag a likely sign, color band, or curb opening. It may help a reviewer find frames faster. It should not promote a detected object into the legal rule, because the official record may include hours, exceptions, vehicle classes, dates, or adjacent geometry that no single image expresses.
Marked truth belongs to dated street imagery
The marked layer records what the physical street displayed at a stated time: paint, signs, curb shape, poles, meters, markings, cones, construction controls, access features, and visible obstructions. Use factual language such as “a blue sign face is visible on the north-side pole” or “the intended curb edge is obscured by a stopped vehicle.” Avoid language such as “the lawful loading zone begins here” unless an authorized source establishes that conclusion.
An elevated oblique may show how a curb relates to the block, intersection, driveway, transit platform, bike lane, or delivery approach. A top-down view may help locate segment limits where surface markings remain legible. Neither replaces close ground photographs of sign text, arrows, curb paint boundaries, meters, curb ramps, or accessibility details. Where controlled geometry or quantified mapping is required, define control, accuracy, method, review, and qualified responsibility separately through an address-specific mapping and photogrammetry discussion. Ordinary images are not survey products merely because software can place them on a map.
A visible curb color is not a legal designation
Paint may be incomplete, faded, covered, temporarily altered, newly installed, awaiting a sign, or left from an earlier rule. Light, shadow, wetness, compression, vegetation, vehicles, and perspective can change how it appears. Record the visible color and confidence of visibility, not the legal meaning. The reconciliation ticket should direct a disagreement to the record owner and the physical-marker owner rather than asking a photographer or model to choose which side is correct.
Commission only on a change trigger
Tie capture to legislation, installation, or discrepancy
A citywide image refresh sounds comprehensive but can produce an expensive archive with no defined comparison clock. Commission imagery when a specific event creates a decision: a rule becomes effective; paint or signs are installed; construction restores a curb; a transit or loading treatment changes; a data steward receives a credible discrepancy report; or an audit sample requires source evidence. Name that event, the decision it enables, and the date by which evidence remains useful.
SFMTA’s current curb-management project page describes the curb as contested space serving access, goods movement, transit, shared mobility, bike infrastructure, parklets, and other uses. The agency’s public notices also provide a current stream of proposed and approved transportation changes. These sources show why the curb changes; they do not establish that every change warrants aerial capture. A ground-only record may be enough for a single sign replacement. Existing City imagery may already answer a geometry question. A staff field walk may be more proportionate when the only decision depends on readable sign text.
Use a three-part trigger test:
- What official or operational event created the need?
- What relationship is not recoverable from existing approved records or ground photographs?
- Who will act differently if the visual source confirms, contradicts, or cannot show that relationship?
If any answer is missing, hold the commission. “We may need it later” is not yet a source specification. If the relationship involves recurring change, adapt the repeat-view discipline used in San Francisco progress documentation without treating the street as a construction site or borrowing a construction conclusion.
Select segment boundaries by decision, not whole block
The capture unit should match the rule unit and the decision. Define a start and end reference, side of street, direction, adjacent travel context, and any junction that changes interpretation. A whole block may contain several regulations, hours, curb colors, driveway interruptions, bus zones, corners, and treatment transitions. One panoramic frame can make them look continuous when the official data does not.
Create a segment brief with a plain-language question. For example: “After owner-confirmed effective date X, can a reviewer locate segment C-104 relative to the crosswalk and loading approach, see whether the planned paint boundary is visible, retrieve the sign companions, and route any disagreement without interpreting the rule from imagery?” The question defines what to include and what to ignore.
Then assign purposeful views. An orientation frame establishes the block face. A relationship frame connects the segment to the decision-relevant approach or intersection. Ground companions preserve sign text and paint endpoints. An exclusion list prevents collection of irrelevant windows, faces, plates, private yards, security features, or neighboring activity. Store a reference thumbnail only when a later comparison is expected and the public owner has approved retention.
A capture window is not an effective date
Record both clocks. The effective date comes from the authorized record supplied by the owner; the capture timestamp comes from the source file and visit manifest. Installation may lag a rule, temporary controls may intervene, and a photograph may precede or follow an administrative update. Never let file chronology manufacture legal chronology. If the two clocks cannot be reconciled, that is a ticket condition, not a captioning problem.
Pair air and ground for a readable curb record
Use aerial and oblique views for relationships
An aerial view earns its place when it shows a relationship that ground sources cannot communicate efficiently. Useful examples include the sequence from intersection to loading approach, the position of a curb segment beside a transit island or bike lane, a pickup path around a median, or the continuity break created by a driveway. The camera direction, frame limits, intended question, and prohibited inference should be named before launch.
Prefer the lowest-data frame that answers the question. A tighter oblique may reveal the necessary geometry while collecting less irrelevant private activity than a broad nadir mosaic. A high overview may orient a corridor but make paint or accessibility features too small to interpret. A low angle may reveal the curb but collect faces, plates, windows, or storefront detail that the ticket does not need. “More coverage” is not automatically better evidence.
Capture feasibility is location- and time-specific. San Francisco includes controlled airspace, dense pedestrian activity, moving traffic, property-control questions, tall structures, transit interfaces, and changing temporary conditions. The remote pilot must assess the actual address, airspace, operation over people and vehicles, visual line of sight, launch/landing authority, and safe alternatives. The San Francisco permits and airspace checklist helps the public owner assemble those questions, but it is not an approval and cannot promise that a requested view is lawful or safe.
Use the aerial asset as an index into the package, not the whole package. Give each relationship frame a view ID and link it to the relevant segment version and ground companions. If safe capture cannot answer the question, record the view as unavailable and route the decision to existing maps, ground evidence, a different date, or another qualified method. Do not force a flight to complete a visual pattern.
Ground companions preserve readable detail
For each elevated view, specify ground sources by evidence purpose: sign face and arrow; paint start and end; meter or pole reference; curb ramp and crossing context; loading entrance; temporary notice; or an occlusion that explains why a planned feature cannot be seen. Use consistent direction labels and a small index so a future reviewer can move from overhead relationship to readable detail without guessing.
Ground photographs need the same claim discipline as aerial ones. A visible sign records its appearance at capture; it does not establish that the sign is current, correctly installed, or legally controlling. An unoccupied curb does not prove unused capacity. A stopped delivery vehicle does not prove authorization or violation. An apparent conflict with a map is a discrepancy to route, not a verdict.
The package can borrow proven file-governance principles from repeatable San Francisco documentation services: stable identifiers, dated manifests, separated masters and derivatives, and written exceptions. Its purpose, however, remains curb reconciliation. Do not add construction milestones, promotional selects, 3D models, or time-lapse deliverables unless a separate buyer decision requires them.
One angle should not carry all three truths
An elevated frame cannot make small sign text reliable. A close ground frame cannot explain a complex approach. Neither image states the authoritative regulation or represents typical use. Accept the package only when every assigned source has one declared job. If a source is being asked to prove both physical presence and legal meaning—or both one-time occupancy and recurring demand—split the question and route the unsupported conclusion elsewhere.
Send mismatches through a reconciliation ticket
Record versions and classify the discrepancy
Open one ticket per decision-relevant segment, not one per photograph. Begin with the official segment ID and version, owner-supplied change trigger and effective date, capture window, view IDs, ground companions, and any occlusion. Then classify what needs resolution. A compact taxonomy keeps the route intelligible:
| Mismatch class | What the source set indicates | Primary route |
|---|---|---|
| Record-to-marker | Owner-supplied rule and visible paint/sign context do not appear aligned | Record owner plus marker owner |
| Geometry | Segment limit or relationship is ambiguous across record and imagery | Record owner; mapping or survey authority if needed |
| Timing | Effective, installation, publication, and capture dates do not align | Change owner and record owner |
| Occlusion | Required physical evidence was blocked, too small, or unavailable | Ticket owner for recovery or alternate source |
| Observation | A bounded observation raises an operational question not answered by the rule | Observation owner for a defined study, not automatic record change |
| No comparison | Missing version, source, or segment definition prevents a valid comparison | Ticket owner; hold inference |
The classification describes the information problem, not fault. Preserve the original files and source metadata; do not overwrite a frame after someone updates paint or data. If a correction is made, link the new authoritative record and, when proportionate, a recovery image. The history should show what was compared, what changed, and who approved closure.
Observed use deserves special restraint. A still can record that specified objects were visible during a defined moment. A short video can record movement during its actual duration. Neither establishes typical utilization, dwell behavior, peak demand, accessibility, safety performance, or compliance without an appropriate sampling plan, definitions, privacy review, and qualified interpretation. If the operational question matters, commission the right study rather than stretching an attractive image.
Assign record, marker, and observation owners
The three truths need separate owners even when one department holds several roles. The record owner resolves the official rule, version, geometry, and publication path. The marker owner resolves physical paint, signs, poles, curb treatment, or installation status. The observation owner defines any time-bounded operational study and controls what may be inferred from it. A ticket owner coordinates the handoff and closure without taking authority from the other roles.
Write those names or functions into the brief before capture. Otherwise, a mismatch can circulate among photographer, data vendor, project manager, and field crew with no one authorized to decide. The photographer should be able to say what was captured, when, how it was processed, and what was obscured. The photographer should not be asked to select the lawful curb rule, diagnose installation quality, or certify the representative use of a segment.
The closure line should record the disposition: record corrected; marker work ordered or completed; source accepted as consistent; geometry clarified by an authorized record; recovery capture accepted; operational study opened; or no action with reason. Include approver and date. If the mismatch remains unresolved, keep it open or explicitly close it as unresolved under the owner’s procedure—do not erase it from a presentation.
Never let AI close a ticket from pixels
Computer vision can prioritize review, detect likely changes, or match source files to segments. It can be wrong because of glare, shadows, vehicles, temporary controls, construction, stale training data, or unfamiliar markings. Require a human authorized by the responsible owner to review the official source and evidence limits. Automation may propose a discrepancy class; it should not declare the governing rule, modify the production record, or certify closure on its own.
Plan a lawful, low-data public-street capture
Separate aviation, property, traffic, and people
Four questions must remain distinct. Federal aviation rules govern the aircraft operation. Property or site control governs where the crew may stand, launch, land, or place equipment. Traffic and pedestrian control require their own lawful coordination. Privacy, surveillance, records, labor, and distribution rules govern what the public owner may collect, retain, analyze, and share. Permission in one lane does not answer the others.
For aviation, use current FAA sources for the actual plan. The FAA’s operations-over-people guidance explains that Part 107 operations over people, moving vehicles, and open-air assemblies depend on the applicable category and conditions. The FAA’s airspace authorization page explains authorization paths in controlled airspace. Those pages do not make a dense San Francisco curb operation feasible. The remote pilot retains responsibility to accept, modify, postpone, or decline the operation.
Build alternatives into the request: ground-only capture, a different safe operating point, a shorter segment, a quieter authorized window, existing public imagery, or no new source. The buyer should specify the decision and evidence limit, not prescribe a flight path that transfers public-space risk to the operator. Scope and cost can be evaluated only after those constraints are known; the San Francisco pricing guide explains why access, approvals, capture design, processing, and revision are separate cost drivers.
Minimize privacy and public-record burden
Before collecting, ask what the agency is authorized to acquire, what policy applies, what must be disclosed, who may access it, how long it should remain, and how a public-records request would be handled. San Francisco’s Surveillance Technology Ordinance describes the City’s Chapter 19B policy environment and links the inventory, impact reports, policies, and annual reports. Whether a proposed system or use falls within those provisions is a determination for the responsible City officials and counsel—not a conclusion this article or an imagery vendor can make.
Use data minimization as capture design. Frame the decision segment rather than an entire neighborhood. Avoid unnecessary dwell on people, plates, windows, yards, workspaces, and security details. Do not collect audio unless specifically lawful and necessary. Decide whether originals, derived images, annotations, or detection outputs have different retention needs. Restrict public-facing derivatives separately from internal source evidence, and attach permitted-use and distribution classes to the manifest rather than relying on an email.
If the project proposes automated detection, document the model’s purpose, inputs, outputs, confidence behavior, review owner, false-positive route, prohibited uses, and deletion path. A low-resolution derivative may be enough for orientation while a controlled master remains available only to authorized reviewers. Public transparency and records staff should see the workflow before collection, not after a vendor has created an indefinite archive.
Collect less instead of blurring everything later
Blurring can be useful for a derivative, but it does not undo the collection, retention, or exposure of the master. Cropping after capture may also remove context and make the record misleading. Prefer a camera position, lens, altitude, direction, and time window that avoid irrelevant detail at the source. When the necessary relationship cannot be captured proportionately, use a ground companion, official map, or no image.
Accept by retrieval and closure
Test the package against a recent curb change
Acceptance should begin with a blind retrieval test. Give a reviewer who did not attend the visit the official segment reference and the change question. Ask that person to locate the regulation source and version, identify the capture date and window, find the orientation and relationship views, retrieve the ground companions, see every occlusion and non-use, identify any mismatch class, and name the owner responsible for the next decision.
If the reviewer must search email, infer filenames, treat the featured frame as the official rule, or ask what a red outline means, the package is not ready. If the reviewer can find the files but no one owns the discrepancy, the media delivery is complete while the reconciliation product is not. The test measures whether the record carries a decision across time and personnel—not whether the photography looks impressive.
Run a second test on closure. Choose one resolved ticket and verify that its original comparison remains intact, the correcting or clarifying source is linked, the disposition is specific, and the approver and date are present. Make sure a public derivative cannot expose restricted masters or unsupported annotations. Expire temporary access and derived data according to the approved rule. A gallery that remains online forever is not a retention policy.
This approach also makes future systems more reliable. California DMV announced new autonomous-vehicle regulations in 2026, while the CPUC continues to regulate autonomous-vehicle passenger service programs. Those programs do not make imagery an operating instruction. They do increase the value of disciplined source lineage: future road users and services need machine-readable rules whose changes can be traced to authorized processes, while public owners need tools for finding disagreements without granting pixels legal authority.
Deliver masters, derivatives, accessibility, and expiration
The final manifest should identify ticket ID, segment and record version, change trigger, owner-supplied effective date, capture date and window, source IDs, file checksums, camera directions, processing steps, ground companions, occlusions, permitted uses, distribution class, retention or review date, mismatch status, owners, and closure link. Separate archival masters, working sources, reviewer derivatives, and public-approved media. State whether geolocation metadata is retained, generalized, or removed.
Supply a small index that works without proprietary software. Descriptive filenames and a CSV or accessible table can connect each view to its purpose. Add concise alt text that describes visible relationships without making a finding. Caption statements should distinguish owner-supplied regulation facts, photographer-observed visible facts, and interpretations supplied by authorized reviewers. Aerial material should not be labeled “drone” unless the capture source is verified as such.
The commissioning brief should arrive with the segment IDs, official change trigger, intended decision, record/marker/observation owners, ground companions, requested window, address or limits, privacy and retention rules, distribution classes, accessibility needs, and prohibited inferences. The provider can then assess whether any aerial component is lawful, safe, proportionate, and useful; propose ground or existing-source alternatives; and scope a ticket-ready package rather than a generic photo count.
Success is a closed loop, not a prettier map
The curb record succeeds when a future reviewer can tell what the official source said, what the street visibly displayed, what a bounded observation did and did not show, where the sources disagreed, who owned the question, and how it was resolved. If that is the decision your San Francisco program needs to support, send the segment limits, trigger, record owners, intended users, capture constraints, and retention rules through the project request form for an address-specific feasibility and deliverable review. The response should begin with whether new imagery belongs in the workflow at all.
