Home

Results 1 - 10 of 78,449 for terrain. Search took 2.528 seconds.  
Sort by date/Sort by relevance
Comoros   Population: 600,500 (2005); Terrain: volcanic islands; Coastline: 340 km 3. Guinea-Bissau Population: 1,600,000 (2005); Terrain: mostly low coastal plain; Coastline: 350 km 4. Maldives   Population: 329,200 (2005); Terrain: flat; Coastline: 644 km 5. Mauritius   Population: 1,200,000 (2005); Terrain: small coastal plain, central plateau; Coastline: 177 km 6. (...) Timor-Leste Population: 947,000 (2005); Terrain: mountainous; Coastline: 706 km 20. Tonga  Population: 114,689 (2006); Terrain: coral formation, volcanic; Coastline: 419 km 21.
Language:English
Score: 1005647.2 - https://www.un.org/esa/sustdev/sids/sidslist.htm
Data Source: un
OPERATIONAL REQUIREMENTS HTAWS equipment should provide Ground Proximity Warning System (GPWS), Forward Looking Terrain Avoidance (FLTA), and a display capability, which places an aircraft position symbol on a terrain and obstacle map and applies terrain display algorithms. (...) The HTAWS should integrate a terrain and obstacle database with GPS/GLONASS vertical and horizontal position to provide enhanced terrain and obstacle awareness. (...) HTAWS should provide flight crews with aural and visual alert aids aimed at preventing a Controlled Flight Into Terrain (CFIT) accident by providing increased terrain and obstacle awareness.
Language:English
Score: 979563.3 - https://www.un.org/Depts/ptd/p...S%20Specifications_UN_Rev3.pdf
Data Source: un
   ICAO Doc 9881 ‐ Guidelines for Electronic Terrain, Obstacle and Aerodrome  Mapping Information      1.  Introduction    1.1 According  to  Chapter  5  of  Annex  4,  paragraph  5.2.1,  as  from  12  November  2015,  Aerodrome Terrain and Obstacle Charts — ICAO (Electronic) shall be made available in whichever of the  following ways  is  appropriate  for  a  particular  chart  or  single  sheet  of  a  chart  series  for  aerodromes  regularly used by international civil aviation.    1.2 Chapter 10 of  ICAO Annex 15 specifies the areas for which terrain and obstacles chart  shall be available in electronic format.    1.3 The Roadmap for the transition from AIS to AIM stipulates,  in the step 13 and step 14,  inside of phase 2, the compilation and provision of terrain and obstacle data set.    1.4 ICAO Doc 9881 provides a guideline regarding the requirements that should be applied  along  the  data  chain  in  order  to  obtain  a  database  commensurate  with  the  criticality  of  the  final  application of the terrain and obstacle data sets.      (...) d) Brazil has an electronic terrain and obstacle data  implementation plan from e‐ TOD project, in accordance with the requirements set out in ICAO Annex 15 for  Area 2. 
