Hey folks, good comments here.
Couple notes and feedback.
First, Cityfreq.com is just a old dump of the FCC database into an static html indexable site with lots of ads. In the beginning, google indexed that entire site and I bet they were making a pretty penny on advertising sincemost searches 3 years ago had cityfreq at the top. I'm not sure how successful they are now, but I'm sure they are still pulling in some ad revenue since folks are still stumbling across it.
AntennaSearch.com is a nice site, however I'm planning on releasing this same level of functionality for the radioreference.com site except with more features. You'll be able to choose a radius to search from a specific point, a specific lat/long, USGS feature, or address. In addition, I'll provide you a google map where you can draw where you want to search for FCC data and get a nice response custom response. I've written most of the Google Maps code, SQL, and math etc required to do the searches, it's just a matter of touching it up, optimizing the queries a little more, and writing the interface.
Right now the queries take an average of 9 secs... so there is some work to be done there.
Couple notes and feedback.
First, Cityfreq.com is just a old dump of the FCC database into an static html indexable site with lots of ads. In the beginning, google indexed that entire site and I bet they were making a pretty penny on advertising sincemost searches 3 years ago had cityfreq at the top. I'm not sure how successful they are now, but I'm sure they are still pulling in some ad revenue since folks are still stumbling across it.
AntennaSearch.com is a nice site, however I'm planning on releasing this same level of functionality for the radioreference.com site except with more features. You'll be able to choose a radius to search from a specific point, a specific lat/long, USGS feature, or address. In addition, I'll provide you a google map where you can draw where you want to search for FCC data and get a nice response custom response. I've written most of the Google Maps code, SQL, and math etc required to do the searches, it's just a matter of touching it up, optimizing the queries a little more, and writing the interface.
Right now the queries take an average of 9 secs... so there is some work to be done there.
Last edited: