You should take all free advice, especially that rendered with only a few sentences of input, as food for thought and nothing more. That said:
With 1000 911 clients, I would consider uptime to be essential. For that reason, I'd want a cluster - two NAS devices with replicated or at least duplicated content, each of which could handle the load should one go down. It also seems like you have more than one datacenter. If so then I'd consider having one cluster per datacenter, optionally with replication across data centers if required - map tiles are pretty static, so simply duplicating the data might be good enough.
Luckily, these would be pretty modest clusters. Your disk space requirements are very small - single digit TB - and you don't appear to need some of the really fancy features offered by the higher end NAS vendors. It seems like you need a smallish 10GbE NAS, with replication, able to service just eight or so clients each, but with each client potentially sending a very large number of small requests at a time. The usage seems like it'll be read mostly, which gives me an idea.
I like your idea of 10GbE, though you may not need the network redundancy if you go with a cluster. I like your idea of an SSD cache, but I would consider taking it even further. If your app is indeed read mostly, then pushing as much data as possible onto SSD will greatly improve response time, and actually reduce the load on the NAS devices. In other words, have you thought about going all SSD?