A client should not need GIS software, a workstation, or the patience to download a two-gigabyte GeoTIFF just to look at a map. That delivery model made sense when every orthomosaic went straight to a GIS department. It makes no sense for a superintendent checking grading from a phone, an owner reviewing a property from a laptop, or a project manager who only needs to pan, zoom, and understand the site.
Drone ortho web tiles solve the viewing problem. Instead of treating the full-resolution orthomosaic as the only way to see the work, the map is prepared as browser-delivered tiles. The client opens a viewer and moves around the site at the level of detail the screen needs. No giant 2GB download before the first look. No phone call explaining how to open a GeoTIFF. No pretending that a shared-drive link is a client portal.
This is the delivery side of SkyView. SkyView is the front door: process the project locally on the pilot's own hardware, without a per-map cloud processing fee, then make the result useful to the people who paid for it. Processing and delivery belong in the same practical workflow, but they are not the same job. A finished ortho sitting on a desktop is not yet a client experience.
The two-gigabyte handoff is a bad default
Large orthomosaics are normal. A detailed map over a large site can become a very large raster, and the master GeoTIFF still matters when the client needs the georeferenced deliverable for CAD, GIS, measurement, or archive. The mistake is forcing every stakeholder to download that master file before anyone can review the map.
A project executive may only need to check the current site condition. A superintendent may want to zoom into a haul road. An owner may want to compare progress around one building pad. Those are viewing tasks, not file-management tasks. Making each person download the complete raster wastes time, creates duplicate files, and guarantees support questions from people who never asked to become GIS technicians.
The professional answer is not to shrink the only deliverable until it is easy to email. That throws away the detail the pilot worked to capture. Keep the proper master output, but give ordinary stakeholders a browser path to the map.
What browser tiles change
A tiled web map breaks the viewing experience into pieces sized for the current area and zoom level. The browser requests what is needed for the screen instead of pulling the entire source raster before it can show anything useful. That is why a client can open the project, see the overview, and move into a specific section without first receiving one enormous download.
The benefit is not a clever compression claim. It is a better distribution model. The high-resolution source still exists. The tiles are the viewing layer. Each does a different job:
- The master ortho is the geospatial deliverable for teams that need the actual file.
- The browser tiles are the accessible review experience for clients and stakeholders.
- The pilot's local project remains where the processing work was performed and managed.
That separation matters. Pilots should not have to choose between a serious deliverable and an easy client experience. A usable system supports both.
SkyView starts on the pilot's hardware
Cloud processing has trained pilots to treat every map like a meter that starts running when the images upload. More acreage, more images, another revision, another map: each can become another processing charge. That model is convenient for the vendor. It is not always good for the operator's margin.
SkyView takes the opposite position. Processing runs locally on the pilot's own compatible hardware. There is no per-map cloud processing fee. The pilot is not shipping an entire image set to a cloud queue just to begin turning photographs into an orthomosaic.
Local processing is not a slogan about avoiding the internet altogether. Client delivery still needs a practical online experience. The point is to put the heavy processing where the pilot controls the hardware and the economics, then use the browser for what browsers do well: fast access, sharing, and review.
That is a more honest division of labor. The desktop does the heavy map processing. The web delivers the view. The client does not need the processing machine, the raw imagery, or specialized software to inspect the result.
No 2GB download is about the viewing path
This distinction needs to be explicit. The “no 2GB download” in this post refers to orthomosaic tiles viewed in the browser. The web viewer tiles the map so the client is not forced through a giant GeoTIFF before the first look. That is the delivery model: browser-delivered tiles, and no hard 2GB viewing cap on that web viewer.
Gaussian splats stay desktop-only. They are a different product path from tiled ortho review in the browser. Keep that distinction when you talk to a client. If the deliverable is an ortho, browser tiles avoid making them download a giant raster just to view it. If the conversation turns to splats, that work stays on the desktop, not in the same tiled web viewer. Pilots deserve that precision before they promise anything to a customer.
What the client actually experiences
The client experience should begin with the site, not the file format. Open the project. See the map. Pan to the area that matters. Zoom in. Review from the browser. That simple sequence removes several points of friction from delivery.
There is no “download this first and call me if Windows does not know what a TIFF is.” There is no requirement that accounting, ownership, and field operations all install the same GIS package. There is no need to make a lightweight JPEG the main deliverable merely because it opens easily.
This also makes review faster. When a client can get into the map immediately, feedback becomes specific: “look at the northeast stockpile,” not “the file will not open.” The conversation moves from technology trouble to the work itself.
That is what a client portal should do. It should reduce the distance between delivery and a useful decision. A folder full of files may be storage, but storage alone is not presentation.
Keep the downloadable deliverable when the job requires it
Browser viewing does not replace the contractual deliverable. If the scope calls for a GeoTIFF, the client should receive the GeoTIFF. If their surveyor needs the raster in a project coordinate system, a browser view is not a substitute. If they need an archive copy, give them the file.
The tiles remove an unnecessary burden from everyone else. They let a broad group review the map while the technical user still receives the master. This is especially useful on construction progress, land management, inspection context, and other jobs where many people need visibility but only a few need the source raster.
Write both parts into the scope when both matter: browser access for review and the named downloadable file for technical use. That prevents the viewer from being mistaken for a lower-resolution replacement and prevents the giant file from being mistaken for the only way to see the job.
Delivery is where the pilot looks professional
Pilots spend enormous effort on capture plans, overlap, control, processing, and quality checks. Then too many hand the client an anonymous cloud-drive link and call the job complete. The map may be excellent, but the delivery makes the business look improvised.
SkyView is designed to make local processing and client-facing delivery parts of one professional system. The ortho is produced on the pilot's hardware without a per-map cloud processing charge. Browser tiles make that ortho practical to review without a giant download. The master file remains available when the scope requires it.
Pilot Ledger gets the short second beat: the quote, job record, and payment workflow can sit behind the same client relationship. That business layer matters, but it is not the headline here. The headline is that SkyView turns local processing into a deliverable clients can actually use.
A better default for September
SkyView is waitlist-only for September 2026. It is not available as a finished public product today. The goal is straightforward: let commercial pilots process on their own hardware, avoid per-map cloud processing fees, and deliver orthomosaics through browser-friendly tiles instead of forcing every client through a multi-gigabyte download.
If that matches the way you want to process and deliver work, join the SkyView waitlist through Pilot Ledger pricing.