Valid 21 APR 2022 00:00 UTC – 18 MAY 2022 23:59 UTC
PACKAGE contains digital obstacle data (.csv format): Area 1 obstacle data set; Area 2 obstacle data set containing only data on obstacles penetrating Obstacle Limitation Surfaces (OLS). [CRC32: 09434187 | DM5: e5085f73387408636d9685e96e722b40]
Additional details are available in Data Product Specification in the table below.
Effective date |
Data
Product Specification |
Area 1 Obstacle Data Set Archive |
Area 2 Obstacle Data Set Archive |
||||||||||||||
E P B Y |
E P G D |
E P K K |
E P K T |
E P L B |
E P L L |
E P M O |
E P P O |
E P R A |
E P R Z |
E P S C |
E P S Y |
E P W A |
E P W R |
E P Z G |
|||
19.05.2022 | DPS (v 1.1) | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
21.04.2022 | DPS (v 1.0) | 250 | - | - | - | - | - | - | - | - | - | - | - | - | 250 | - | - |
24.03.2022 | DPS (v 1.0) | 249 | - | - | - | - | - | - | - | - | - | - | - | - | 249 | - | - |
24.02.2022 | DPS (v 1.0) | 248 | - | - | - | - | - | - | - | 248 | - | - | - | - | - | - | - |
27.01.2022 | DPS (v 1.0) | 247 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
02.12.2021 | - | 246 | - | - | 246 | - | - | 246 | - | - | - | 246 | - | - | 246 | - | - |
04.11.2021 | - | 245 | - | - | - | - | - | - | - | - | - | - | - | - | 245 | 245 | 245 |
07.10.2021 | - | 244 | - | - | - | - | - | - | - | - | - | 244 | 244 | 244 | - | - | - |
09.09.2021 | - | 243 | - | - | - | - | - | - | - | 243 | 243 | - | - | - | - | - | - |
12.08.2021 | - | 242 | 242 | 242 | 242 | - | 242 | 242 | - | - | - | - | - | - | - | - | - |
15.07.2021 | - | 241 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
17.06.2021 | - | 240 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
20.05.2021 | - | 239 | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
- | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - | - |
Older data | - | 238 | - | - | - | 223 | - | - | 233 | - | - | - | - | - | - | - | - |
— AREA 1 —
AIRAC 19.05.2022 – NIL
AIRAC 21.04.2022 – CRC32: F16EA272 MD5: 915fe15fc061cd9415f6895825af4124
AIRAC 24.03.2022 – CRC32: 98CD506B MD5: a030215faded7c2696f4806e85e9bd35
AIRAC 24.02.2022 – CRC32: E0F80C74 MD5: 8524d9564e1cee49deba9cd5a370868d
AIRAC 27.01.2022 – CRC32: FB0C45E5 MD5: daaaa90aa4610e183d2e8a46790fc9a4
AIRAC 02.12.2021 – CRC32: 0B06548A MD5: 64db6eee3f08a3ce94e5148fe144c91d
AIRAC 04.11.2021 – CRC32: 9E8CE6B4 MD5: 6ef80d48ceedee6a29d925c6a8b5e729
AIRAC 07.10.2021 – CRC32: F239B903 MD5: bc7e80d892bf027c832e1b3e7f2dd0dd
AIRAC 09.09.2021 – CRC32: 0696E8D4 MD5: ce027380bf9dce31a404053dd01a2b61
AIRAC 12.08.2021 – CRC32: 5E647872 MD5: 6c9ba4d042f80569927ad8087fb2dce9
AIRAC 15.07.2021 – CRC32: EA9C8AB9 MD5: be8438da6f6197907b4a20857e16defd
AIRAC 17.06.2021 – CRC32: E0A891FA MD5: 9a68ad38cf460499fd2336ddb0c741ac
AIRAC 20.05.2021 – CRC32: 9FEFE71B MD5: 3fc64542ebd7e154b817a9d63972dd5f
AIRAC 22.04.2021 – CRC32: 6552C244 MD5: ecd0d385b584384c84c86f72cc305213
AIRAC 25.03.2021 – CRC32: DE2E376A MD5: 5a496608d59c82f4118213370e51aa32
— AREA 2 EPBY —
AIRAC 12.08.2021 – CRC32: 932C9A9D MD5: 4f7c28d0f822a29520e3fbdff57c7177
— AREA 2 EPGD —
AIRAC 12.08.2021 – CRC32: 8E3570D7 MD5: 0253e38ff7b911a159328aff176d7106
— AREA 2 EPKK —
AIRAC 02.12.2021 – CRC32: 93F14488 MD5: 14517f26ca53807f80c6e17f30bfc55a
AIRAC 12.08.2021 – CRC32: 934CD3FD MD5: 45a97ea2730c2d772cb295af04385e6f
— AREA 2 EPKT —
AIRAC 30.01.2020 – CRC32: F7882931 MD5: 8dc9f46de896d54cac160bfe27a0eb92
— AREA 2 EPLB —
AIRAC 12.08.2021 – CRC32: 1AB1308E MD5: ec55cf5eade82dfab8d418a81c90aad3
— AREA 2 EPLL —
AIRAC 02.12.2021 – CRC32: 81088746 MD5: 3f0d28895a46e4dcfc151ccb7b86e18e
AIRAC 12.08.2021 – CRC32: 3CC85098 MD5: 64f71bf51959566e4356494e20f48fc6
— AREA 2 EPMO —
AIRAC 05.11.2020 – CRC32: 70679756 MD5: d354961af8f236aab5ee99fc8aa12867
— AREA 2 EPPO —
AIRAC 24.02.2022 – CRC32: BEBCA452 MD5: a5ed44bde9abea34dea64f3aa782f4dd
AIRAC 09.09.2021 – CRC32: B34105E8 MD5: f223a4bff7573edfe711fcc88e50dfd4
— AREA 2 EPRA —
AIRAC 09.09.2021 – CRC32: 730D24B6 MD5: 0a06372c37c6d61aeab640314897bdd0
— AREA 2 EPRZ —
AIRAC 02.12.2021 – CRC32: E9604223 MD5: c4a77b8ec690823c66a0d942f5936df1
AIRAC 07.10.2021 – CRC32: 2C832D8A MD5: a2bc51dbd50bdc8cfa5495c0c3b380a1
— AREA 2 EPSC —
AIRAC 07.10.2021 – CRC32: 73FEECFF MD5: 7ec36277f9d7db9071051905cc77e665
— AREA 2 EPSY —
AIRAC 07.10.2021 – CRC32: CB7801A9 MD5: 31ec91350caec39e2c0450b5720cfb59
— AREA 2 EPWA —
AIRAC 21.04.2022 – CRC32: 204BC036 MD5: 3261fb39c8463193ed1d3550135fc6a9
AIRAC 24.03.2022 – CRC32: 06C111DC MD5: baad4d367468309b6412c93720b3eb29
AIRAC 02.12.2021 – CRC32: 2E3B9C24 MD5: abfba2fb8c57473f8d82569b1d2888ea
AIRAC 04.11.2021 – CRC32: DCD6E01F MD5: 896886875ce1be85e06477fc0e8f4632
— AREA 2 EPWR —
AIRAC 04.11.2021 – CRC32: D22066B2 MD5: d620a6c09b66912e934f2bad0b8ba91a
— AREA 2 EPZG —
AIRAC 04.11.2021 – CRC32: 77269F5B MD5: 3c58187139ee27df84cb37450061b9da
Archival Area 1 and Area 2 Obstacle Data Sets may be obtained by sending a request by e-mail to ais.poland@pansa.pl
Should you have any questions, doubts or sugestions do not hesitate to e-mail us at: ais.poland@pansa.pl
Please read the disclaimer available in the “Disclaimer” tab.
Area 1 Obstacle Data Set
CAUTION: The obstacle data set is made available on the terms specified in the “Legal protection of AIS publications” tab.
The area of coverage of the data set is Area 1 according to ICAO Annex 15, that is the whole territory of Poland.
The source of obstacle data within the territory of the Republic of Poland is the Civil Aviation Authority. This is stated at the level of a single data record.
The originator of obstacle data within the territory of the Republic of Poland is either a certified surveyor for as-built measurements or the obstacle owner for design data. This is stated at the level of a single data record.
The Area 1 obstacle data set has been developed on the basis of all en-route obstacles reported to the AIS and published in AIP POLAND in ENR 5.4. That being so, AIS POLAND cannot guarantee that the data set includes all existing aeronautical obstacles equal to or higher than 100 m above ground level within the EPWW FIR. – if the end-user wishes to use the data, the end-user assumes liability for its use.
The data set is delivered in a .csv format and will be updated in accordance with the AIRAC cycle – information on obstacles erected within the AIRAC cycle and information about obstacle lighting failures will be published by NOTAM.
WGS-84 is used as a horizontal reference system for the obstacle data. This is stated at the level of a single data record.
The vertical reference frame for the obstacle data is Kronstadt-86. The vertical reference frame used is stated at the level of a single data record.
The Area 1 obstacle digital data set does not contain the required obstacle marking and horizontal extent data for all records. Furthermore, there is no data available about the type and color of obstacle lighting.
Area 2 Obstacle Data Set – contains only obstacles penetrating the obstacle limitation surfaces (OLS)
CAUTION: The obstacle data set is made available on the terms specified in the “Legal protection of AIS publications” tab.
The area of coverage of the aerodrome obstacle data set is an area bounded by the lateral extent of the aerodrome obstacle limitation surfaces, as defined in the Regulation of the Minister of Infrastructure of 12 January 2021 on aviation obstacles, obstacle limitation surfaces and devices of a hazardous nature.
The Area 2 obstacle data set contains only obstacles that penetrate the obstacle limitation surfaces (OLS).
The source of the obstacle data within the territory of the Republic of Poland is the Civil Aviation Authority. This is determined at the level of a single data record.
The originator of obstacle data within the territory of the Republic of Poland is either a certified surveyor for as-built measurements or the obstacle owner for design data. This is stated at the level of a single data record.
The Area 2 obstacle data set has been developed on the basis of all aeronautical obstacles reported to the AIS and published in AIP POLAND in AD 2.10. That being so, AIS POLAND cannot guarantee that the data set includes all existing aerodrome obstacles – if the end-user wishes to use the data, the end-user assumes liability for its use.
The aerodrome obstacles data set is delivered in a .csv format and will be updated in accordance with the AIRAC cycle – information on obstacles erected within the AIRAC cycle and information about obstacle lighting failures will be published by NOTAM.
WGS-84 is used as a horizontal reference system for the obstacle data. This is stated at the level of a single data record.
The vertical reference frame for the obstacle data is Kronstadt-86. The vertical reference frame used is stated at the level of a single data record.
The aerodrome obstacles data set does not include horizontal extent as one of the required attributes for most records. Furthermore, there is no data available about the type and color of obstacle lighting.
Polska Agencja Żeglugi Powietrznej
ul. Wieżowa 8, 02-147 Warsaw
Informacje kontaktowe:
e-mail: info@pansa.pl
tel.: + 48 (22) 574 57 06
We firmly believe that the internet should be available and accessible to anyone, and are committed to providing a website that is accessible to the widest possible audience, regardless of circumstance and ability.
To fulfill this, we aim to adhere as strictly as possible to the World Wide Web Consortium’s (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1) at the AA level. These guidelines explain how to make web content accessible to people with a wide array of disabilities. Complying with those guidelines helps us ensure that the website is accessible to all people: blind people, people with motor impairments, visual impairment, cognitive disabilities, and more.
This website utilizes various technologies that are meant to make it as accessible as possible at all times. We utilize an accessibility interface that allows persons with specific disabilities to adjust the website’s UI (user interface) and design it to their personal needs.
Additionally, the website utilizes an AI-based application that runs in the background and optimizes its accessibility level constantly. This application remediates the website’s HTML, adapts Its functionality and behavior for screen-readers used by the blind users, and for keyboard functions used by individuals with motor impairments.
If you’ve found a malfunction or have ideas for improvement, we’ll be happy to hear from you. You can reach out to the website’s operators by using the following email
Our website implements the ARIA attributes (Accessible Rich Internet Applications) technique, alongside various different behavioral changes, to ensure blind users visiting with screen-readers are able to read, comprehend, and enjoy the website’s functions. As soon as a user with a screen-reader enters your site, they immediately receive a prompt to enter the Screen-Reader Profile so they can browse and operate your site effectively. Here’s how our website covers some of the most important screen-reader requirements, alongside console screenshots of code examples:
Screen-reader optimization: we run a background process that learns the website’s components from top to bottom, to ensure ongoing compliance even when updating the website. In this process, we provide screen-readers with meaningful data using the ARIA set of attributes. For example, we provide accurate form labels; descriptions for actionable icons (social media icons, search icons, cart icons, etc.); validation guidance for form inputs; element roles such as buttons, menus, modal dialogues (popups), and others. Additionally, the background process scans all of the website’s images and provides an accurate and meaningful image-object-recognition-based description as an ALT (alternate text) tag for images that are not described. It will also extract texts that are embedded within the image, using an OCR (optical character recognition) technology. To turn on screen-reader adjustments at any time, users need only to press the Alt+1 keyboard combination. Screen-reader users also get automatic announcements to turn the Screen-reader mode on as soon as they enter the website.
These adjustments are compatible with all popular screen readers, including JAWS and NVDA.
Keyboard navigation optimization: The background process also adjusts the website’s HTML, and adds various behaviors using JavaScript code to make the website operable by the keyboard. This includes the ability to navigate the website using the Tab and Shift+Tab keys, operate dropdowns with the arrow keys, close them with Esc, trigger buttons and links using the Enter key, navigate between radio and checkbox elements using the arrow keys, and fill them in with the Spacebar or Enter key.Additionally, keyboard users will find quick-navigation and content-skip menus, available at any time by clicking Alt+1, or as the first elements of the site while navigating with the keyboard. The background process also handles triggered popups by moving the keyboard focus towards them as soon as they appear, and not allow the focus drift outside of it.
Users can also use shortcuts such as “M” (menus), “H” (headings), “F” (forms), “B” (buttons), and “G” (graphics) to jump to specific elements.
We aim to support the widest array of browsers and assistive technologies as possible, so our users can choose the best fitting tools for them, with as few limitations as possible. Therefore, we have worked very hard to be able to support all major systems that comprise over 95% of the user market share including Google Chrome, Mozilla Firefox, Apple Safari, Opera and Microsoft Edge, JAWS and NVDA (screen readers), both for Windows and for MAC users.
Despite our very best efforts to allow anybody to adjust the website to their needs, there may still be pages or sections that are not fully accessible, are in the process of becoming accessible, or are lacking an adequate technological solution to make them accessible. Still, we are continually improving our accessibility, adding, updating and improving its options and features, and developing and adopting new technologies. All this is meant to reach the optimal level of accessibility, following technological advancements. For any assistance, please reach out to
Our website uses cookies and thereby collects information about your visit to improve our website (by analyzing), show you Social Media content and relevant advertisements. Please see our page for furher details or agree by clicking the 'Accept' button.
Below you can choose which kind of cookies you allow on this website. Click on the "Save cookie settings" button to apply your choice.
FunctionalOur website uses functional cookies. These cookies are necessary to let our website work.
AnalyticalOur website uses analytical cookies to make it possible to analyze our website and optimize for the purpose of a.o. the usability.
Social mediaOur website places social media cookies to show you 3rd party content like YouTube and FaceBook. These cookies may track your personal data.
AdvertisingOur website places advertising cookies to show you 3rd party advertisements based on your interests. These cookies may track your personal data.
OtherOur website places 3rd party cookies from other 3rd party services which aren't Analytical, Social media or Advertising.
This content is blocked. Accept cookies within the '%CC%' category to view this content.