|
ckurz7000
|
|
|
Group: Forum Members
Posts: 538,
Visits: 2.2K
|
If Track Waypoint were meant to replace the position report then the position report feature should be taken off the program. As long as it is here, it ought to be optimized to give us the functionality it purports to provide. As it stands now. It is often times useless because it references obscure little towns. In my opinion, it should only reference aeronautical features, period.
-- Chris.
|
|
|
|
|
Tony N
|
|
|
Group: Forum Members
Posts: 368,
Visits: 2.6K
|
I tried that suggestion (SD 3.6.2 on Samsung S3 - flying mode selected but on the ground) but couldn't get it to work. The displayed "position report" didn't change from the default.
Also, for me, too many "finger pressing" operations required while flying the aeroplane, pressing the PTS and trying to keep a good lookout.
Tony
|
|
|
|
|
Sky Painter
|
|
|
Group: Forum Members
Posts: 627,
Visits: 15K
|
+xBut Skydemon is there to make life (flying) easier, not more complicated! Track Waypoint is there for a purpose. What's complicated about a long tap on a navigational feature and selecting Track Waypoint. I use it frequently when talking to a LARS controller.
Mike _________________________________________ Samsung Galaxy Tab A8 – Android 11.0 & SD 4.2.2 Huawei P30 – Android 11.0 & SD 4.2.2
PC – Windows 10 (Home Ed) Version 22H2, Build 19045.6575, SD 4.2.2
|
|
|
|
|
efrenken
|
|
|
Group: Forum Members
Posts: 265,
Visits: 3.5K
|
But Skydemon is there to make life (flying) easier, not more complicated!
Eric
|
|
|
|
|
Sky Painter
|
|
|
Group: Forum Members
Posts: 627,
Visits: 15K
|
You could always use the Track Waypoint function in order to provide you with a more meaningful position report relative to a navigation feature of your choosing, especially when talking to a LARS controller.
Mike _________________________________________ Samsung Galaxy Tab A8 – Android 11.0 & SD 4.2.2 Huawei P30 – Android 11.0 & SD 4.2.2
PC – Windows 10 (Home Ed) Version 22H2, Build 19045.6575, SD 4.2.2
|
|
|
|
|
Tony N
|
|
|
Group: Forum Members
Posts: 368,
Visits: 2.6K
|
I had a similar experience in UK. I was asked by Farnborough LARS as to my position and, from SD, was just about to tell him I was x NM from some town I had never heard of and, if I recall, didn't even appear on my CAA ICAO 1:500,000 chart.
I don't know how you would chose what to display for real-time position information but I think aeronautical features or very large towns would be best for ATC recognition/understanding purposes.
Tony
|
|
|
|
|
efrenken
|
|
|
Group: Forum Members
Posts: 265,
Visits: 3.5K
|
Tim,
Just checked and found about 10 'towns' in Germany in the nearer area I'm living in shown at a scale of 750k. All do have a population between < 1,000 and 6,000 and no controller would ever have heard about them. These are situated in a small part of Germany, so I estimate there are more than 300 of these throughout Germany, which is more than a few.
I sometimes had a problem reporting my position, because the position report at the top of the window was referencing to a town, which even I never had heard of, although I live in that area.
Eric
|
|
|
|
|
Tim Dawson
|
|
|
Group: Forum Members
Posts: 8.2K,
Visits: 9.7K
|
Yeah, but in most countries, the data is perfectly reliable. I'm not about to switch off the report-relative-to-town feature (which is used extensively) because a few small towns in certain countries are incorrectly displayed at large scales. That is not the solution.
|
|
|
|
|
ckurz7000
|
|
|
Group: Forum Members
Posts: 538,
Visits: 2.2K
|
+xHi Pascal, hopefully the solution I alluded to above will resolve this. Our alternate data does appear to correctly break down populations. If the next chart update still has issues in this regard, we will have to schedule some development time to investigate your suggestion. Chris, the position report is already driven from the zoom factor threshold associated with towns, which is ultimately derived from population data. I therefore believe that the solution I mentioned above will stop what you're seeing from happening in Switzerland. If you have a specific example elsewhere I'll be happy to look into it, but we already make that position report only look at towns which are visible at 1:750k scale. Tim, I set the scal to 750k and checked which towns were still visible. I found many small towns with populations around 2.000-3.000 which were still visible at that scale. An example: Pöggstall (pop. 2.461 as of Jan 1, 2016), which is located 6 nm south of LOAA. No controller would ever have heard of that unless he grew up in that area. It seems that you have unreliable census data on municipalities. Therefore it might be better to rely only on aeronautical features. -- Chris.
|
|
|
|
|
psuter
|
|
|
Group: Forum Members
Posts: 52,
Visits: 31
|
+xHi Pascal, hopefully the solution I alluded to above will resolve this. Our alternate data does appear to correctly break down populations. If the next chart update still has issues in this regard, we will have to schedule some development time to investigate your suggestion. Chris, the position report is already driven from the zoom factor threshold associated with towns, which is ultimately derived from population data. I therefore believe that the solution I mentioned above will stop what you're seeing from happening in Switzerland. If you have a specific example elsewhere I'll be happy to look into it, but we already make that position report only look at towns which are visible at 1:750k scale. Thanks Tim for taking care of this so quickly, i'll check after the next update and give you some feedbak.
|
|
|
|