Sorry, couldn’t resist… 😉

just so every one is clear, selling to google is creepy, not giving the guys $500M each

I like this option better…

Creepiest suggestion maybe ever

Yes, but this was considered to be “plan B”. plan A was that Larry and Sergei just give us $500,000,000 each with no strings attached, as well as full access to all of Google’s data and IP, and in return, Austin takes them for a ride in his airplane. 🙂

I can see only advantages 🙂

There’s already a measuring tool – but I do encourage you to poke at the code and see what you can do… 🙂

Probably a matter of lowering the bar (higher-level x-platform) and being able to share tools. A person who can write python or some other scripting is not necessarily a c programmer. It leaves a strong core to WED and a lighter addon for things people may or not see as useful.

However, I’m well aware this is not a trivial thing to implement and probably depends a lot on the way tools and interfaces are currently implemented and whether they can be (reasonably easily) exposed through a scripting interface. The other thing would be to find out if there is a sufficient number of x-plane scenery developers who would take advantage of such a capability to warrant spending any time on it. If there’s only a couple of hundred WED users, contributed code would seem better. If there’s a 1000 users, a scripting interface might be useful.

Maybe I should make a tool for WED (something simple like a measuring tool) using the current source so I don’t sound so much like I’m making this up as I go along 😛

When done properly, I doubt it’d be high-traffic. Ideally, once a user starts working on an airport and have determined the area, WED would just selectively download the few tiles they need for the area. That can all be automated, and requires only very few tiles at the start of a project. At most, further work would require downloading a few more tiles further down the road.

All in all, that would cause way less traffic than the average slippy map use of a single regular OSM user.

Unidentifiable and long gone. The message was “Unable to open .XML file: not well-formed (invalid token).” No clue how to get that one back but restarting was easy using the data of the unworkable one.