This shows two different fields. The funny shaped one was created in AOG by driving and making a boundary. That is why it is so crooked. The retangular one on the left was drawn in google earth, imported into AOG as a new field. Each one was driven in the simulator and then the kml file for each was loaded into google earth. While back in google earth, I measured the offset distance from AOG boundary and Google earth polygon. Looks like about a meter. Probably in the rounding. The red cut lines are now bigger so when we start importing backgrounds into AOG, you will not “fall off” the world. Again, the green is auto tool, the yellow is manual tool, and the blue is just driving around. If you trace them you can see they both start in the same point and the field on the left was driven too over the field on the right. Of course you could not see the field on the right in AOG. At least not yet…
If you are interested, Here are the KML files for both fields. Just edit the names to drop the “.txt”.
Notice how small the files are. Again, I have no idea how big a kml file can be, but these work well. You can turn each item on and off in the window to the left. Pretty cool stuff.
AOGkml-20191215102709.kml.txt (87.5 KB)
AOGkml-20191215114824.kml.txt (77.6 KB)