Menu
▾
▴
2 Attachments
#2165 Phi - vfrmap tile server address change
Don't know if it is substantial, but one day on forum or mailing-list i've seen that someone complains that vfrmap does not work on the Phi. It was connected with tile server address change. Attached is the patch, that changes the URL for the latest tiles e.g.
Hi,
I see the date in the address has already changed to 20200227 in the mean time. We'll keep running behind if we continue hardcoding the url like this. Maybe it's time to start using the API that was designed for embedding the maps in other applications? This does come with a limit on number of requests though: http://vfrmap.com/map_api.html I don't know the details of our deal with VFRMap though, if we have any...
If I might to add something to it. As stated in the mentioned page "For any use of the API, please contact api@vfrmap.com to obtain an API key. API requests without a key will soon be rejected.". I don't think there would be any acceptable decision on behalf of vfrmap or OpenWeatherMap that FG can use one shared key (they would have to remove request limit to this key).
There is small discussion in the #2179 ticket (https://sourceforge.net/p/flightgear/codetickets/2179/) regarding openweathermap API access (also with a key). Where to store the keys users have obtained. There was my proposition to add another dialog inside the weather dialog (weather API keys), but maybe it should be more system-wide setting e.g. internet API keys and there one can have vfrmap,owm or other keys. Just my 2 cents.
The VFRMap API URL has been updated (again? not sure how many times its changed since this issue was created) in merge request #333. As Gijs said, it will continue being a problem as they periodically change the URL for the API however.
The approach that we landed on for dealing with OpenWeatherMap requiring an API key was just to remove it. That was also done in #333: https://sourceforge.net/p/flightgear/fgdata/merge-requests/333/.
Last edit: ranguli 2024-10-21