Have a drone orthomosaic too big to open in CAD? The FixFinder Ortho Tiler cuts a GeoTIFF of up to 30 GB into square tiles, writes a .tfw world file for each one, and hands you a .dwg with every tile already attached at its real coordinates.
A full-site drone orthomosaic is often one GeoTIFF of many gigabytes. Desktop GIS reads it in pieces, but a CAD drawing has to load the attached image, so a single huge file can make the drawing slow or impossible to work in. The fix is to cut the ortho into a grid of smaller tiles, give each tile a world file so it knows where it sits, and attach only the tiles you need. This guide explains the parts in plain English, with sizes in feet first.
The steps at a glance
- Check the GeoTIFF. Note the file size, the coordinate system and its units, and the pixel size before you cut anything.
- Pick a tile size. Tile width on the ground equals tile size in pixels times the pixel size, so a 5,000 pixel tile at 0.1 ft per pixel covers 500 ft.
- Cut the tiles with world files. Cut the ortho into square tiles and write a .tfw world file next to each tile.
- Attach the tiles in CAD. Attach only the tiles you need, placed at their real coordinates from the world files.
- Check the alignment. Snap to a known point or your survey linework and confirm the tiles land where they should.
1. Check the GeoTIFF
Before you cut, know three things: the coordinate system (and whether its units are meters, US survey feet or international feet), the pixel size (ground sample distance) and the file size. Your mapping software shows these in the layer properties; on the command line, GDAL's gdalinfo prints them. A classic TIFF tops out at 4 GB; bigger files use the BigTIFF variant, which GDAL controls with its BIGTIFF creation option.
2. Pick a tile size
Tile size is set in pixels, but you think in feet. Multiply: tile size in pixels times the pixel size gives the tile width on the ground. A 5,000 pixel tile at 0.1 ft per pixel covers 500 ft by 500 ft. At 0.25 ft per pixel the same 5,000 pixels covers 1,250 ft. Smaller tiles open faster in CAD but give you more files to manage; pick the size that matches how much of the site you work on at once.
3. Cut the tiles and write world files
A world file is a six-line text file that sits next to an image with the same name, such as R01_C01.tif and R01_C01.tfw. According to GDAL's documentation, the six values are:
- Pixel size in X
- Rotation about the Y axis (usually 0)
- Rotation about the X axis (usually 0)
- Negative pixel size in Y
- X coordinate of the center of the upper-left pixel
- Y coordinate of the center of the upper-left pixel
Two details trip people up. First, the coordinates are for the center of the top-left pixel, half a pixel in from the corner. Second, a world file does not record the coordinate system. The numbers are in your ortho's units, so a State Plane ortho in US survey feet gives a world file in US survey feet. Note the system and set your drawing to the same one.
With the Ortho Tiler (Pro). Upload the GeoTIFF (it does not need to be a Cloud Optimized GeoTIFF), or up to 20 corridor orthos that it joins first, pick a square tile size in pixels and optional LZW compression, and download one zip. Tiles are named by row and column (R01_C01, R01_C02 and so on), butt edge to edge with no overlap, and the tiles on the right and bottom edges are smaller. Tiles with no image are left out. The zip also has a tile index as KML for Google Earth and DXF for CAD.
Free, with GDAL. If you are comfortable on the command line, GDAL's gdal_retile.py cuts a raster into tiles of a set pixel size with -ps (the default is 256 by 256, too small for CAD) and writes them to the folder you give with -targetDir. Adding the GeoTIFF creation option -co TFW=YES writes a .tfw next to each tile. For one area only, gdal_translate -srcwin cuts a single window by pixel offset and size.
4. Attach the tiles in CAD
Set the drawing to the ortho's coordinate system and units first. Some CAD programs read a world file when you attach an image; in others you place the image yourself using the insertion point and pixel size from the .tfw. The Ortho Tiler skips this step: extract the whole zip into one folder and open the .dwg it includes, and every tile is already attached at its real coordinates. Attach or load only the tiles around the area you are drafting.
5. Check the alignment
Zoom to a control point, a checkpoint or a feature in your survey linework and confirm the image lines up. If the tiles land half a pixel off, the world file was read as a corner instead of a center. If they land far away, the drawing and the ortho are in different coordinate systems or units; the State Plane zone finder and the unit converter help sort that out. To see the tile layout or your CAD linework over imagery in Google Earth, the free CAD to KML converter turns a DXF or DWG into KML in your browser.
Questions
What is a .tfw world file?
A plain text file of six numbers that places an image on the map: pixel size in X, two rotation terms (usually 0), the negative pixel size in Y, and the X and Y coordinates of the center of the top-left pixel.
Does a world file say which coordinate system the tile is in?
No. It only holds the six numbers. The values are in the units of the ortho's coordinate system, for example US survey feet for a State Plane ftUS ortho, so keep a note of the system and set your CAD drawing to match.
What tile size should I use?
Pick the ground size you want, then divide by the pixel size. At 0.1 ft per pixel, 5,000 pixel tiles are 500 ft square; at 0.25 ft per pixel the same tiles are 1,250 ft square. Smaller tiles mean more files but lighter drawings.
Is the FixFinder Ortho Tiler free?
No. It is a Pro tool: FixFinder Pro is $9 a month and includes 20 tiling jobs a month for GeoTIFFs up to 30 GB. The free route is GDAL on your own computer.