Board index FlightGear Development Scenery

Using WED - Airport Sign Extractor

Questions and discussion about enhancing and populating the FlightGear world.

Re: Using WED - Airport Sign Extractor

Postby MickeySkooter » Mon Jul 09, 2018 8:43 pm

Yet another update coming, ASE v0.9.7.4 . Seems the SET PREFS hint box remained on even after the prefs were ok. The update seems to have corrected the issue, little more testing and will post the link here. Sorry with all the updates, I try to get them out as soon as possible but there is always something else I didn't see before. Minor tweaks here at there,

Appears that the executable is so much faster than the basic that it jumps the FileExist function. Once you have an airport and click monitor ufo you will know if the prefs are set correctly. If it can't find ufo-model-export it will prompt you to set the proper folders.

Here's the update V0.0.7.4
https://drive.google.com/file/d/1hoe8DW ... sp=sharing
MickeySkooter
 
Posts: 108
Joined: Tue Feb 20, 2018 4:33 am
Location: Montz, Louisiana
Callsign: NC3110
Version: 2017.3.1
OS: Windows 10

Re: Using WED - Airport Sign Extractor

Postby MickeySkooter » Tue Jul 10, 2018 2:47 pm

[ ] Considering a few new features. SURVEY, a two-point survey in multisign like a surveyor would do with a transit. Click two points with the UFO and export them to ASE. Click SURVEY and analyze the grade, distance and heading between point 1 and point 2. Printable results.
[-] An internal sign count within the default airport one-mile circle from the tower location found in the WED dat file.
[x] I see a couple tweaks I can do like the sign disappears when you turn off Monitor UFO.
[ ] Would like the UFO to bomb signs for runway mile markers.
[ ] Considering making the UFO fly to a point by making a flight plan.
Last edited by MickeySkooter on Sun Jul 15, 2018 12:49 am, edited 2 times in total.
MickeySkooter
 
Posts: 108
Joined: Tue Feb 20, 2018 4:33 am
Location: Montz, Louisiana
Callsign: NC3110
Version: 2017.3.1
OS: Windows 10

Re: Using WED - Airport Sign Extractor

Postby MickeySkooter » Wed Jul 11, 2018 5:52 am

ASE Blog ~ Screenshots and other information on ASE progress.
\https://www.mickeyskooter.com/440267917

Here are the complete folders, resources and update ASE 0.9.7.9

https://drive.google.com/file/d/1u6XYcT056gSKBbMcdHPMhfWulBpyBmHg/view?usp=sharing
Last edited by MickeySkooter on Sat Jul 28, 2018 3:25 pm, edited 5 times in total.
MickeySkooter
 
Posts: 108
Joined: Tue Feb 20, 2018 4:33 am
Location: Montz, Louisiana
Callsign: NC3110
Version: 2017.3.1
OS: Windows 10

Re: Using WED - Airport Sign Extractor

Postby MickeySkooter » Sat Jul 14, 2018 10:03 pm

07/14/2018 ~ Now working on sign count, from the airport tower. [checkRange] The distance calculation is a subroutine [calcDistance] which works fine when it's the working sign and ufo or stg data. The difference being I'm checking 1 sign over all signs in the obj editor for that airport. I run into a float overflow exception error. Thinking it would be simple: the number of signs within a mile divided by the number of signs at an airport x 100.

07/14/2018 ~ Fixed the issue with the sign count. I see a greater issue when
an airport has other airports within the same STG. The STG would have signs and other objects within the same file so updating would be tricky. Right now as the code exists, it would have to append its signs and models to all other airports in the STG. I went to an airport near KPHX, 1AZ2, which has no signs. The OBJ editor is empty, which would empty the STG file if updated.
MickeySkooter
 
Posts: 108
Joined: Tue Feb 20, 2018 4:33 am
Location: Montz, Louisiana
Callsign: NC3110
Version: 2017.3.1
OS: Windows 10

Re: Using WED - Airport Sign Extractor

Postby MickeySkooter » Sun Jul 15, 2018 1:24 pm

Back to search calculations between two GPS points. It appears I was calculating a cylinder not an ellipsoid with one distance factor, as the latitude moves up or down from the equator the distance factor should less until it becomes 0 at the poles. WGS84. I have to go back to portreekid's statement
" Your not placing signs in the real world" Add to the problem, east to west goes 0 to -180 and west to east, 0 to 180. Seems it should be converted to 0 to 360 with two hemispheres, north (, and south. Can't ignore elevation, could be measuring well under the airport with 0 elevations So what is the equator diameter in feet. What is the curve for latitude? It should progress from equator x 100% to equator x 0 % at the poles but, in a curve. Latitude starts 0 a the equator and 90 at the north pole (-90 the south pole) ?????
MickeySkooter
 
Posts: 108
Joined: Tue Feb 20, 2018 4:33 am
Location: Montz, Louisiana
Callsign: NC3110
Version: 2017.3.1
OS: Windows 10

Re: Using WED - Airport Sign Extractor

Postby MickeySkooter » Mon Jul 16, 2018 7:21 am

:shock:
Last edited by MickeySkooter on Sat Jul 28, 2018 3:27 pm, edited 2 times in total.
MickeySkooter
 
Posts: 108
Joined: Tue Feb 20, 2018 4:33 am
Location: Montz, Louisiana
Callsign: NC3110
Version: 2017.3.1
OS: Windows 10

Re: Using WED - Airport Sign Extractor

Postby MickeySkooter » Wed Jul 18, 2018 7:50 am

New app 'Object Extractor'' is available. Extracts OBJECT_SHARED models from the ufo-model-export file and places them in the clipboard. Just paste them at the end of the stg.file and save it. Then in FG reload scenery.
See blog on the 'update status' page.http://www.mickeyskooter.com works with Google Chrome browser.

https://drive.google.com/file/d/11xlrwVPBAj-FJu0DyLDt6OFPCbdtmEA0/view?usp=sharing
MickeySkooter
 
Posts: 108
Joined: Tue Feb 20, 2018 4:33 am
Location: Montz, Louisiana
Callsign: NC3110
Version: 2017.3.1
OS: Windows 10

Previous

Return to Scenery

Who is online

Users browsing this forum: No registered users and 5 guests