Tool / Free · v0.5

Photo tools.

Put site photographs on a map, and against the site’s 3D model, with every location reviewed by you.

Runs in your browser · Photographs are not uploaded · Locations are never guessed

Photo tools Pilot v0.1, before the CAD and Blender downloads, at 1024 pixels, opened without a site: the Photo Map to Google Earth page with its three steps, choose photographs, review locations and captions, and download the photo map. No photographs are loaded.
The Pilot v0.1 page as it opened without a site on November 12, 2026, before the CAD and Blender downloads were added.

Know where each site photograph was taken

A site visit produces a folder of photographs. Weeks later, the question is where each one was taken and which way it faced. The answer is in the files’ GPS records, where they have one, and in someone’s memory where they do not.

The photo tools read what the files record, show it for review, and let you correct or add a location by hand. Nothing is placed by guessing. The result is a photo map anyone can open in Google Earth and, with a site from Site Lens, a set of photographs tied to that site’s 3D model.

They are for landscape architects, architects, planners and designers who document existing conditions.

How it works

On its own: a photo map

  1. Choose photographs. Add single files or a ZIP, or drop them on the page.
  2. Review. Check each location, type one for a photograph that has none, add captions, and untick any photograph to leave it out. Choose Show on aerial to see the ticked photographs as numbered pins on an aerial photograph, with the direction each one faced.
  3. Download. Confirm that you may share the photographs and their locations. Download the Google Earth KMZ; choose your State Plane zone (outside the United States the UTM zone of the photographs is chosen for you) and download the CAD files or the Blender cameras; or download the key view package for Illustrator, InDesign and print.

No site and no Site Lens project are needed.

With a site from Site Lens

  1. Send the site. In Site Lens, open Export and choose Send this site to Photo tools. The site’s coordinate frame, its 3D model and a copy of the photographs kept in the project open here in a new tab.
  2. Add and place photographs. Each located photograph appears as a pin on the model.
  3. Match a photograph to the model. Use Photo Match to line the photograph up by eye and save the camera as reviewed.
  4. Download or import. Download the photo and camera package for Blender, or return to Site Lens and choose Import from Photo tools.

What you get

Google Earth photo map (KMZ)
Your photographs as clickable camera icons. Each pop-up shows the photo fitted within 600 × 800 pixels with its caption, date, coordinates and where the location came from. Without a site, choose full size or reduced copies; at full size a photo stored sideways or upside down is copied upright so Google Earth shows it the right way up. With a site sent from Site Lens, the originals are included unchanged. A KML alone carries the pins and details without the pictures.
Civil 3D and MicroStation files
Photo locations in California State Plane (NAD83, US survey feet, zones I to VI), or anywhere else in WGS 84 / UTM, with the zone chosen from the photographs; in metres, US survey feet or international feet. A DXF with a point, a label and an arrow for the direction the camera faced where it is known (recorded by the phone against true north, typed by hand, or grid north from a Site Lens GIS point); a Civil 3D point file (PNEZD, comma delimited); a CSV with every field; and the photographs named by point number.
Blender cameras without a site
The photographs and their camera records in the same State Plane coordinates as the DXF, shifted to an origin near the photographs. The README gives the shift, so a model exported from Civil 3D or MicroStation lines up. The Landscape Camera Setup add-on (v0.5.1) sets each photograph as its camera’s background; a photograph stored sideways or upside down is copied upright first. By default the package also holds the ground around the photographs from USGS 3DEP with the USDA NAIP aerial draped on it, and each camera stands at the ground under its photograph plus an eye height you set (5 ft unless you change it).
Key view package
A key view map on an aerial photograph (on a plain ground outside the United States), 11 × 8.5 in, with a numbered pin for each photograph, a view wedge where the photograph records a direction, a scale bar and a north arrow: as an SVG for Illustrator, with a script that puts each part on its own layer, and as page 1 of a PDF. The PDF then has a page for each photograph, held within 6 × 4 in with its number and caption. A Data Merge spreadsheet and the photographs, as reduced upright copies, are ready for InDesign.
Photo pins on the 3D model
With a site sent from Site Lens, every photograph that has a location shows as a pin on the site’s 3D model. A tick box hides the pins.
A camera record for each photograph
Position, direction and lens values as far as the file records them, each with its source. You can correct a location by hand; a location you type is marked as placed by hand.
Photo Match
Look through a photograph’s camera at the model with the photograph over it, adjust the values and look again until edges meet, then save the camera as reviewed. This is a visual alignment, not a solved or survey-accurate camera.
Photo and camera package (ZIP)
The ticked photographs, their camera records and, if you choose, the site model as GLB. The Landscape Camera Setup add-on for Blender (v0.4.0 or later, a free download) reads the package and sets each photograph as its camera’s background.
Back into the Site Lens project
In Site Lens, Import from Photo tools copies the photographs and reviewed cameras into the open project. Its message reports how many were new, changed and the same.

