georeferenced airport circuits

Important: These forums are for discussions between SkyDemon users. They are not routinely monitored by SkyDemon staff so any urgent issues should be sent directly to our Customer Support.

georeferenced airport circuits

Author	Message
Hans M.	Hans M. posted 5/6/2013 10:30:12 AM Topic Details Share Topic
Group: Forum Members Posts: 1, Visits: 6	One thing I miss almost daily when using SD are the airports traffic circuits. I know about your problems with public organizations as Skyguide. But there is another way to success: You already have your own vector based VFR airspace data. Why don’t you just integrate vector based traffic patterns of European airports? For example www.platzrunden.de has all European traffic patterns including approach sectors and entry circuits for Garmin GPS. There it’s very easy to join downwind, turn into base and final leg. You have to vectorize it only once because traffic patterns change rarely. For the SD customers it would be an appreciated added value to your great software! Thanks for your excellent product SD. I love it! Hans
	Reply Like 116
ckurz7000	ckurz7000 posted 5/6/2013 4:12:45 PM Post Details Share Post
Group: Forum Members Posts: 538, Visits: 2.2K	That would be great! -- Chris.
	Reply Like 97
Tim Dawson	Tim Dawson posted 5/8/2013 4:53:19 PM Post Details Share Post
Group: Forum Members Posts: 7.8K, Visits: 8.4K	Vectorised circuits would be a huge undertaking, with no clear path forward for maintaining them, and the addition of significant risk exposure when people start flying circuits "heads down" not looking where they are going because they want to follow the circuit on SkyDemon to ensure noise abatement etc. It's unlike we would invest in developing that feature.
	Reply Like 85
bharb	bharb posted 7/20/2013 3:25:47 PM Post Details Share Post
Group: Forum Members Posts: 26, Visits: 351	On my last flight I flew to a very small airfield where it was hard to navigate by landmarks. There we used Air Nav Pro with Austrian traffic pattern data from rogersdata.at to keep inside the traffic pattern and it worked great. And to be honest - I was more disturbed by searching for landmarks on the ground and comparing them to my chart than my Co, who followed the track on his tablet (we tried to answer exactly that question - what will be more safe, searching for landmarks or having a moving map with you). So, I understand that maintaining the traffic circuits would be a pain, but there are some commercial vendors of traffic patterns especially for Europe, like www.platzrunden.de, www.navidat.eu or rogersdata.at (which provides data for Air Nav Pro for example). In my opinion it would be great if you could negotiate another distribution option for those vendors, so both parties have the benefit and the users of SD get vectored traffic patterns (I am not involved in ANY of those commercial vendors!). Currently I use the custom data editor to insert traffic patterns of my destinations by myself by having them shown as "undefined airspace" - this works ok but is not really beautiful and of course a lot of work to get the coordinates of the turning points out from Jeppesen charts (via Google Earth and visual editing). A special custom data format for traffic patterns with courved edges and so on would be great. Maybe at least this could be implemented in one of the future SD versions. So, please rethink your opinion on traffic patterns in SD after reading above lines! Thanks, Bernhard.
	Reply Like 88
dixius	dixius posted 2/26/2014 12:29:20 PM Post Details Share Post
Group: Forum Members Posts: 1, Visits: 9	Hello, yes I follow the arguments told by Bernhard. It would be a pain to maintain the traffic circuit data for you. But it shoud be possible to build a interface for the airfield circuit data for example: (airtraffic.txt file) in OpenAir-Format Moenchsheide AC O AN 11/29 1650ft * UL * MOGAS AH 1650 ft AL 750 m UL MOGAS DP 50:30:27 N 007:15:46 E DP 50:30:35 N 007:16:47 E DP 50:31:18 N 007:16:56 E DP 50:31:34 N 007:14:10 E DP 50:30:37 N 007:13:57 E DP 50:30:31 N 007:15:02 E Aachen AC O AN 08/26 1500 ft * UL AH 1500 ftAL 520 m, UL DP 50:49:17 N 006:10:28 E DP 50:49:14 N 006:10:12 E DP 50:49:06 N 006:10:00 E DP 50:48:15 N 006:09:37 E DP 50:48:06 N 006:09:41 E DP 50:48:01 N 006:09:55 E DP 50:48:27 N 006:13:03 E DP 50:48:36 N 006:13:12 E DP 50:49:28 N 006:12:54 E DP 50:49:34 N 006:12:39 E DP 50:49:30 N 006:12:07 E Achmer AC O AN 07/25 AH 1000 ft AL 940 m DP 52:22:20 N 007:53:27 E DP 52:21:35 N 007:53:57 E DP 52:22:13 N 007:56:37 E DP 52:22:58 N 007:56:07 E ..... That are some selfmade airport circuits from germany in OpenAir-Format. Every user is responsible for correct data and maintanance of data. Only a interface and a description is nessesary. I think it is a possible solution for you and some pilots that are very interesstet for that. Tags air traffic Edited 2/26/2014 2:18:23 PM by dixius
	Reply Like 85
Tim Dawson	Tim Dawson posted 2/26/2014 3:00:55 PM Post Details Share Post
Group: Forum Members Posts: 7.8K, Visits: 8.4K	You can already define bits of airspace in SkyDemon using the Data Creator tool on a PC, you could always define a circuit as a piece of airspace. While we may at some point accept "official" circuit descriptions directly from airfield owners, I can't see us having a general purpose format for users to create their own. Most users would not be interested in fiddling around with things like this.
	Reply Like 88