• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Orthoimagery Question

Messages
53
Country
unitedstates
I am wondering if there are any good tutorials on dealing with super high-res ortho in global mapper and how to divide the images properly and output as 0.3cm. I'm trying to create 60GB worth of 2100 sq. miles, and for now all I want to do is see some end-result in FSX to test (even just compile a little). Maybe I will just try to compile the airport tiles and test that first.

Any good hints / suggestions / tutorials, most of the terrain tutorials online are about taking one single airport or area and using Google Maps through SbuilderX, that is not what I want to do. I found a couple USGS to FSX tutorials, but they sure seemed rather incomplete at best.
 
Last edited:
Well, I figured out how to load the index file into Global mapper as the base coordinates and map, so that is good. I also figured out how to create a catalog of independent smaller regions (it was very simple).

I guess I will play around with it some more before asking more questions...
 
Thanks for the tips, very helpful and that allowed me to figure it all out --- except ONE thing left is killing me, something I am doing to the image in the remastering process did end up making it non-compilable by FSX resample.exe.

Do you have any hints on how to overwrite the GEO-TIFF header outside of the FwTools and Gdal package, it doesn't work. I've followed 5+ different ways to do it and FSX can never re-compile my post-mastered work. I have no issues compiling it pre-mastered (after GDALWARP it compiles fine, but after any image editing EVEN when I re-write the header and INF it still fails in FSX resample). A few more things I can try but running out of ideas.

I tried listgeo to geotifcp -g, and it re-creates the TIFF just fine but the TIFF does not compile in FSX.
 
Last edited:
two things important for the resample. the coordinats must be geographic (latitude longitude), and if you edit the image you will have to reinsert the geographic data. with the geotifcp -g command etc.
Sorry but I can't help much more in this but could be of help.
 
Thanks for the tips, very helpful and that allowed me to figure it all out --- except ONE thing left is killing me, something I am doing to the image in the remastering process did end up making it non-compilable by FSX resample.exe.

And from here the fun begins... I haven't a clue as to what you are doing to take a fairly simple process and keep screwing it up.

Explain to me why you "think" it's appropriate to overwrite a GeoTiff header. Are you so well versed in geo-spatial analysis to know, not think, what is or is not appropriate for a GeoTiff header?

Are you aware that the Resample compiler does not need to have a GeoTiff as source material?

Are you aware that a BMP file is perfectly acceptable as a source for the Resample compiler, so long as the INF file contains the appropriate data for the compiler to process?

I'm not trying to be harsh or anything, but it's not rocket science we are dealing with to make photo based scenery, but there is a need to have a structured process and to maintain that process to be able to do any large scale project. And there is a need to have some understanding of the X's and O's of the underlying data that will be a basis for the process.

Let's see, following your threads at Avsim your experience is that in the past month you've bought some payware photo work, you are an IT guy and that makes you imminently qualified to make scenery for FSX and you found some source material that should look fairly nice for people that have a semi-super computer. How hard can it be, right???

I don't have the slightest idea which direction to tell you to turn to, because your comments don't give any clue as to what you are doing and what you are doing it with. Other than you found the Utah GIS site. (BTW, they are nice people to deal with, based upon my past experience.)

If I did have some words of wisdom based upon the little that you've posted, it would be that Global Mapper should be seriously considered and that sufficient time be spent trying to become familiar with it's capabilities.

It has a nice scripting process, that when coupled with a little programming magic can automate a whole lot of the process that you seek to undertake.

But it seems like you think it's easy to just churn out some BGL files. It can be fairly easy to generate large amounts of source material for compiling, but you need to be able to walk first before you try to run a marathon!
 
Wow, that is a lot of unnecessary picking. I am not screwing anything up, I've just started compiling this project with post-mastered files within the past day (keep screwing it up??), and it is purely a matter of procedural or syntactical issue, excuse you :)

I am not an IT guy, I am a programmer of 25-years thank you, and furthermore I wrote a program in .NET to automate everything myself and I don't need extra scripting, but apparently I misunderstand part of the process. For now I just want to compile a post-mastered freeware scenery. Learn some etiquette.

I don't have any problems compiling pre-mastered files, as I said only cannot re-inject the file properly. I already tried listgeo > .gtf, then creating the new TIF file as such: geotifcp -g t94Geo.gtf Tile94.tif FinalTile94_WGeo.tif

