Jump to content

Crowd sourced coverage


mhammett

Recommended Posts

http://www.cellmapper.net/ is another one. Even before I found S4GRU, I felt that Sensorly was the most popular service, and they had the best mobile app. OpenSignal has some strange things in their app (like the "which direction is your tower" estimator that I have never observed working with any accuracy) that make me scratch my head.

 

-Mike

Link to comment
Share on other sites

I've used both Sensorly and OpenSignal, but Sensorly is far less buggy and feels more polished. Doesn't Root Metrics use crowd sourcing for their coverage maps? I have installed and poked around a couple more but quickly deleted them. Most everything out there for "signal info" or "coverage comparisons" is crap besides SignalCheck (Pro) and Sensorly.

Link to comment
Share on other sites

http://www.cellmapper.net/ is another one. Even before I found S4GRU, I felt that Sensorly was the most popular service, and they had the best mobile app. OpenSignal has some strange things in their app (like the "which direction is your tower" estimator that I have never observed working with any accuracy) that make me scratch my head.

 

-Mike

I was looking for that one the other day! I used it back in the day on my Epic. Thanks for the link!

Link to comment
Share on other sites

I have been messing around with an app called Net Monitor. When it's active it will log your location, signal strength and your SID, NID and BID that you can export to a KML file. That can be opened by Google maps and you can selectively see how the coverage is working on a sector by sector basis. It's pretty neat. It's not crowd sourced at all which was the next step I was wanting to take it. Find a way to take uploaded KML files, average the data and make it publicly accessible. That's the part where I've not dabbled much at all. 

 

My personal experience is that the KML files can get quite excessive in size which makes GMaps very unresponsive when opening it the first time. 

 

Thoughts?

Link to comment
Share on other sites

I have been messing around with an app called Net Monitor. When it's active it will log your location, signal strength and your SID, NID and BID that you can export to a KML file. That can be opened by Google maps and you can selectively see how the coverage is working on a sector by sector basis. It's pretty neat. It's not crowd sourced at all which was the next step I was wanting to take it. Find a way to take uploaded KML files, average the data and make it publicly accessible. That's the part where I've not dabbled much at all.

 

My personal experience is that the KML files can get quite excessive in size which makes GMaps very unresponsive when opening it the first time.

 

Thoughts?

Netmonitor only works if the sites in your market broadcast their true locations. In most markets, they do not. Rather they broadcast some point offset, sometimes quite sways away, for each sector.

 

Sent from my HTC ONE

 

 

Link to comment
Share on other sites

Netmonitor only works if the sites in your market broadcast their true locations. In most markets, they do not. Rather they broadcast some point offset, sometimes quite sways away, for each sector.

 

Sent from my HTC ONE

That may be true. I know in the Columbus market they've been accurate. But the site's location is irrelevant if you're mapping signal quality. Your GPS location, the RSSI and the site's SID/NID/BID are relevant.

Link to comment
Share on other sites

That may be true. I know in the Columbus market they've been accurate. But the site's location is irrelevant if you're mapping signal quality. Your GPS location, the RSSI and the site's SID/NID/BID are relevant.

True. I just automatically assumed you were wanting the site location. Reading it again, I see you didn't actually mention that.

 

Sent from my HTC ONE

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • It’s a neat and seemingly valid / effective strategy that, at least from my understanding, is only really used by VZW
    • Those are usually left over from the initial AWS deployment, so all run B13/B66 with support for BC0/BC1 (although that’s been shut off on most sites). No NR. Sites with the later Ericsson radios got an OTA update and broadcast B2. On those sites, a B5 OTA update was also available (and tested), but ultimately rolled back. Putting up all that power/spectrum severely degraded the B13 output.  The site atop Crystal Mountain is another story and uses the same setup as the site on the ridge near Neilton. These antennas were selected for their vertical beamwidth. Most modern directional antennas have small vertical beamwidths and would require extreme downtilt to cover the road next to a steep ridge. Thus, they would have a severely limited coverage footprint beyond the road. Omnis can be a better choice in these instances, especially when there’s LoS to the coverage objective (since they’ll generally have lower gain figures). Omnis also don’t run in to the horizontal sector edge problem, which can be difficult to optimize for with directional antennas that have complex or irregular 3D gain profiles. That’s why on a lot of sites on mountains, you’ll see wider antennas used. For example, the Verizon site on Joyce Ridge has three sectors with 80-degree HBW antennas. 
    • Do you know what RAN is behind those Omni's? LTE (bands?) are they pushing any NR through them? Very curious   edit: I guess I could check cellmapper etc but you might know more nuance!
    • N41 here has been expanded from 140Mhz to 180Mhz.  Speeds seem the same so they just need to work on backhaul
    • I noticed today that T-mobile has shut of B41 LTE in the Louisville area and widened the 2nd n41 carrier to 80MHz. That just leaves them with 5x5 B12, 10x10 B2, and two 10x10 B66 carriers on LTE, everything else is in NR (besides their 2G network). They have 20x20 n71, 20x20 n25, 5x5 n25, and 180MHz n41. 
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...