Hi everyone - first post here. I looked around but couldnt find an answer.

My organization is helping radio stations across africa generate maps that as accurately as possible, visually show the reach of their radio signal for the average radio user.

We are planning on doing this with GEOJson, our own database and Mapbox - however, it occurred to me that it might be of interest to others to have this data be publicly available.

But I understand that OSM is mostly for physical features - not so much invisible things like radio signals. But if it were possible to create a "layer" that showed the radio signals perhaps so it didnt interfere with other features on OSM.

Very interested to know people's thoughts.

Thanks!

asked 06 Jan '15, 13:41

Bart%20-%20Farmradio's gravatar image

Bart - Farmr...
61113
accept rate: 0%


  1. We have the concept of "verifiability". Radio signal strength is something that the average contributor cannot verify.

  2. we had in the past similar requests like radioactivity levels, noise polution, timezones, etc. We could create plenty of invisible polygons on the map. Since OSM editors are not able to manage easily layers, such invisible polygons for a limited public (unlike admin boundaries widely used for geocoding) is not really welcome in our global geodatabase. But we are happy if you create a mashup with OSM as background map ;-)

permanent link

answered 06 Jan '15, 15:07

Pieren's gravatar image

Pieren
9.7k2075157
accept rate: 15%

  1. Depends: My mobile phone can record signal strength in dBm for both mobile coverage and any WiFi APs it sees. This can be extended to other frequency ranges and types of transmissions using relatively cheap equipment no more exotic than a GPS receiver. So I don't think verifiability is an issue.

However, 2. As tempted as I am to like to have radio coverage on the maps I use, I don't think that should be a focus for OSM. Probably better to use OSM as background geographic data to overlay the signal strength map on.

(06 Jan '15, 19:39) stf

Well, verifiability will be an issue if you make some measurements in summer (leaves on the trees, especially when it's been raining) and some in winter (no leaves). :-)

(06 Jan '15, 20:04) SomeoneElse ♦
1

@stf: verifiability is an issue, esp. as signal strength and SNR varies wildly depending on equipment used (e.g. my old cellphone has excellent mobile coverage where the new one only reports mediocre, on the same network, in the same physical location).

(07 Jan '15, 10:33) Piskvor

There are other VGI projects that have special interests: https://wiki.openstreetmap.org/wiki/Related_Project Maybe openBmap is able to integrate such details and we all can get a geoposition by a list of radios, soon :-)

(07 Jan '15, 17:29) iii

I would be inclined to agree that its best to keep it seperate

There is no reason at all why you can't still release your data with an open licence (CC-By etc). It can then be mashed with OSM data in QGIS or whatever to give an accurate representation by anyone who wishes to use it.

Best of both worlds

permanent link

answered 06 Jan '15, 16:43

DaCor's gravatar image

DaCor
1.3k11028
accept rate: 2%

Hi @DaCor - happy to release the data of the mashup. Since I'm still finding my way around OSM, would that data be hosted on OSM or on our own server and then made available as a zipped file of geojson coordinates or shapefiles (for example)?

Also - we are planning to use mapbox for our mashups, as it allows for some custom basemaps/tiles - but I think they also use OSM no?

(07 Jan '15, 13:23) Bart - Farmr...

You wouldn't need to release the mashup data, just your own raw data. There are a multitude of formats you could release under, but yes geojson is as good as any. See http://www.townlands.ie/page/download/ for where additional download options were added simply to allow greater usage of the data.

Depending on what you are using, you should have an option to export in a number of formats. The more the better

(07 Jan '15, 16:02) DaCor
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×74
×25
×6
×5

question asked: 06 Jan '15, 13:41

question was seen: 2,691 times

last updated: 07 Jan '15, 17:29

powered by OSQA