Note:
I am aware that people said as long as the data is in the INF, but that is not working for me. Once remastered, the file won't compile regardless of what I put in the INF file. Perhaps then the issue lies in the fact that I need to re-examine the INF file, but according to posts in here as an alternative it should work by rewriting the GEO-data from a pre-mastered file, but it doesn't. That was my point. I also suspect another possibility is that the remastering process is modding the file in a way that is making geotifcp fail to rewrite the geo-data correctly. I am not using the same generic remastering process as others are in here, which might be the cause... I see that my Geo-Data output is not being written correctly and there appears to be an issue with the file format.

Check the attitude at gate A-5...
 
Last edited:
I figured it out with no thanks or help from the above smart aleck comments by LCSims, my XDIM and YDIM settings are wrong, but when using a GEO-TIFF the compiler is overriding them from the FILE's geo-data instead of the INF, that is why I could originally only compile Geo-Tiffs.

EDIT:

Yup, that was it, obviously XDim/YDim are the gotchas for new people, I will fix it in my script for my .NET application (found a corrected formula), and now it works.
 
Last edited:
Hello:

I was asked by PM to offer some input on this thread; based on the time stamp for the last post above, and the time stamp on the PM, it would seem that the OP may be satisfied with his present understanding of how to create custom photo-real land class scenery via his proprietary scripted workflow.

However, IMHO, this thread merits a few additional comments. :)


Based on a brief review of the OP's posts here at FSDeveloper and the OP's prior posts at AVSIM alluded to by Lance, it is apparent that the OP is working on a scenery project for the Salt Lake City, Utah area in the USA:

http://forum.avsim.net/topic/426316-anyone-just-tired-of-this/page-2#entry2852990

http://forum.avsim.net/topic/422806-mse-2-swiss-first-impression/page-2#entry2853065


Based on statements in other posts in threads here and at AVSIM, the OP has been a FS enthusiast for more than 20 years, and the above referenced project is his first endeavor into making scenery now that he has seen the potential for enhancing the realism of scenery made possible on the MSFS platform since the release of FSX.


I believe it would be reasonable and appropriate to expect that members of the FSDeveloper community should try to offer a more friendly and supportive interaction with a fellow dedicated flight simmer and would-be scenery developer (whether freeware or payware). :(



That being said, I also believe that it would be reasonable and appropriate that the OP, as a relatively new member of the FSDeveloper community, recognize that other members of the FS community here and in other forums who take the time to reply with individualized suggestions, actually have objectively valid reasons based on their many years of experience, as to why they ask for more details of what workflow is being used by an OP in a troubleshooting thread. ;)


The same would-be helpers who may have little available time and energy to offer free assistance to an OP in a troubleshooting thread, may only be willing and/or able to answer questions and troubleshoot a workflow ...if the OP provides sufficient info to expedite the trouble shooting process.


So, if an OP wants to increase the likelihood of getting an expedited resolution to a FS development challenge in a troubleshooting thread, the OP, IMHO must be willing to be less secretive, and thus be prepared to ex: post an *.INF file or other FS development workflow details when the generous offer is made by experienced FS developers to offer individual troubleshooting assistance based on the OP disclosure of the suggested / requested info.

Without disclosure of the info suggested / requested in a troubleshooting thread, an OP may ultimately be calling for speculation on the part of a thread respondent as to what the OP is actually doing.

Replies based on speculation may ultimately prove to be a waste of one's time and energy that might also be un-helpful to the OP; furthermore, the OP's non-disclosure of such info deemed pertinent may discourage further replies by more experienced would-be helpers to that thread, and possibly other threads initiated by the OP in the future. :scratchch


I hope these observations might prove helpful to the OP in the future. :idea:


And I also hope that in the future, we will see more appropriate forum posting behavior by everyone, because I don't want to start wearing the same hip waders and body armor here at FSDeveloper ...that I am already compelled to wear in the forums over at AVSIM. :eek:

I believe it would be far better for the future of FSDeveloper that some thread respondents here (who seem to want to reply to troubleshooting threads by newbie OP's, but who also seem to have less patience with newbies in recent months and/or years), might consider refraining from posting inappropriate and personally insulting comments into threads by newbie OP's, as this reflects badly on- and has a degenerative effect on- the FS development community in general ...and fseveloper.com in particular. :mad:


Perhaps those here who are "long on experience", but (more recently) "short on patience", might consider doing a "missed approach" to circle the airport and not the drain, thereby allowing a troubleshooting thread by a newbie OP to evolve to the point that one might (later !) be better able to share in such threads, some valuable insights from their own experience which could help the OP (and other readers) ...so everyone's Flight Sim experience may become even more enjoyable ? :rolleyes:

GaryGB
 
Last edited:
Back
Top