Don’t store big amounts of data in modules in the first place. Store it somewhere else and require it from there. You can store it in datastores, in a url endpoint you can require with HttpService, really anything that comes to mind.
Just don’t store it in plain text inside a module script. Not only will the entire session lag when you open studio, but it will also take a ton of extra time to publish updates for that place. In general Roblox isn’t optimized for very large scripts.
Another thing you can do is store the compressed version of the data in a module script, and decompress it inside code when you need it. But the main negative of that will be that you wont be able to edit said data. On the other hand, if this some sort of API result, you may not want to edit it in the first place.
There are many patterns in your data that you can take advantage of to compress it. For example the airport names all have english characters that are just capitalized in the first letter, this means you need just 5 bits to represent a character(because the english alphabet has 26 letters) instead of 8 bits that are actually used. Also there is categorical data in there that can be converted to enums and then bits. For example strings like “small_airport” don’t need to be stored whole, you just need to figure out all the different values, assign increasing numbers to them, and then figure out how many bits it takes to store them(it likely is 3-4 bits instead of all the bytes you waste). Even the coordinates can be compressed down using custom float representations if you are aware of how many decimal points you need.