EFB chart VFR format

[midlifeflyer]

Yes, that is my core point. Whether vector or raster, you are using a software viewer to display FAA data. Either presentation is equally valid for navigation purposes.

Definitely. One step further, until you get at least up to the level of Part 91, Subpart F (Large, turbine, fractional aircraft) there is no specific regulatory requirement for any "aeronautical charts." You see a requirement for charts for 91F, 91K, 121, 125, and 135 ops, but not for plain vanilla Part 91. The closest for Part 91 is the 91.103 requirement to "become familiar with all available information concerning that flight" as part of our planning.

 

[flyingron]

Google NASR. The FAA publishes all airspace information as ESRI shapefiles, which are vector maps.

No, they do not. NASR only distributes the controlled airspace boundaries as shapefiles.
The other info is a combination of csv and other text format.

 

[flyingron]

The files defining a vector map, OTOH, describe the features (airports, navaids, topographic features, etc., and their locations) in a database. The software developers writing the viewing software can choose how to display the information. The displayed map is created by the viewing software from the database.

A vector map gives you a bunch of lines to draw, with the exception of a few controlled airspace bondaries, the FAA does not produce stuff.
There's tons of other data (positions of various things: airports, navaids, obstructions, etc...). THIS IS NOT VECTOR DATA though you can massage it into a vector map. You could also turn it into a raster map (which is exactly how the FAA makes sectionals, they all start from USGS topo data and then get layered on with all the stuff the FAA feels important).

 

[Ed Haywood]

No, they do not. NASR only distributes the controlled airspace boundaries as shapefiles.

Please describe how uncontrolled airspace is mapped.

(positions of various things: airports, navaids, obstructions, etc...). THIS IS NOT VECTOR DATA though you can massage it into a vector map.

A point is by definition not a vector.

 

[flyingron]

Please describe how uncontrolled airspace is mapped.

I have no idea what point you're trying to make. The shapefiles give the boundaries of CONTROLLED airspaces as I stated. That's it.

A point is by definition not a vector.

Very good. But a point also is not representable. You can turn it into something on a raster or draw it with vectors. The representation of a VOR is not a point. The representation of an airport is not a point.

 

[Ed Haywood]

I have no idea what point you're trying to make. The shapefiles give the boundaries of CONTROLLED airspaces as I stated.

My point is, uncontrolled airspace is mapped by drawing the boundaries of controlled airspace. What remains is uncontrolled. Therefore the vector shapefile file portrays ALL airspace, as I stated.

 

[flyingron]

My point is, uncontrolled airspace is mapped by drawing the boundaries of controlled airspace. What remains is uncontrolled. Therefore the vector shapefile file portrays ALL airspace, as I stated.

I never said it didn't What I'm saying is that the controlled airspace boundaries are a tiny fragment of the data that NASR provides and that the various EFB providers roll into their vector maps.