Supported files and software

  • Photographs: JPEG, PNG or WebP. GPS is read from JPEG files when they have it. iPhone HEIC photographs cannot be read; export them as JPEG with location included.
  • Many photographs at once: a ZIP can carry a CSV or GeoJSON of points matched to the photographs by filename. A CSV template is on the page.
  • Limits: on the photo map without a site, up to 200 photographs and 1 GB, 32 MB per photograph; photographs from ZIPs count up to 160 MB in all, and one ZIP holds up to 100. With a site from Site Lens the page holds up to 160 MB. A download larger than about 150 MB comes in parts.
  • Google Earth: the KMZ is a standard KML archive.
  • Civil 3D: the DXF (AutoCAD R12) and the PNEZD point file. AutoCAD: the DXF.
  • MicroStation: the DXF.
  • Coordinates: California State Plane zones I to VI (NAD83, US survey feet), or WGS 84 / UTM (metres) with the zone chosen from the centre of the photographs, north or south of the equator; either in metres, US survey feet or international feet, with latitude and longitude in the CSV. State Plane zones of other states and national grids such as Lambert-93 or the British National Grid are not offered. The Blender download needs a California zone in US survey feet.
  • Blender: the Landscape Camera Setup add-on, v0.5.1, which reads packages with the terrain underlay as well as earlier ones. Version 0.5.0 (still available, and linked from READMEs of packages downloaded before November 13, 2026) reads packages made without the underlay, and refuses those with it rather than misplacing their cameras. The terrain is a standard GLB that Blender’s glTF importer opens.
  • Illustrator: the key view map as an SVG, with an ExtendScript (.jsx) that turns its named groups into layers. Inkscape opens the same groups as layers.
  • InDesign: Data Merge from a UTF-8 CSV with an @Photo column; the photographs sit beside the CSV and are listed by file name. Adobe’s release notes say Data Merge reads UTF-8 files from InDesign 21.5 (July 2026) and keeps accented letters and symbols from 22.0 (November 2026); in earlier versions, captions in plain ASCII merge cleanly.
  • PDF: the key view map and the photo pages, for printing or for placing page by page.
  • Site Lens: a site is sent from, and imported back into, Site Lens in the same browser on the same device.

What is in v0.5

Pilot v0.5, November 2026, adds a terrain and aerial underlay to the Blender download:

  • The ground around the photographs from USGS 3DEP, in the package’s coordinates, with the USDA NAIP aerial photograph draped on it, as terrain-underlay.glb. The add-on imports it with the cameras.
  • Each camera stands at the ground under its photograph plus an eye height, 5 ft unless you change it. The height is computed, not measured; phone GPS altitude is not used.
  • Landscape Camera Setup v0.5.1 reads these packages and draws each photograph in front of the terrain at half opacity, so the two can be compared.
  • The underlay is ticked by default; untick it for the camera package alone. Only the rectangle around the photographs is sent, to USGS (or USDA for the aerial if USGS does not answer).

v0.4

Pilot v0.4, November 2026, adds a key view package, the key view map and photo index that landscape architects lay out in Illustrator and InDesign:

  • A key view map on a USDA NAIP aerial photograph loaded at print resolution, 11 × 8.5 in: numbered pins, view wedges where a direction is recorded, GPS accuracy circles, a scale bar, a north arrow and notes. Pins that would hide each other are set at the nearest free spot and joined to their photo’s position by a thin line. It comes as an SVG for Illustrator, with its parts as named groups and a script that moves each onto a layer, and as page 1 of a PDF.
  • A PDF page for each photograph, held within 6 × 4 in (4 × 6 in when upright) and never cropped, with its number and caption below.
  • A Data Merge spreadsheet for InDesign (Number, Label, Caption, Original file, @Photo) with the photographs beside it, as reduced upright copies without embedded GPS.
  • Numbers match the aerial preview and the CAD download. The map is drawn in the chosen State Plane zone, or north up without one.

