AeroScenery Beta - Help With Testing Required

    Quote from Ian C

    Hi Nick

    Many thanks for all the work you're doing. AeroScenery is far more user-friendly than FSET - and about twice as quick by my reckoning.

    I have a spreadsheet that calculates lat-lon co-ordinates from tile numbers. It will also tell you which tile you are in if you input co-ordinates. I don't know whether that was the kind of thing you meant? It originally came from Rodeo - though I have modified it a bit myself.

    Cheers

    Ian

    I used this spreadsheet as my reference:

    Image tile coordinates

    If yours is different to that, send it over so I can compare numbers and formulae and figure out what's going wrong.

    Thanks.

    AeroScenery - Easily create photoreal scenery for Aerofly

    Hi Nick

    I am experiencing some unusual tile "dropouts" with AeroScenery images

    The left stitched image was downloaded yesterday from G and the right image was from today's retry.

    The dropouts are 256x256 pixels. Looking at the dropouts in detail

    they appear to be the same tile from a different dataset rather than a fetch failure.

    At first I thought the dataset had been prepared by G with substitutions for problem tiles.

    But if the dropout tiles vary from run to run is there somehow a runtime selection of dataset version per tile??

    Has anyone else experienced this?

    cheers

    Stu

    PS

    Have downloaded several tiles since then without any issue.

    G just having a bad day ??

    i7-6700K CPU @ 4.00GHz | ASUS Z170-A | 16Gb DDR4 | Samsung SSD 950 PRO NVME M.2 256GB | Samsung SSD 850 EVO 1TB | GeForce GTX 1080 Ti on GP102-A GPU | Oculus CV1 | Windows 10

    Edited once, last by lenidcamper: update (November 4, 2018 at 11:16 PM).

    Quote from lenidcamper

    I am experiencing some unusual tile "dropouts" with AeroScenery images

    I've not experienced this, but Google does whatever it can to stop people bulk downloading map tiles. AeroScenery makes itself appear as a regular browser and introduces a variable delay to try to combat this.

    Either this is part of Google's rate limiting / bulk download prevention strategy or just that you're randomly being pushed to a server that's serving up older map tiles.

    AeroScenery uses the following Google Maps url template.

    http://mt1.google.com/vt/lyrs=s&x={0}&y={1}&z={2}

    In the next version I'll make this configurable.

    mt0.google.com and mts0.google.com also exist which might have given different results here.

    AeroScenery - Easily create photoreal scenery for Aerofly

    Nick,

    Speaking of the "next version" . . .

    I would really appreciate a couple of more size choices. Especially, the one that is 4 times larger than your Small (grid 13). Not sure which way the numbers go. But, between the Small and Large.

    I am also looking forward to see your magic with the USGS. Some of the images are staggeringly beautiful - almost like a photo.

    Is there some method of editing these images prior to GeoCruching without have to edit several hundred small files? The water in the Puget Sound area is a real mess, both the deep water which may be 50% of a grid 9 tile and also around most of the smaller islands. I started trying to clean them up, but there are so many, I would probably lose interest in the area before I could finish.

    Regards,

    Ray

    Quote from Jetjockey10

    Is there some method of editing these images prior to GeoCruching without have to edit several hundred small files? The water in the Puget Sound area is a real mess, both the deep water which may be 50% of a grid 9 tile and also around most of the smaller islands. I started trying to clean them up, but there are so many, I would probably lose interest in the area before I could finish.

    You need to be editing the files in the "stitched" folder. There should be a manageable number per level 9 square depending the image detail level. You're probably looking at all the 100s or 1000s of map image tiles.

    The stitched files are around 8000px square by default.

    Sadly I'm not getting much time for either AeroScenery or Aerofly at the moment. Hopefully soon though.

    AeroScenery - Easily create photoreal scenery for Aerofly

    Nick,

    I guess because I am choosing level zoom level 17 and 9 - 14, the number of stitched images is unmanageable for editing say half the tiles with semi-matching colors to overwrite the bright white tiles for the water. :/ Thanks.

    We have a saying that goes something like this. There are a few creative programmers that work for free, and there are a few programmers that are really good at what they do, but it is truly rare to find a really good, creative programmer that works for free. We will just have to wait until you have the time for the next version. :P

    Regards,

    Ray

    Quote from Jetjockey10

    I would really appreciate a couple of more size choices. Especially, the one that is 4 times larger than your Small (grid 13). Not sure which way the numbers go. But, between the Small and Large.

    Just to second that. I'm a bit unusual in that I cover my whole territory with level 15 tiles. (A level 10 area would be good for me.) The level 9 area is too big for level 15 processing, and levels 13 and 14 are too small unless some way is found of running geoconvert sequentially rather than simultaneously. (In that case I could have multiple (more than 6) small tiles selected - which would be a reasonable workaround.)

    Quote from nickhod

    ...

    The hex numbers are derived from the lat and lon, so those also being incorrect makes sense.

    ...

    Hey Nick, I could be wrong and just taking a wild guess here, but if you're calculating the filename hex from the lat and lon decimal degrees values that might be the problem. The size of the tiles in terms of degrees latitude are not uniform as you get further north or further south of the equator. For example (assuming my spreadsheet is correct), a level 9 tile is ~0.70 deg 'tall' at the equator, but only ~0.11 deg 'tall' at the north pole. If you've assumed uniform spacing and are converting from degrees to hex from that, it might explain the issue...?

    If you did port all that code from my excel sheet (ugh!), and this really is the problem, you can get the grid coord numbers directly from rows 26 & 27 and rows 46 & 47 in that spreadsheet on the 'DONT_EDIT' tab. They are the number of the tile before it is converted into lat and long decimal degrees. Note that I split them into NW corner and SE corner (because of the area expansion feature I had in that spreadsheet) so you may need to offset them by 1 before converting to hex.

    Quote from qwerty42

    Hey Nick, I could be wrong and just taking a wild guess here, but if you're calculating the filename hex from the lat and lon decimal degrees values that might be the problem. The size of the tiles in terms of degrees latitude are not uniform as you get further north or further south of the equator. For example (assuming my spreadsheet is correct), a level 9 tile is ~0.70 deg 'tall' at the equator, but only ~0.11 deg 'tall' at the north pole. If you've assumed uniform spacing and are converting from degrees to hex from that, it might explain the issue...?

    If you did port all that code from my excel sheet (ugh!), and this really is the problem, you can get the grid coord numbers directly from rows 26 & 27 and rows 46 & 47 in that spreadsheet on the 'DONT_EDIT' tab. They are the number of the tile before it is converted into lat and long decimal degrees. Note that I split them into NW corner and SE corner (because of the area expansion feature I had in that spreadsheet) so you may need to offset them by 1 before converting to hex.

    Thanks for the info. I haven't looked at this fully yet, but it's on my list before I release the next version.

    I'm either calculating the just the hex tile name wrong, or the hex tile name and the lat and lon wrong. I'll let you know what I find.

    AeroScenery - Easily create photoreal scenery for Aerofly

    Quote from nickhod

    Thanks for the info. I haven't looked at this fully yet, but it's on my list before I release the next version.

    I'm either calculating the just the hex tile name wrong, or the hex tile name and the lat and lon wrong. I'll let you know what I find.

    Thanks, curious to know what you figure out. I won't deny the possibility that there's an error in my spreadsheet, since it's an ugly translation of programming code into spreadsheet logic, but I have previously converted some pretty huge areas from levels 9 thru 15 using it and FSET and never noticed any tile offset problems between the various levels. I've also compared the coordinates my spreadsheet calculates to the level 9 coordinates that GeoConvertHelper calculates, and they've agreed to 12 decimal places (if you account for the .1 degree inward offset that GeoConvertHelper automatically adds in). It's not a guarantee it's right, but if it's not then I'd suspect it may be an issue with the original code snip Rodeo posted...

    question à Nickhod,

    si l'on a qu'une seule ou quelques images stitched modifiées existe-t-il une possibilité de relancer AeroScenery ou GeoConvert seul afin de créer le fichier ttc sans relancer l'ensemble du processus de la map entière ?

    Merci à vous.

    Cordialement.

    CPU Intel Core I7 6700 K @4.00 Ghz + BiQuiet Pure Rock - CM Asusteck MAXIMUS VIII RANGER - RAM GSkill Ripjaws4 DDR4 3000 16 GB - NVidia GeForce GTX 1060 3GB - 2x SSD Samsung 500 GB 850 EVO - DD WD 2 TO.

    Quote from dauphin20217

    question à Nickhod,

    si l'on a qu'une seule ou quelques images stitched modifiées existe-t-il une possibilité de relancer AeroScenery ou GeoConvert seul afin de créer le fichier ttc sans relancer l'ensemble du processus de la map entière ?

    Not via the UI...

    The tmc file in the stitched images directory defines a level 9 size area (if you're using level 9). When you run GeoConvert it will always use all the stitched images to generate all levels requested.

    However, you can make GeoConvert do what you want by editing the tmc file.

    You could specify the region that you've changed in the lat lon, then have it generate ttc files smaller than this size.

    You'd need to set masks to off if you tried this.

    May be more effort than just running it again though.

    AeroScenery - Easily create photoreal scenery for Aerofly

    Ok merci, et effectivement mieux vaudrait de simplement relancer le processus entier ... 2 heures.

    CPU Intel Core I7 6700 K @4.00 Ghz + BiQuiet Pure Rock - CM Asusteck MAXIMUS VIII RANGER - RAM GSkill Ripjaws4 DDR4 3000 16 GB - NVidia GeForce GTX 1060 3GB - 2x SSD Samsung 500 GB 850 EVO - DD WD 2 TO.

    I sometimes use AeroScenery to convert a level 9 tile area with tiles from levels 9 to 14. The whole process takes about 11 hours. What I have noticed, however, is that Geoconvert slows down with time - particularly as it processes the level 14 tiles. At the beginning it is producing several level 14 tiles per minute - towards the end it is producing them at a rate of about 1 per minute.

    I have no idea why this happens. Have other people found the same thing? If it is happening to others as well it has implications regarding the most time-efficient way to use AeroScenery. It seems that it would be better to process a lot of smaller areas rather than one big area? This is not convenient at the moment because Geoconvert doesn't process areas sequentially, but when that problem is overcome it might be something to bear in mind.

    Quote from Ian C

    I sometimes use AeroScenery to convert a level 9 tile area with tiles from levels 9 to 14. The whole process takes about 11 hours. What I have noticed, however, is that Geoconvert slows down with time - particularly as it processes the level 14 tiles. At the beginning it is producing several level 14 tiles per minute - towards the end it is producing them at a rate of about 1 per minute.

    I have no idea why this happens. Have other people found the same thing? If it is happening to others as well it has implications regarding the most time-efficient way to use AeroScenery. It seems that it would be better to process a lot of smaller areas rather than one big area? This is not convenient at the moment because Geoconvert doesn't process areas sequentially, but when that problem is overcome it might be something to bear in mind.

    I don't know all the factors that affect the speed, but I can prepare a level 9 tile w/ 9 - 14 in about 2 hours. 1,365 total tiles with 13 having 256 and 14 having 1024. You have to watch that GeoConvert doesn't start over and redo the same area and same tiles a couple of times. I check the tile count and when it reaches 1,365 I stop GeoConvert and copy the tiles over and start flying.

    Regards,

    Ray

    I should add that this is at Level 17, 1.1 m

    Quote from Ian C

    I sometimes use AeroScenery to convert a level 9 tile area with tiles from levels 9 to 14. The whole process takes about 11 hours. What I have noticed, however, is that Geoconvert slows down with time - particularly as it processes the level 14 tiles. At the beginning it is producing several level 14 tiles per minute - towards the end it is producing them at a rate of about 1 per minute.

    I have no idea why this happens. Have other people found the same thing? If it is happening to others as well it has implications regarding the most time-efficient way to use AeroScenery. It seems that it would be better to process a lot of smaller areas rather than one big area? This is not convenient at the moment because Geoconvert doesn't process areas sequentially, but when that problem is overcome it might be something to bear in mind.

    As Jetjockey10 said, watch that GeoConvert isn't starting over again. It seems to do this at random, but moving, resizing or minimising the GeoConvert window often seems to trigger it though.

    I try not to run concurrent GeoConvert instances (which will happen with AeroScenery 0.6 if you process multiple squares). Version AeroScenery 1.0 (coming this year) should provide a workround to run GeoConvert instances sequentially.

    GeoConvert definitely isn't the quickest, but 11 hours seems a lot.

    AeroScenery - Easily create photoreal scenery for Aerofly

    Thanks to all who have replied. I'm using zoom level 18 so that may be slowing things down a bit (though not on the download side of things, because that only takes a couple of hours).

    I'm fairly sure that GeoConvert isn't restarting - though I have encountered that problem in the past.

    If I only go up to level 13 (using zoom level 17) it only takes a couple of hours.

    I found that with 16 gig of memory more than 2 concurrent GeoConvert instances are thrashing away in the page file.

    So I doubt more than 2 instances are actually gaining any performance benefit over dual instances run sequentially.

    Eight concurrent instances eventually cause a pagefile crash.

    Hopefully v1.0 of AeroScenery will have some configuration for MaxConcurrentGeoConvert instances.

    /Stu

    i7-6700K CPU @ 4.00GHz | ASUS Z170-A | 16Gb DDR4 | Samsung SSD 950 PRO NVME M.2 256GB | Samsung SSD 850 EVO 1TB | GeForce GTX 1080 Ti on GP102-A GPU | Oculus CV1 | Windows 10

    Edited once, last by lenidcamper (November 28, 2018 at 5:19 PM).