OpenStreetMap logo OpenStreetMap

Changeset When Comment
171081107 4 months ago

Hey GenericUsername4,

Please check the wiki regarding the distinction between street lamps and lighting masts:

tower:type=lighting

"This tag is for large poles that are used for lighting.
E.g. lighting for stadiums, public places, floodlights, and large headlight masts.

This does not include street lights, even if they are larger."

170935520 5 months ago

Hi silversurfer!

Per the wiki, every tennis court should be individually tagged and ideally the entire pitch (with fence) should be tagged as a recreation ground.

---

"Draw the area of every single tennis court and add leisure=pitch + sport=tennis."

"Tennis courts are typically surrounded by a fenced area. Draw the way of the fence around the court(s) and add barrier=fence. Add any entrances to the fenced area with barrier=gate and connect them to footpaths or other equivalent ways in the surrounding area. The closed 'fence' way containing courts inside it is often tagged with landuse=recreation_ground as well."

---

sport=tennis

The node for each tennis court will eventually be turned into an area - I literally can't keep enough tasks available here:

https://maproulette.org/browse/challenges/41188

149975393 6 months ago

Hi,

Please read the documentation re: Lighting Masts.

"This tag is for large poles that are used for lighting.
E.g. lighting for stadiums, public places, floodlights, and large headlight masts.

This does not include street lights, even if they are larger."

Thanks!

164140644 8 months ago

Hi osmhonehone,

Instead of mapping utility pole or streetlamp-mounted microcells like this:

MCCMNC=310410
communication:mobile=yes
man_made=tower
tower:construction=pole
tower:type=communication

It would be better to follow existing standards and wiki guidelines to map them like this:

MCC=310
MNC=410
communication:mobile_phone=yes
highway=street_lamp (or man_made=utility_pole)

This approach should align more closely with current tagging practices.

Let me know if you have any questions!

162872949 9 months ago

Hi Tex,

Please avoid using:
"man_made"="communications_tower"

This tag is meant for very large landmark towers (e.g., CN Tower). For typical telecom structures, a better tag set is:

"man_made"="mast"
"tower:type"="communication"

See the wiki for more details. Thanks!

161041805 12 months ago

Hi Adam,

Something like support:pole (872,000 uses) may be better than tower:type=advertising (542 uses) in this case.

Feel free to browse the wiki for more ideas:

advertising=*

160928953 about 1 year ago

Hi rivermont,

There's no WASU-FM transmitter at the school.

Confirmed via Wikipedia: "Their transmitter sits atop Rich Mountain in Watauga county."

https://en.wikipedia.org/wiki/WASU-FM

And via FCC query:

https://www.fcc.gov/media/radio/fm-query

159442956 about 1 year ago

Hi David,

I noticed you retagged a mobile phone mast (node/10895269171) as a mobile phone tower in this changeset.

As a reminder, here is how the wiki defines the difference between a tower and a mast:

"Unlike a man_made=tower which is accessible and provides platforms, a man_made=mast only offers ladder steps to climb it on the outside."

As this site more closely matches the definition of a mast, I've gone ahead and re-tagged it.

160397783 about 1 year ago

Hi Greg,

Responding to your PMs here.

Thanks for explaining the issue. If the iD editor isn’t showing mobile_phone in the dropdown, I’d recommend reporting it as a bug on the iD GitHub page:

https://github.com/openstreetmap/iD

As a workaround, you could manually add the communication:mobile_phone tag without using the dropdown or try another editor, rather than deleting the nodes.

Regarding the tower vs. mast distinction:

- Towers must be freestanding and provide platforms for accessibility.

- Masts can be either freestanding OR guyed and must not have platforms, offering only ladder steps for access.

The key difference is accessibility. The presence or absence of guy wires does not determine the classification. For example, the wiki page for masts features a freestanding monopole-style structure as the example photo.

Based on this, the three sites you changed to towers align more with the definition of masts.

160397783 about 1 year ago

Hi Greg,

I’m a bit unclear about the purpose of this edit—it seems you’ve deleted three existing communication mast nodes and replaced them with new nodes tagged as communication towers.

A few concerns:

1. By removing the original nodes instead of simply re-tagging them, you’ve erased their edit history. This goes against best practices as outlined here:

osm.wiki/Keep_the_history

2. The correct tag for these structures is man_made=mast, not man_made=tower. According to the OSM Wiki: “A tower is accessible and provides platforms, whereas a mast only offers ladder steps to climb it.”

man_made=tower

Notably, one of the deleted nodes was one you originally added as a mast.

3. Deleting the nodes has also removed additional descriptive tags, such as the construction type, which were not re-added in your edit.

Would you mind clarifying the reasoning behind this changeset?

142777064 about 1 year ago

Hi Minh,

Thanks for the comment and for linking the discussion.

As you noticed, my edit aimed to align the communication mast with current documentation.

While I see the merit in your proposed changes, I have some concerns about implementing them in practice:

1. The vast majority of communication masts are collocations with multiple operators.
2. Mapping masts as areas, as mentioned in the discussion, adds unnecessary complexity and essentially forces micromapping.
3. Since the proposal has not yet been accepted into the documentation, current guidelines should generally be followed.

Regarding the removal of the name—this was an oversight on my part, and I agree it makes sense to retain it in this case.

I removed the wikidata tag because there are multiple operators at this site (with unique wikidata tags), and I believed retaining a single wikidata tag would inaccurately represent the collocation.

141495754 about 1 year ago

If every other style of site (monopole/lattice/guyed) has a construction type, why wouldn't a site mimicking a tree or flagpole?

141495754 about 1 year ago

Thanks for the comment. What would you suggest the construction type be for a site mimicking a tree or flagpole?

152364454 over 1 year ago

Hi,

I've noticed you've been adding some communications masts!

Please take note that the tag "man_made=communications_tower" should rarely be used. Instead, please use the combo "man_made=mast" +
"tower:type=communication".

Thanks, and feel free to check the documentation for more info!

152339628 over 1 year ago

Hey Alan,

I've noticed that you've been changing the tower construction type (tower:construction) designation of some sites from "monopole" to "freestanding".

I just wanted to give you a heads-up that "monopole" is the industry standard term for these types of sites. While "freestanding" is a general catch-all term for sites without any guy wires, it is less specific than "monopole." Additionally, "monopole" is already widely used, with over 9,000 nodes worldwide using this tag.

Thanks!

149403096 over 1 year ago

Yep, that was a typo - should have been the "operator" tag.

Thanks for the catch! Updated.

147621678 over 1 year ago

Hey, thanks for the heads up.

The address was added from the U.S. DOT NAD (via Rapid Editor). Clearly, there are some issues with this source.

I'll go through my older edits to see if I've done this for any other nodes and be a bit more careful about adding addresses from this source in the future.

140259522 over 2 years ago

My edit should have only affected standalone nodes (at traffic signs) which were not accompanied by a node on the adjacent way. Per the documentation:

"Insert a node with tag highway=stop on the approach way(s) that must stop, at the stopping point. Drivers may be required to give way (yield) whether or not a physical sign is present; but if you also want to capture the signs, you can use a traffic_sign=* tag as well"

(where "as well" is emphasized within the documentation).

140259522 over 2 years ago

I converted them to a node on the road where they occur, which is the correct way to represent them (as per the documentation).
---

Published using OSMCha: https://osmcha.org/changesets/140259522