Kevin does have a point. I think what he's also trying to say is that the quality of the objects used on most routes could use some tuning, but i'm not going to get into that.
While it may be a common factor that non-fictional routes aren't getting put out as frequently as the fictional ones, there's also the factor that no one has been here to aid in development. I've been hearing a lot about why we haven't put out routes yet, and why the ratio of real to fictional is on a 1 to 10 ratio, but I haven't heard about anyone helping us with the work load. Even this topic is a clear example.
Like EDawg said, this is a hobby, and we're not getting paid for it. You don't know the real meaning of the dollar until you're earning it, and setting your own free time aside for your work, or your family. Back when this site started, routes were being put out all the time, both fictional and non-fictional. Asking us to do that 5 years down the road, when we're all grown and have people and bills to support obviously isn't going to get you the same result. If you're being honest about what you do, and you know you don't have time to develop, or contribute, then it's fine. You're not at fault for being human.
This doesn't however, go the same for the crowd of below 18. At 18 you become an adult, so anything below that is still in his/her early adolescence. I'm developing because I love doing it, not because I want to appease you. If I lost interest in what I did, then in the blink of an eye, my work would be discontinued, and that would be the end of that, until someone else decides its their time to pick up the slack.
By the way, on the basis of the fictional routes, at one point in the site's history it was a rule that a fictional route be made first so that the developer get a feel for what they are doing, and obviously it's become a habit (one, because there's a limitless amount of creativity in the fictional routes than there is in the real ones). At that point, an accurate skeleton of a real route would be given to the developer to detail, and that should've yielded a similar output. You can't just jump into something and end up getting in way over your head. It's like thinking you know every single thing about a Windows PC but when you get put to work in their technical department, one line of encrypted code may seem like hieroglyphics to you. It's a stepped process that needs to be taken very slowly.
BStyles