# I let Claude Code build my home golf courses in a video game

Joe Hill, 2026-11-15. https://joehill.net/posts/ai-built-my-home-golf-courses/

> Yes, an AI agent can build a real golf course in PGA TOUR 2K25 from free public data: USGS LiDAR for the ground, OpenStreetMap for the layout, aerial photos and public scorecards for checking. Claude Code did the building. It took several passes per course, and I still do the publishing, the local knowledge and the final say.

Play video: [I had AI rebuild my old home golf course from free map data](https://www.youtube.com/watch?v=OvvnpnT1eKQ)

## The story

My buddy back home and I play PGA TOUR 2K25 on the PS5. The game comes with a course designer, so in theory you can build any course you want, including the real ones we know from back home in Indiana.

In practice, the course designer is a bear. I wasn't about to shape every hill and bunker of a real course by hand.

That's when I started thinking. The data to do it is all publicly available, and it's free.

The U.S. Geological Survey has scanned the ground with LiDAR, so the hills and the trees are already measured. [OpenStreetMap](https://www.openstreetmap.org/) has the greens, fairways, bunkers, water and tees drawn in. The state of Indiana publishes aerial photos. And the scorecards, with the real yardages and pars, are on public scorecard sites.

So I decided to turn it into an AI project. I wanted to see if I could get one big idea through: let Claude Code build the courses for me.

I started with the ones from back home, like Leaning Tree (my old home course), Rock Hollow and Purgatory. The video up top is how they came out.

Here's what the agent does on each course:

1. Gathers the data: the map layout, the LiDAR scans, the aerial photos and the scorecard.
2. Builds the course file with a community tool called [TGC Designer Tools](https://github.com/malifica/TGC-Designer-Tools). The terrain and the trees come from the LiDAR, and the holes come from the map.
3. Adds the water, the tees, the grounds (clubhouse, buildings, carts) and a backdrop of farmland and distant hills.
4. Does a realism pass. It sizes every tree to the scan, puts every tee on its real tee box on level ground, clears the tee shots, checks every hole against the aerial photo, and checks every tee's yardage against the scorecard.
5. Drops the file in the game folder for me to open and publish.

When the map and the scan data are both complete, a course takes the agent roughly 35 to 60 minutes to build, and about zero minutes of my time. The realism pass is roughly another 15 to 30 minutes of the agent's time.

That's the happy version. It also took a lot of passes, and a few things went sideways along the way.

## How it went

Honestly? Pretty convincing, and not on the opening try. Rock Hollow got to version 9 before I published it. Leaning Tree got to version 5 and Purgatory to version 4. Most of the problems showed up once real people played the courses, because my PC can't run the game well enough to play a hole. So the real feedback came from my buddy back home and my stepdad. Here's where it struggled and what fixed it.

### Where it struggled

- The trees were way too big. The tool gives each scanned tree a random large model, so they came out about twice their real height and the real gaps closed up. My buddy found hole 1 at Leaning Tree blocked by trees. The fix was measuring the game's tree models and resizing every tree to its scanned height. Rock Hollow went from 37 blocked tee shots to 0.
- Some tees were in the wrong spot. My stepdad played Rock Hollow and said it "played amazing," but he found one tee with no tee box and one sitting on a downslope. Placing tees by the scorecard yardage lands them a few meters off the real box. Now each tee gets snapped onto its real box and the ground under it gets leveled.
- Power lines looked like rows of trees. In the LiDAR at Purgatory, the lines read as trees. The agent built a filter that finds them and takes them out.
- Hand-traced holes were off. The map had just an outline for Leaning Tree, so the holes were traced from aerial photos, and they landed 4 to 16 meters off. The greens, bunkers and tees got re-fit to the aerial photo, and then I marked up the rest myself.
- It guessed some routings wrong. Where the map had no hole lines, the agent had to guess how each hole plays. A hole that comes out 40 or more yards short of the scorecard means the guess is wrong. At Chippendale, the real back tee on hole 10 sits up by the clubhouse, over a big ravine. I knew that from playing there, and I had to point it out.
- It fixed the wrong thing once. The game has a meter for how much a course can hold, and it fills up. The agent started by trimming trees, which hurt the realism and barely helped. Then it worked out that the water and the size of the terrain are what really fill the meter.

And some of it is still on me. The agent can't drive the game, so I do the publishing. I bring the local knowledge. And I'm the judge of "realistic," so nothing is done until I'm happy with it.

## If you want to try this yourself

Everything here is free public data plus one community tool. You'll need the PC (Steam) copy of the game to build the course file.

1. **Start with the map** Look your course up on [OpenStreetMap](https://www.openstreetmap.org/). You want greens, fairways, bunkers, water, tees and hole lines. If all it has is an outline, the holes have to be traced from aerial photos, and that's where my trouble started.
2. **Get the elevation scan** The ground comes from USGS LiDAR scans. Most of my Indiana courses used the statewide scan. Purgatory used a newer county scan, the sharpest of the bunch.
3. **Grab the aerial photos and the scorecard** I used Indiana's state aerials and USGS NAIP photos to check where the greens, bunkers and tees really are. The yardages and pars came from public scorecard sites like Stymie, GolfPass and BlueGolf.
4. **Build it with TGC Designer Tools** [TGC Designer Tools](https://github.com/malifica/TGC-Designer-Tools) is the community tool that turns the LiDAR and the map into a PGA 2K25 course file. I had Claude Code run it for me.
5. **Check it against the real thing** Size the trees to the scan. Put every tee on its real tee box, on level ground. Check every tee's yardage against the scorecard. If a hole plays way short of the card, the routing is wrong.
6. **Get somebody who knows the course to play it** Open the file in the game's designer, publish it, and hand it to somebody who has walked the real place. A course traced from photos is fast to draft, but the routing isn't reliable until a local marks it up.

## Got an idea you've been sitting on? Let's see if AI can build it.

And [obligatory shameless plug] this is the same thing I do for businesses. Somebody has an idea, the pieces to do it are already sitting there, and it needs a person to point AI and automation at it and keep an eye on the result. If you're interested in seeing what that could do for a problem in your business, reach out!

Work with me: https://joehill.net/?book
