2018-05-23 02:16:53.132654+02 by Dan Lyke 2 comments
Older article, but it just came across a The Spatial Community Slack channel: Why Map Portals Don't Work: Part I
A little musing on why command-line interfaces (in the form of search boxes) are a necessity; slippy maps don't do everything.
That's related to Few Interact With Our Interactive Maps–What Can We Do About It? from last year, talking about ways other than slippy maps to present data.
[ related topics: Work, productivity and environment Community Maps and Mapping ]
comments in ascending chronological order (reverse):
#Comment Re: Why Map Portals Don't Work made: 2018-05-23 11:47:05.660067+02 by: DaveP
Does your map interaction even work if I’ve shut off JavaScript because your map gets covered up by some annoying ad or a "we use cookies to make your experience suck" dialog that obscures the map completely?
Increasingly, if the only interface to the data is a map, I’ll just close the window and give up, and I LOVE maps, and used to prefer them as a way of interacting with data.
Kids. Lawn.
#Comment Re: Why Map Portals Don't Work made: 2018-05-23 19:11:46.803263+02 by: Dan Lyke
I do miss the old MapQuest interface that was JavaScript free... May still be, unfortunately so much of the web is a big ol' security hole these days that it's really not navigable without JS.