v0.3

Pilot v0.3, November 2026, adds a look at the photographs on an aerial photograph before you download:

  • Show on aerial under Review: the ticked photographs as numbered pins on a USDA NAIP aerial photograph, with a wedge for the direction each one faced, where the file records one, and its approximate angle of view (a line where the lens is unknown), and a circle for the GPS accuracy the phone recorded. Choose a pin to see its photograph.
  • The pins are numbered as in the CAD download. With a State Plane zone chosen, they are drawn in that zone, at the positions the CAD download writes; without one, north is up.
  • Nothing is requested until you choose Show on aerial. Only the rectangle around the photographs, which shows where they were taken, is sent: to USGS, or to USDA if USGS does not answer.

v0.2

Pilot v0.2, November 2026, adds downloads for other software without needing a site:

  • Up to 1 GB of photographs on the photo map without a site, about 100 phone photographs or more, up from 160 MB.
  • Reduced copies (longest side 2400 pixels) or full-size photos in every download, with photos stored sideways or upside down turned upright for Google Earth and Blender, and large downloads split into parts.
  • CAD files for Civil 3D and MicroStation in California State Plane.
  • A Blender camera package without a site, and Landscape Camera Setup v0.5.0, which reads every California zone.

v0.1

Pilot v0.1, November 2026, is the first version listed as its own tool. The photo map existed before as a separate page; the work with a site was a tab inside Site Lens and has moved here.

  • The photo map takes single files as well as a ZIP, typed locations, captions and a KML-only download.
  • A site sent from Site Lens opens with its 3D model and the photographs kept in the project.
  • Photo pins on the 3D model.
  • Photo work on a site is saved in the browser, and Site Lens can import it into the project.
  • When the photo tools and the project hold different versions of one photograph and the browser cannot tell which is newer, Import leaves the project’s copy alone and names the photograph.

Limitations

  • CAD points and Blender cameras are where the phone said it was, not survey positions. Phone GPS latitude and longitude are used as NAD83 without a datum shift, a difference of about 1 to 2 m in California, smaller than the GPS error. In UTM they are projected on WGS 84 with no shift to a national datum such as ETRS89 or GDA2020. CAD elevations are 0 unless you choose the phone’s altitude, whose vertical datum is not checked. Blender camera heights are the ground plus an eye height with the underlay, and set in the add-on without it.
  • The terrain underlay is bare ground: buildings and trees are not modelled, so roofs and tree crowns in the aerial lie flat on the ground and appear shifted. Line photographs up on curbs, paving edges and road paint. A photograph taken from a step, an upper floor or a bridge needs its camera raised by hand, and on a slope a GPS position a few metres off also moves the ground height under the camera. The photographs can spread over at most about 4,000 ft for the underlay (5,000 ft with a 500 ft margin). The download does not record which 3DEP survey, date or resolution fed each cell; the service’s catalog lists them.
  • In the CAD download, the direction arrow is drawn only where a direction is known against true north (recorded by the phone or typed by hand) or grid north (from a Site Lens GIS point). Magnetic and unreferenced directions are listed in the CSV but not drawn. Phone compass directions are often off by 10 to 20 degrees.
  • Outside the United States, or with UTM chosen, there is no aerial yet: Show on aerial sends nothing, and the key view map has a plain ground in place of the aerial. The Blender download is not offered with UTM, because Landscape Camera Setup v0.5.1 reads only California State Plane in US survey feet.
  • The aerial is USDA NAIP aerial photography, often a year or more old; the caption gives the newest flight date the service lists there, when it answers. NAIP covers the lower 48 states only; elsewhere the aerial may be blank, and the caption says so when the service lists no imagery. The aerial does not correct a position or a direction: pins and wedges show what the phone recorded. Magnetic and unreferenced directions are drawn dashed, as if from true north.
  • The key view package uses the same aerial photography and the same pins: it does not correct a position or a direction. Its text is set in Arial in the SVG and in Helvetica, the PDF’s standard font, in the PDF. Caption characters outside the Windows Western character set, such as Greek or Chinese letters and symbols like ≥ or ✓, show as “?” on the PDF pages; the README names the views and characters, and the spreadsheet keeps them. Captions longer than three lines end in “…” on the PDF pages; the spreadsheet keeps them whole.
  • A pin shows where a photograph was taken as far as its GPS or your own entry says. Phone GPS is approximate, and less reliable under trees and beside buildings. Check locations before sharing.
  • Photo Match is an alignment by eye. It does not solve the camera from the photograph, and it is not a survey.
  • The photo map on its own does not save your session; keep your original files.
  • Work on a site is kept in this browser on this device only. Clearing the browser’s site data removes it. Import it into the Site Lens project and save the project file to keep it.
  • A site can only be sent from Site Lens, which covers San Diego County.
  • A project photograph whose saved camera record does not fit the site’s current coordinate frame is left out of the send, named, and kept in the project.
  • A photograph removed here returns the next time the site is sent, because it is still in the project.

