search

ngageoint / hootenanny

Hootenanny conflates multiple maps into a single seamless map.
GNU General Public License v3.0
359 stars 74 forks source link

Area Apron(GB015) w/ Aerodrome Pavement Functional Status(SFS)=not Applicable(998) => SFS dropped #4712

Closed MikeTho16 closed 3 years ago

MikeTho16 commented 3 years ago

Describe the bug I am not sure how significant this is. I could not find anything in the TRD or the GAIT documentation as to whether this was part of a valid combination. SFS=998 may be required if Load-bearing Surface Type(RST) =Loose/Unpaved(2) or Grass/Sod(2).

Also Applies to

mattjdnv commented 3 years ago

Like in some of the other issues, we drop 998 values when translating to OSM since OSM generally doesn't store "negative" values.

Moving this to the "Things to think about" list until we figure out what to do.

mattjdnv commented 3 years ago

Digging further into the TRD and the other extraction guides, I'm not sure if there could be a case for giving an Apron/Stopway/Runway/Taxiway an SFS value of Not Applicable. The valid values are:

Unknown 0   The attribute value is unknown.
Fair    1   The condition is adequate for limited aircraft operations. ( It is capable of supporting 30 days of limited operations by the heaviest (highest Load Classification Number (LCN) or Aircraft Classification Number (ACN)) aircraft that can use the facility. )

Good    3   The condition is adequate for sustained aircraft operations. ( It will support 30 days of sustained operations by the heaviest (highest Load Classification Number (LCN) or Aircraft Classification Number (ACN)) aircraft that can use the facility. )

Poor    5   The condition is sufficient for only emergency aircraft operations. ( It will support only emergency or occasional operations by the heaviest (highest Load Classification Number (LCN) or Aircraft Classification Number (ACN)) aircraft that can use the facility. )

Not Applicable  998 There is no possible value in the attribute range that would be applicable. ( May occur when the attribute is not applicable to the feature type (for example: the Airfield Type attribute of a Settlement feature type). )

I can see tagging it with poor or fair if it is unpaved or grass but not Not Applicable.