Kevin Reilly wrote in message ...

You can perhaps see where I'm headed with this. We have at least one
bridge that's in the right place but the wrong geometry. We have several
reported cases of bridges that aren't where they should be, and at least
one that is where it shouldn't be. All of which suggests to me that many
of the bridge problems could well be down to simple *typos* in the
scenery database. Even issues with bridges in the right place but of the
wrong type could be explained by this, if generic bridge types are
defined by a flag pointing to a generic model and the flag is wrong.

Could this be the case, or am I putting 2 and 2 together and getting 6?
As I said, I know nothing of FS scenery design or implementation. If I'm
way off target, please let me know.

I strongly believe you are right. Why? Because of what I have found
with regards to the Lake Pontchartrain Causeway near New Orleans. The
Causeway, at 24 miles long, is the longest bridge in the world - but
it doesn't show up over the waters of Lake Pontchartrain in FS2004.
Yet, the bridge *does* show up, over *land*, moved exactly 24 miles
north of where it should be! It's as if it hop-scotched over itself.

Is this a lat/long problem? Or is it a bit more complex? If it's
some sort of toggle in the code or database, it would explain why the
bridge is there, but not where it should be. So I would tend to agree
with you on your conjecture.

Krunch