I hope not, especially for visually impaired users, tablet or mobile users, or just for general ease of use. It's way easier for me to type in a location's name or airport code than try to figure out where it is on the map.
Here's an example: let's say I'm flying from Seattle-Tacoma (SEA) to Boston's Logan Airport (BOS). On a normal travel site, I type in SEA<tab>BOS<return>. Boom, done.
In this design, I'd somehow or another choose my origin, and then try to figure out which of the many major airports in the Northeast I'm actually looking for. My sense of geography of that area is pretty bad, so it would likely take me a while to figure it out.
Or let's consider the reverse: flying to the Pacific-Northwest. If you're zoomed out far enough, you're going to have a very small amount of distance between Vancouver, Seattle, and Portland. I guess you'll need to zoom in far enough to be able to visually differentiate them in order to drop the pin? OK, but why not just type in "Vancouver", "Seattle" or "Portland"?
I hope not, especially for visually impaired users, tablet or mobile users, or just for general ease of use. It's way easier for me to type in a location's name or airport code than try to figure out where it is on the map.
Here's an example: let's say I'm flying from Seattle-Tacoma (SEA) to Boston's Logan Airport (BOS). On a normal travel site, I type in SEA<tab>BOS<return>. Boom, done.
In this design, I'd somehow or another choose my origin, and then try to figure out which of the many major airports in the Northeast I'm actually looking for. My sense of geography of that area is pretty bad, so it would likely take me a while to figure it out.
Or let's consider the reverse: flying to the Pacific-Northwest. If you're zoomed out far enough, you're going to have a very small amount of distance between Vancouver, Seattle, and Portland. I guess you'll need to zoom in far enough to be able to visually differentiate them in order to drop the pin? OK, but why not just type in "Vancouver", "Seattle" or "Portland"?