Imagine you draw a line following a trail on a map. Looks good, ship it! Now someone else loads that same line on their computer and it looks like a jagged mess because they are twice as zoomed in on the map as you were. Oops. What about the wide parts vs narrow parts of the trail? Do you represent that as two lines or just keep one down the middle? You send your trail to a friend who overlays it on their map that uses a different datum? How were the photos from the airplane assembled, and how did they represent a round object on a flat image? Did they have a good GPS lock when they took the photos, or did they even bother to check? What if the line you created is to be used 100 years in the future when the center of mass of the earth or magnetic north has shifted, how does your coordinate system account for that?

I know just about enough GIS stuff to fit on a few index cards, but I quickly realized it is way more complex than how simple Google Maps makes it out to be.

Sorry, hallucinate in the sense that the map says there's a track but there isn't anything there, whether or not it was drawn by a human. I meant it as an allusion to the map tripping balls but forgot that the overlap with AI terms would confuse HN.

With OSM I think a lot of walking tracks are from GPS traces uploaded by volunteers, so maybe sometimes stuff sneaks in. Or maybe the map shows old tracks that have since been erased by rangers. Or maybe there's a nearby track that has been marked down in the wrong place.