Ability to remove TFR's that are not a factor

[preid]

I see two NEW stadium TFR's on my (non ads-b) displays now.
I am in Socal were Disney has one SFC-3000AGL and the two new ones I saw on my flight West of Burbank SFC-2000AGL or something.(staples and another stadium)
Is there a way to have the TFR's (which is great BTW) in the database files, go away, like airspace does, when 1000-2000 feet above that area?. I had a passenger insisting I fly around the red area, even though we were at 9500 feet and the TFR was not an issue to be concerned with.
Thank you!

 

[swatson999]

Might be easier to educate your "passenger" on TFRs and who is PIC

 

[preid]

You missed my point. TFR's are quite well understood, hence their insistence I go around the red area, except the area wasnt "HOT" nor was it ever a factor 7000 feet below me. I want a TFR to be alerting me when its a factor or a pilot is within the actual area. Another example- fires result in TFR's for firefighting up to 1000-2000 feet AGL, yet a pilot can overfly the area at 5000 feet and never be in that TFR. I am requesting that the area, if below a certain feet, just like Class B and every other class in SoCal is, be removed from the screen if it does not apply.
I think if the passenger wasnt a pilot and understood the significance of a TFR they would have been looking out the window

 

[Garrett]

I think the TFR's should stay as they are.(period)

 

[swatson999]

I think you missed *my* point...

I concur with Garrett...they're fine the way they are.

 

[dynonsupport]

I believe the TFR airspaces follow the same logic as normal airspace where you can tell SkyView to only show airspaces within X feet of your altitude. This filters a lot out.

The issue is that stadium TFR's are blanket TFR's for multiple points in the world and thus list distances from the surface to XXXX AGL, not to specific MSL altitudes. Thus, SkyView can't really do anything without getting super fancy and trying to determine where the highest ground point is under what might be hundreds of square miles for a large TFR. So for airspaces referenced to AGL, not MSL, we never filter these.

 

[preid]

Dynon- thank you for the response! What I was looking for.
Is there any chance of adding permanent TFR's to the database files? For example Beale (BAB) is a permanent TFR that appears to be "updated" weekly yet has been a TFR from 4100MSL-18K for years. (Sort of like the way Disney land is shown)
I would be happy to update a DFG or other myself if needed.
Thank you!