Not yet tested

  • The DXF and point file have been checked with an independent DXF reader and against PROJ coordinates. The DXF has been opened in Civil 3D with one photograph; the point file has not yet been imported into Civil 3D, and neither has been opened in MicroStation.
  • Neither camera package has been opened in Blender with the add-on since the tools moved to this page. Add-on v0.5.1 and the terrain underlay have not yet been opened in Blender: Blender is not installed where they were built. They were checked with automated tests, including the add-on’s own Python checks on the files, and with real USGS terrain and aerial requests at Presidio Park, San Diego (Zone VI), and Civic Center, San Francisco (Zone III).
  • 100 full-size phone photographs have not been run through every download on a phone or tablet.
  • A saved Site Lens project with photographs from an earlier version has not been sent here.
  • The site view was checked in a Chromium-based browser on a desktop, not in Safari or Firefox and not on a phone.
  • Show on aerial was checked on a production build in a Chromium-based browser, at desktop width and at 375 px, with five synthetic JPEGs carrying GPS tags at Presidio Park, San Diego. The pins matched PROJ coordinates in Web Mercator and in Zone VI. It has not been tried with real phone photographs, in Safari or Firefox, on a real phone, or with 200 photographs. The aerial took up to about 8 seconds to arrive; the USGS date lookup did not answer within 6 seconds in two of three tries, so the caption often has no date.
  • The key view package has not been opened in Illustrator, InDesign, Inkscape or Affinity, and the layer script has not been run. It was made on a production build in a Chromium-based browser from five small synthetic JPEGs carrying GPS tags at Presidio Park, San Diego, not from real phone photographs. The PDF was read and drawn with Poppler, the SVG checked as XML and drawn in the browser, and the ZIP opened with unzip. The print-resolution aerial took about 18 seconds to arrive.
  • UTM and the metre and international-foot files have been checked only with automated tests: against PROJ 9.9.0 conversions and an independent series at the zone central meridians and five cities (Paris, Tokyo, Sydney, São Paulo, Cape Town), and through the downloads with synthetic photographs carrying GPS tags at those cities. They have not been tried with real photographs taken outside California, and the files have not been opened in CAD or GIS software.
  • There have been no practitioner interviews.

Questions

Is it free?

Yes, it is free to use.

Are my photographs uploaded?

No. They are read and processed in your browser. There is no account. Show on aerial, the key view package and the Blender terrain underlay send only the rectangle around the ticked photographs, which shows where they were taken, to USGS (or USDA) to fetch the aerial photograph and the terrain.

Does GPS give a matched camera?

No. GPS gives a position only. Direction, lens and vertical alignment come from the file where it records them, and otherwise from your review in Photo Match.

Do I need Site Lens?

No. The photo map, the CAD files and the Blender cameras work on their own. The pins on a 3D model and Photo Match need a site sent from Site Lens.

Which State Plane zone do I choose?

The one your drawings use. Outside the United States the page chooses Automatic (UTM), the UTM zone of the ticked photographs’ centre; in the United States outside California you can choose it too. California zones follow county lines; the page lists the counties in each zone and warns when photographs lie far from the area the zone is designed for. That check does not follow county lines, so a photograph in a neighbouring zone may not be flagged; check the county list.

Related: Landscape Camera Setup · Site Lens · Site Dossier