I’ve built something similar, although my tool can pull its data from any service that supports tile indexing via the Web Mercator Transform (e.g. Google Maps, OSM, basically every online mapping service):
Its original purpose is the creation of Twitter bots like the ones liked below, but it works well for grabbing detailed satellite maps of arbitrary areas.
And the images are generated in your system with the data from a public source.
Not sure who owns the copyright to them. ^^
On 18.04, it can't find the correct openvc
On 19.04, same things
On 20.04, the repo doesn't include config for 20.04
Would love to try it, but ...
However, here's a hint: try to install a minimal ubuntu server on a VM and install/run your package.
You'll quickly discover the real transitive dependency set of your software.
I've recently discovered pretty cool telnet server. Map in telnet: telnet mapscii.me
At first I couldn't figure out how to zoom in. I pressed all they keys. Then I accidentally moved the mouse over the window and it zoomed in.
So my first thought was, "how the heck do they capture the mouse in the terminal!".
Then I exited out of it by killing telnet, and noticed that my terminal was still capturing my mouse input! Just moving the mouse over the terminal put ASCII codes on the command line.
What is this sorcery?
Definition of felicette
You can use it like this:
docker run -it -v "$PWD"/felicette-data:/root/felicette-data milhouse1337/felicette felicette -l "Montreal"
Take quite some time to install. And some images are great like
`felicette -l "New York"
Some totally blank (real time and dark)
felicette -l "Hong Kong"
Some not sure as a bit random like those of Three Gorges Dam using
felicette -c 109.5568 31.0390
felicette -c 111.003761 30.823748
felicette -c 110.25 30.95
One has coloured and the other not sure.
I guess this is part of being satellite images?
I'm checking on this, thanks for reporting this. Meanwhile, could you please raise this as an issue on the repository?
- Allow farbfeld output (to stdout)
- Allow specifying your own assignment of bands
- Allow to skip the colour adjustment if you want to do that separately
- Ensure it works correctly with a non-Unicode locale
Points 2, 3 are in the to-do list.
Will definitely add 1, 4.
And thanks for checking it out!
Preferably on the phone/tablet.
Works quite well. Input images must have geo data in the exif metadata like longitude, latitude, FOV, camera pitch (most drones e.g. Autel and DJI drones will include this). You need to set it up on a server, then it's a web app which you could access from a phone/tablet but it involves uploading the images so it probably won't work well like that.
But I'm sure you're aware of https://qgis.org/en/site/. Some of my friends used this to analyze vegetation using drone imagery.
> TL;DR: Generate JPEG earth imagery from a location's name/coordinates
It downloads imagery. At first I thought this was a project to simulate satellite imagery from OSM data or something.
> This tool is for a sentient being who wants to view high-res satellite imagery of earth
Landsat is what 30 meters-per-pixel? That's not high-resolution.
Will update the README, thanks for pointing it out.
> Landsat is what 30 meters-per-pixel? That's not high-resolution.
With the panchromatic band, we can get 15m resolution. But you're right with the fact that one can get images with better resolution on any commercial platforms.
But even OpenMapTiles renders at 15m, I feel. Still have to look into some docs though, I'm curious.
But even at it's full potential, Landsat 8 gives a temporal resolution of 14 days for a location, iirc.
So released with Landsat 8 first, and I think sentinel 2 has better resolution, up to 10m, if I am not wrong. So it'd be a lot better if Sentinel 2 integration were in-place.
It supports sentinel 1/2/5p, landsat 8 and a few other satellites if you have the required API access identifiers. The idea is to fetch data not from buckets but from the actual sources, so the underlying philosophy is a bit different.
"The satellite has a 16-day repeat cycle with an equatorial crossing time: 10:00 a.m. +/- 15 minutes." from USGS website.