Thanks for testing! I am not sure, what exactly you are referring to. If I fly down the ILS localizer and G/S I end exactly over the runway threshold. Anyways, I would not know how to fix the ILS position.
04R ILS is misplaced when using XP 11.20's default version, which I think is ID 56281. I then loaded LIPZ ID 60430 and did another approach. This time the ILS localizer was in the correct place. Hope this helps.
flyingpauls
commented
in reference to scenery pack
75698on April 1, 2020 7:45 AM
This was rejected because it does not agree with the current aerial images. It is maybe the best to wait until Google earth is updated.
The runways have been completely repaved, some changes occurred also in shape of tarmac on 04R startint point south west of the main apt.
The bing source is very recent, according to my information
Works on 04L has been completed and now 04L has the same length of rwy 04R. Runway must be made the same length of the 04R as it's used as main taxiway
Yes, I know and I already did that. It is uploaded to the gateway but got rejected. I intended to wait until Google or ESRI images are up to date. Unfortunately, you cannot download it yet. But I think you can import it to WED.
Julian agreed to recheck the airport. Once, it is approved, fix it if it is still not close to the current real state. And, by the way, if you have images, please share them. It would be most welcome.
Bing has updated status of the runway 04L where you can see the runway is already active as main taxiway for the full length. I've a good friend that works in LIPZ airport as manager (i live 5km north of the apt) and i'm collecting info. Unfortunately we cannot take shots of the airport due to the COVID lockdown that prevent us from moving without a "valid" reason.
I'll keep you informed about runway status and marking positions
I collected some more notes. The TOTAL LENGTH of the usable 04L runway is still UNCHANGED and the runway will not be extended, for now. The extension is considered as a TAXIWAY. There is another junction that connects 22R with 22L, you can see it on charts.
At least, taxiway G is what should be F. And the signs that indicate stand numbers (those that are "in the terminal", in front of the aircraft parked) not correspond with those that are on the floor. This are the correct ones. For example, I was on gate 324.
I can confirm the issue - however runway 04L is not used as a runway anymore, so the issue is not pressing. Extending the airport boundary or placing an exclusion zone should get rid of the trees which are not present in real life.
To the moderator: Please ignore this upload. Use the improved version 60368. Thank you for your work!
ILS is about 20m to the left
flyingpauls May 17, 2018 3:44 PM
Thanks for testing! I am not sure, what exactly you are referring to. If I fly down the ILS localizer and G/S I end exactly over the runway threshold. Anyways, I would not know how to fix the ILS position.
flyingpauls May 17, 2018 4:38 PM
I also did an autoland with the A320. No problem.
dbrooke May 17, 2018 4:41 PM
I came in with the FF A320, with the localiser exactly lined up on the PFD, but was half on the grass.
flyingpauls May 17, 2018 8:40 PM
My Autolanding was also on the FF. Strange. We need to find out what is going on here. Do you use XP 11?
taxtax May 20, 2018 6:00 PM
04R ILS is misplaced when using XP 11.20's default version, which I think is ID 56281. I then loaded LIPZ ID 60430 and did another approach. This time the ILS localizer was in the correct place. Hope this helps.
This was rejected because it does not agree with the current aerial images. It is maybe the best to wait until Google earth is updated.
Fire brigade buildings in front of the parking area have been removed 2 years ago. There is a new taxiway now in this place (Q)
flyingpauls April 23, 2020 7:34 PM
I changed that already and uploaded. It got rejected. The reason is not clear, however.
shezan74 April 24, 2020 8:31 AM
I confirm the taxiway is present and fully operative. Bing maps recently updated reports the status:
https://www.bing.com/maps?osid=627ed8f8-6624-4e3a-ab8e-9a8ba21f2ffd&cp=45.50541~12.341651&lvl=16&style=h&v=2&sV=2&form=S00027
shezan74 April 24, 2020 8:34 AM
The runways have been completely repaved, some changes occurred also in shape of tarmac on 04R startint point south west of the main apt.
The bing source is very recent, according to my information
flyingpauls April 28, 2020 7:33 AM
You can download my new version from the gateway and check. Please tell me about any problems.
Jan Vogel March 8, 2021 3:16 PM
This should be fixed by now, we have had some new uploads/improvements to this airport since then.
Works on 04L has been completed and now 04L has the same length of rwy 04R. Runway must be made the same length of the 04R as it's used as main taxiway
flyingpauls April 23, 2020 7:26 PM
Yes, I know and I already did that. It is uploaded to the gateway but got rejected. I intended to wait until Google or ESRI images are up to date. Unfortunately, you cannot download it yet. But I think you can import it to WED.
flyingpauls April 24, 2020 5:35 AM
Julian agreed to recheck the airport. Once, it is approved, fix it if it is still not close to the current real state. And, by the way, if you have images, please share them. It would be most welcome.
shezan74 April 24, 2020 8:30 AM
https://www.bing.com/maps?osid=2e4f7ed5-1798-4561-b7b9-9001c556af25&cp=45.514329~12.366816&lvl=16&style=h&v=2&sV=2&form=S00027
Bing has updated status of the runway 04L where you can see the runway is already active as main taxiway for the full length. I've a good friend that works in LIPZ airport as manager (i live 5km north of the apt) and i'm collecting info. Unfortunately we cannot take shots of the airport due to the COVID lockdown that prevent us from moving without a "valid" reason.
I'll keep you informed about runway status and marking positions
shezan74 April 27, 2020 8:14 AM
I collected some more notes. The TOTAL LENGTH of the usable 04L runway is still UNCHANGED and the runway will not be extended, for now. The extension is considered as a TAXIWAY. There is another junction that connects 22R with 22L, you can see it on charts.
Jan Vogel March 8, 2021 8:28 PM
Latest updates to this airport probably covered this..
Updated aerial map from Microsoft BING:
https://www.bing.com/maps?osid=4a87d2e0-4c83-4b92-af58-81e78db4a310&cp=45.507153~12.346262&lvl=16&style=h&v=2&sV=2&form=S00027
At least, taxiway G is what should be F. And the signs that indicate stand numbers (those that are "in the terminal", in front of the aircraft parked) not correspond with those that are on the floor. This are the correct ones. For example, I was on gate 324.
flyingpauls February 21, 2021 10:18 PM
Indeed, G should be F. The quick exit G has not been implemented. I try to sort out the confusion with the ground signs too. Thanks for the hint.
flyingpauls February 22, 2021 6:53 AM
I noticed it is not the ground signs, but the old signs in front of the gate. I fixed those.
Is it possible to add the holding point B for Rwy 04R? Thanks for your beautiful work.
There are trees before the threshold of runways 04R and 04L. See attachment.
Jan Vogel October 2, 2023 10:45 AM
I can confirm the issue - however runway 04L is not used as a runway anymore, so the issue is not pressing. Extending the airport boundary or placing an exclusion zone should get rid of the trees which are not present in real life.
Jan Vogel March 22, 2024 8:21 AM
This was fixed with the latest inclusion of "automatic autogen removal in front of runways" technology.