intersections - a way to locate and add new ones

Started by bill721, January 13, 2014, 08:10:59 PM

Previous topic - Next topic

bill721

Is there a location where I can find additional intersections that can be imported into Plan G?  I fly utilizing VATSIM with online flight controllers.  I find that they request certain departure intersections that I don't see in FSX or imported into Plan-G.  Is there another source  I can use to get the an updated list of intersections that I can import into Plan-G?  Presently I just use the lat long of the new intersection to estimate where ti's located and create a waypoint.

Thank you.  Plan G is a great program.

Bill

allardjd

I've got an ongoing project, posting add-on waypoints for FSX in the File Library at the Mutley's Hangar site.  Currently there are about 2,500 of them and I'm adding more every few days.  The download currently gives you a pair of bgl files to put into FSX and then Plan-G picks them up when you re-build the Plan-G databases.  As the number grows the number of bgls will increase as I have to keep them below 100K each to keep things working - but only two bgl files for now.

http://forum.mutleyshangar.com/

John Allard

bill721

#2
I finally have all my waypoints in FSX.  Now I need to get them built in plan-g.  How do I get plan-g to read a .bgl file in the FSX addon scenery folder and build it into the plan-g database?

tim arnot

Plan-G follows the standard afcad naming conventions, so make sure it starts with ap_, nv_ etc or ends with _ade etc

Tim. @TimArnot

bill721

#4
Tim thanks for the reply.  The file is compiled and I can't see how it is formatted.  The WorldINT.BGL file I added to the FSX scenery addon scenery library fixed it so I can see the waypoint WWTOO and many others on the FSX map but as I said not in either NEXT or Plan-G. 

When building the database Plan-G will read scenery files in the FSX addon scenery folder if data is formatted properly correct? 

Thanks as always...

Bill

bill721

Update...... I have it fixed.  I worked with the owner of the navdata and he suggested that I change the file name and that fixed it.....

I changed WorldINT.BGL  to APWorldINT.BGL and the file was read.

It took some work and multiple post to get all the navdata there but success.......

Tim again...thanks so much for your help.