I just didn't quite get Stuarts answer on the ml, will ask next time we& catch him in a call (if we& remember). (Also, if we& find a way to get more affordable hosting of big datasets, we&'d rather use that for publishing ortho scenery) if you consider how much money in terms of power bill you've spend on generating this) and those people get barely anything back (see Torstens liberapay) So yeah, few people spending a lot of money to run this (I'd actually count you, David, into this. receive currently nothing for hosting all of this (or the about 1.5k we spend on osm2city). James, as I said, idk what's the deal at his work place. look here to see how well this goes barely covers the cost and idk what the price tag will be on his AWS stuff for building osm2city (still think it's not a financially wise choice to run this on AWS) Torsten tries to cover cost with liberapay. there's an electricity cost and we could live with a slower (and cheaper) internet plan if we didn't host stuff.Īnd to be honest, I don't see this cost decreasing any time soon. and we run our 2 mirrors using cloud machines which cost about 50 bucks a month plus it uses some power at home cause the one mirror is at home (the VPS for that is only to get a static IPv4), its shared with other stuff and our home internet traffic too so I can't confidently put a cost on this but. I know Torsten had recently take measures cause cost was getting more (iirc he wrote about that on the mailing list), James is running it at work, idk what's the deal there. I'll also update to a new to pick up changes in towns, cities, roads, farmland, piers, parks, breakwaters, etc.ĭgginson wrote in Sat 4:31 pm:(though in a few years, it might be affordable enough to keep both styles).Ĭause right now for most people this is really affordable (free), and like 3 people host the core of the scenery stuff, Torsten, James and us&. Switching to a 30m raster for v2 will improve that considerably, but the source data is almost 100x as big, so it's going to take some serious time and computing power for the pre-processing. Right now, the background land cover in my scenery (where no detailed vector data is available from OpenStreetMap) is chunky because I'm using a vectorised global 250M land cover raster. I imagine every FlightGear user will end up having their preference, and some will even switch from flight to flight. I think it will be good to have the choice between the two kinds of scenery (three, counting photo ortho scenery), because WS3.0 will always look a little pixelated when you fly closer to the ground (say, below 6,000 ft AGL - TBD), while WS2.0 vector scenery can really bring out the small details like parks, inland shorelines, creeks, and ponds on the other hand, WS3.0 scenery can be easier on the video card, and show a lot more variety when you're at higher altitudes. Other people are working on that, and doing a good job as far as I can tell. Merspieler wrote in Fri 11:36 pm:will V2.0 be WS3.0? Thanks to everyone who has tried this out, posted kind words, and reported bugs (if you find any in this release, please post them at. south of 60N, then to all of Canada and the U.S., then to Greenland, Iceland, the Caribbean, etc, and finally to all of the Americas.įor v.2, whenever it happens, I plan to move from a 250m raster to a simplified 30m raster as a source for background landcover to smooth out the shapes, and will likely also add more features from OSM.īefore that, though, I'll focus on bug swatting and on adding some 3D models that will be available for all scenery builds - my priorities are major bridges (which are important landmarks from the air) and some lake freighter models (the Great Lakes feel empty without them). Then I expanded to the buckets around the St Lawrence Seaway (including the river and the Great Lakes), then to Canada and the U.S. My first scenery bucket was w080n40, which turned out to the be hardest one in the Americas to build because of the density of roads, towns, etc (it includes NYC, Toronto, Montreal, Boston, Ottawa, Buffalo, and Québec, among others). I started in November 2022 as a kind of therapy, a few weeks after I was forced to sell my plane after being medically grounded, and have been building and rebuilding almost continuously since then. I may put out minor versions (like 1.01) as bug fixes, but there will be no more major feature or configuration changes for the v.1 stream, so it's stable enough to replace the default TerraSync scenery as soon as we're set up to regenerate osm2city for 128 10x10 deg scenery buckets. I have completed an internally-consistent build of my FlightGear Americas Scenery and am releasing it as version 1.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |