When we get to a finished product, probably the best way to handle it for our Database editors is to keep a Google Doc that we can keep edited. Then export that to update a SQL Database and then all the markers. That's probably easier (and safer) than giving everyone access to the SQL database.
That's essentially what we did in the past. It's just we used Fusion Tables as the database that we edited and then exported it into a Fusion Table static data map.
Here is a rough draft small demo map with a few MMIMO sites in the greater Seattle area:
This is what most users will see.
I will be making performance enhancements in the coming weeks, although the map seems to perform well with all of the datasets I've tested thus far - up to 9,000 pins.
I currently have not had time to make a publicly-available backend for people to fiddle with, but @S4GRU had a chance to take a look at it and can speak to how it works.
Most likely MHF4, or possibly u.fl size ports. I found what look to be u.fl on the T-Mobile Askey board and I am tearing it down after a late snack to find out the same thing. I have a ton of these handy in my lab but you can get MHF4 here and u.fl here with 2 day shipping. It's where I get all of mine and they work great. Just select what type of SMA jack you want on the opposing end in the dropdown.