Language:English
Score: 979396.7 - https://www.icao.int/NACC/Docu...017/PARAST28/PA-RAST28IP02.pdf
Data Source: un
INTRODUCTION This paper presents the plan for South Africa relating to the implementation of electronic Terrain and Obstacle Data (eTOD). Amendment 33 to ICAO Annex 15 (effective 12/07/2004) introduced requirements for States to ensure that electronic sets of Terrain and Obstacle Data (TOD) are available. (...) SACAA 14/10/2008 14/10/2008 See AP/008 AP/003 2 Terrain To be addressed at the SA eTOD WG meetings. (...) SA eTOD WG 18/11/2010 Next meeting on the 21st May 2009. AP/007 4 Terrain Terrain dataset available from and maintained by ACSA.
Language:English
Score: 978509 - https://www.icao.int/WACAF/Doc..._TF5/Docs/e-tod%20-%20ip-6.pdf
Data Source: un
IMPLEMENTATION OF ELECTRONIC TERRAIN AND OBSTACLE DATA (Presented by the Secretariat) SUMMARY This paper reviews requirements for the provision of electronic terrain and obstacle data (eTOD). (...) The increasing worldwide equipage of aircraft and air traffic control units with systems that make use of electronic terrain data requires standardization in the provision of supporting electronic terrain and obstacle data. Furthermore, as terrain information is increasingly finding its primary use in the cockpit, many other personnel involved with operations will benefit from the use of quality terrain and obstacle data.
Language:English
Score: 977861.3 - https://www.icao.int/WACAF/Doc...5/Docs/wp4%20ais%20maptf-5.doc
Data Source: un
PowerPoint Presentation OLS / ACI O L S S Y M P O S I U M 2 0 2 1 O F S / O E S a n d i t s R o l e i n T O D Terrain & Obstacle Database. Availability of updated obstacle and terrain data is key to the safety of flight operations Data is collected based on Annex 15 and Pans-Aerodromes provisions Aeronautical charts are produced in accordance with Annex 4 Terrain & Obstacle Database. Coverage areas have been specified by ICAO: Area 1: entire territory of a State Area 2: within the vicinity of an aerodrome Area 2a: rectangular area around a runway that comprises the runway strip plus any clearway that exists Area 2b: Area shaded blue Area 2c: Area shaded yellow Area 2d: Area shaded green Area 3: within the aerodrome Area 4: within the aerodrome Terrain & Obstacle Database. • With the introduction of OES into the OLS concept, it helps to: i) Define the areas within 2C & 2D where obstacle & terrain data are operationally significant. Terrain / Obstacle TOD Areas Annex 15 Area 1 Standard Area 2 Area 2a Standard Area 2b Standard Area 2c Recommendation Area 2d Recommendation Area 3 Recommendation Area 4 Standard Standard The area bounded by the lateral extent of the aerodrome obstacle limitation surfaces are contained in Area 2C Terrain & Obstacle Database. • The TOD surfaces act as triggers • The proposed OFS and OES will stil be mostly contained in Area 2C.
Language:English
Score: 967788.5 - https://www.icao.int/Meetings/...le_of%20OFS_and_OES_in_TOD.pdf
Data Source: un
A further step was taken with the development of GPWS with a forward looking terrain avoidance function, generally referred to as enhanced GPWS and known in the United States as Terrain Awareness and Warning System (TAWS). (...) The source and scope of the terrain, obstacle and airport data, and features such as the terrain clearance floor, the runway picker, and geometric altitude (where provided) should all be described. • Displays required to deliver GPWS outputs include a loudspeaker for voice announcements, visual alerts (typically amber and red lights), and a terrain awareness display (that may be combined with other displays). (...) (c) Use of Basic GPWS or Use of the Forward Looking Terrain Avoidance Function Only. Objective: To verify that a pilot understands what functionality will remain following loss of the GPWS or of the forward looking terrain avoidance function.
Language:English
Score: 965428.9 - https://www.icao.int/APAC/Meet...l%20-%20draft%20-%20130418.pdf
Data Source: un
To be able to provide reciprocity for calculations on propagation paths along sloping terrain, the profile used for further calculations is based on the connecting line between the terrain heights of the transmitter and the receiver location (normalized profile). (...) Correction factors for the terrain irregularity shall not be applied to sea-path propagation paths. For d < 10 km: No terrain irregularity is taken into account for distances shorter than 10 km.
Language:English
Score: 963013.5 - https://www.itu.int/en/ITU-D/P...0documents/HCM4A-E-Annex05.pdf
Data Source: un
A further step was taken with the development of GPWS with a forward looking terrain avoidance function, generally referred to as enhanced GPWS and known in the United States as Terrain Awareness and Warning System (TAWS). (...) The source and scope of the terrain, obstacle and airport data, and features such as the terrain clearance floor, the runway picker, and geometric altitude (where provided) should all be described. • Displays required to deliver GPWS outputs include a loudspeaker for voice announcements, visual alerts (typically amber and red lights), and a terrain awareness display (that may be combined with other displays). (...) (c) Use of Basic GPWS or Use of the Forward Looking Terrain Avoidance Function Only. Objective: To verify that a pilot understands what functionality will remain following loss of the GPWS or of the forward looking terrain avoidance function.
Language:English
Score: 957077.3 - https://www.icao.int/APAC/Meet...7-130502%20final%20-%20SIN.pdf
Data Source: un
Timeline Start End Remarks 2014 2015 2016 2017 2018 Phase II eAIP P-11 2014 2018 The target is to be implemented by 2018 Terrain A-1 P-13 2007 - Already Implemented Obstacle A-1 P-14 2017 2019 The target is to be implemented by 2019 Terrain A-4 P-13 2007 - Already Implemented Obstacle A-4 P-14 2017 2019 The target is to be implemented by 2019 Terrain A-2 P-13 2020 The target is to be implemented by 2020 Obstacle A-2 P-14 2020 The target is to be implemented by 2020 6AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 EGYPT National AIM Implementation Roadmap Phase/Step Step No. Timeline Start End Remarks 2014 2015 2016 2017 2018 Phase II Terrain A-3 P-13 2018 2019 The target is to be implemented by 2019 Obstacle A-3 P-14 2018 2019 The target is to be implemented by 2019 AD Mapping P-15 2019 2020 The target is to be implemented by 2020 Phase III Aeronautical data exchange P-09 2018 2020 Communication networks P-10 2005 2020 Aeronautical information briefing P-12 2001 2018 Training P-16 2005 2020 7AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 EGYPT National AIM Implementation Roadmap Phase/Step Step No. Timeline Start End Remarks 2014 2015 2016 2017 2018 Phase III Agreement with data originators P-18 2006 2018 Interoperability with meteorological products P-19 2017 2020 Electronic aeronautical charts P-20 2018 2020 Digital NOTAM P-21 2017 2020 8AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 Status of Egypt B0-DATM Implementation 9AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 Status of Egypt B0-DATM Implementation Provision of AIS/AIM products and services based on the Integrated Aeronautical Information Database (IAID) Elements Status Action Plan Remarks Integrated Aeronautical Information Database (IAID) FI - AIXM (+version) FI - version 4.5 – upgrading to version 5.1 by 2018 eAIP (IAID-based) PI To be completed by 2018 eAIP is provided in digital format - CD since 2006 NOTAM (IAID-based) FC - SNOWTAM (IAID-based) NC - PIB (IAID-based) FC - Charting (interoperable with IAID) NC To be completed by 2018 Procedure Design (interoperable with IAID) NI To be completed by 2018 ATS (interoperable with IAID) FI - 10AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 Status of Egypt B0-DATM Implementation Aeronautical Data Quality Elements Status Action Plan Remarks Quality Management System (QMS) FC - Formal agreement with originators PC To be completed by 2018 Digital data exchange with originators PI To be completed by 2018 Metadata FC - Data quality monitoring PC To be completed by 2018 Data integrity monitoring PC To be completed by 2018 AIRAC adherence FC - 11AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 Status of Egypt B0-DATM Implementation WGS-84 Elements Status Action Plan Remarks FIR/ENR FC ‐ Terminal FC ‐ AD FC ‐ Geoid Undulation (GUND) FC ‐ 12 AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 Status of Egypt B0-DATM Implementation electronic Terrain and Obstacle Datasets (eTOD) Elements Status Action Plan Remarks Area 1 Terrain FC - Area 1 Obstacles NC To be completed 2019 Area 4 Terrain FC - Area 4 Obstacles NC To be completed 2019 Area 2a Terrain PC To be completed 2020 HECA & HEBA Completed Area 2a Obstacles NC To be completed 2020 Area 2b Terrain PI To be completed 2020 HECA & HEBA Completed Area 2b Obstacles NI To be completed 2020 Area 2c Terrain PI To be completed 2020 HECA & HEBA Completed Area 2c Obstacles NI To be completed 2020 Area 2d Terrain PI To be completed 2020 HECA & HEBA Completed Area 2d Obstacles NI To be completed 2020 Area 3 Terrain NI To be completed 2019 Area 3 Obstacles NI To be completed 2019 AMDB NI To be completed 2020 13AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 B0 – DATM: Service Improvement through Digital Aeronautical Information Management Elements Applicability Status Action Plan/Timelines Remarks National AIM Roadmap Egypt Fully Implemented ‐ Updated Version by Nov 2016 AIXM Egypt Fully Implemented ‐ Current: version 4.5 upgrading to version 5.1 by 2018 eAIP Egypt Fully Implemented Fully Implementedby Dec 2018 QMS Egypt Fully Compliant - WGS-84 ENR AD TMA GUND Fully Compliant - eTOD Area 1 Terrain Area 1 Obstacle Area 4 Terrain Area 4 Obstacle Fully Compliant Fully Compliant Fully Compliant Fully Compliant Fully complaint by Dec 2019 Outlook 2020 (Status of B0-DATM by 2020) 14AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 Status of AIM Deficiencies AIM Deficiency Status Action Plan/Timelines Remarks Lack of the required Obstacle Datasets for eTOD Area 1 and Area 4 Not Completed Completed by Dec, 2019 Tender for the new system was completed and we are in phase of signing the contract with the supplier 15 Challenges AIM SG/3, Cairo, Egypt, 15‐18 MAY 2017 B0-DATM  eAIP (P-11): Software Provider insolvent issue.  P-19: Interoperability with different systems.  P-13, P-14: Funding issue.  Civil / Military Coordination.
Language:English
Score: 955664 - https://www.icao.int/MID/Docum...3-MIDAD%20TF4/PPT7%20Egypt.pdf
Data Source: un