Joseph E's Comments
| Changeset | When | Comment |
|---|---|---|
| 86739200 | over 5 years ago | Tags in OpenStreetMap should be verifiable by regular mappers who visit the area. These buttes do not have any physical characteristics which identify the as volcanoes. Basically all hills in the Cascades range and surrounding areas are volcanic in origin, but if the volcanic vent is extinct (like these, which have not been active for >57k years) and no longer visible, there is no way to know that these hills were volcanoes in pre-history.
|
| 83113086 | over 5 years ago | Edith,
|
| 88309790 | over 5 years ago | Thank you. So, you are able to determine this by looking at aerial imagery? It's not necessary to check whether or not the settlement was planned by the local government - but usually these irregular settlements are not planned or approved, right? |
| 88309790 | over 5 years ago | Hello Ronnie.
|
| 84932633 | over 5 years ago | Hi Bravo Mapper,
|
| 83113086 | over 5 years ago | Hello Edith. I noticed that most uses of the tag "residential=irregular_settlement" are in this part of Syria. Do you know what this tag means?
|
| 70402835 | over 5 years ago | This area has many features added as natural=sink_hole, but the much more common tag is natural=sinkhole - see natural=sinkhole |
| 75765709 | over 5 years ago | It looks like there are a number of features that were tagged with natural=sink_hole here. Perhaps they should be natural=sinkhole instead? See natural=sinkhole |
| 70404200 | over 5 years ago | Michael, In this area there are a number of features tagged as natural=sink_hole which were first added a year ago. Perhaps you meant to tag them natural=sinkhole? See natural=sinkhole
|
| 84140005 | over 5 years ago | Majid_jafary, I see that you have added many building=plot features which cover the whole area of a property, but are not actually limited to the area of the building. Please considering using a different tag to map plots, such as place=plot or boundary=lot - however, it is not common to map plot boundaris in OpenStreetMap in general. The key building=* should only be used for actual buildings. |
| 63523085 | over 5 years ago | That's a local use of this tag. Internationally it is more common that highway=trunk represents "A trunk road, trunk highway, or strategic road is a major road, usually connecting two or more cities, ports, airports and other places, which is the recommended route for long-distance and freight traffic. Many trunk roads have segregated lanes in a dual carriageway, or are of motorway standard. - wikipedia"
It's hard to argue that this road is high importance if it's connected to highway=secondary roads. Perhaps the rest of OK 33 should be upgraded to highway=primary? |
| 63523085 | over 5 years ago | Why is this a highway=trunk? It connects to highway=secondary roads at both ends and in the middle, and it is a state highway. This suggests it should be a highway=secondary or perhaps highway=primary. Or should OK 33 be generally upgraded to highway=trunk? |
| 86299088 | over 5 years ago | Right, I understand that this is a popular way to tag extinct volcanoes, but it is incorrect. The tag natural=volcano should represent a volcanic vent, so the center of a crater or volcanic plug or fumarole etc, - but these nodes are the highest elevation point on each hill, so they are natural=peak features. It could be possible to map the historic location of the extinct volcanic vent separately, if you can find a reliable and accurate source for this information, but personally I don't think it is entirely appropriate for OpenStreetMap since it cannot be verified to be correct or not by OpenStreetMap users.
|
| 86299088 | over 5 years ago | tguen, I have changed these peaks back to natural=peak. The tag natural=volcano is used for a volcanic vent, so it needs to be active or dormant and still identifiable as a volcanic vent by a non-expert. These hills do not qualify. Also, the nodes are at the highest point of the hill, not necessarily the location of the extinct volcanic vent.
|
| 84946407 | over 5 years ago | |
| 84946558 | over 5 years ago | Stay-Healthy Streets in Seattle do not appear to be Living Streets According to the announcement by SDOT, the streets in the Stay-Healthy Streets program have a speed limit of 32 kph (20 mph), much higher than the maximum for a Living Street (20 kmh to "walking speed"). It appears that the legal change is that these streets are now motor_vehicle=destination, with through-traffic prohibited, but they are not Living Streets according to the description in this page or at Wikipedia: "designed primarily with the interests of pedestrians and cyclists in mind and as a social space where people can meet and where children may also be able to play legally and safely... vehicle parking may be restricted". "These streets are often built at the same grade as sidewalks, without curbs. Cars are limited to a speed that does not disrupt other uses of the streets (usually defined to be pedestrian speed), or through traffic is eliminated using bollards or circuitous one-way operation. To make this lower speed natural, the street is normally set up so that a car cannot drive in a straight line for significant distances, for example by placing planters at the edge of the street, alternating the side of the street the parking is on, or curving the street itself. Other traffic calming measures are also used." The streets in Seattle have street parking along their whole lengths, and there are no design changes compared to other highway=residential streets in the city, except for signage / paint. While I would personally love to see real Living Streets in the USA, it doesn't appear that this tag should be used in Seattle (or Portland, where we have implemented similar short-term policies on "Neighborhood Greenways") at this time. If the city redesigns these streets and lowers the speed limit to 5 or 10 mph and legally allows pedestrians to use the whole street at any times, then we can reconsider. --Jeisenbe (talk) 20:48, 31 May 2020 (UTC) |
| 66212659 | over 5 years ago | freebeer, what is the source of data for the Agua Caliente reservation? I'm having trouble confirming it. Compare: http://www.aguacaliente.org/content/Geospatial%20Information%20Systems/ |
| 78697606 | almost 6 years ago | My guess is that this changeset was an honest misunderstanding, but I will have to investigate further. |
| 78643277 | almost 6 years ago | Re: "not accepted by the Indonesian community." Are you in Indonesia? I do not normally hear much from other local mappers here in Papua. Is there something in particular that looks incorrect? I checked maxar imagery, but it was rather low-resolution so there might be mistakes. > What are you fixing here?
The coastline had previously been moved in this section by a non-local mapper, who was trying to fix it after it was accidentally broken.
|
| 79201390 | almost 6 years ago | "This results in coastline, land polygon, and water polygon artifacts to consider this large body of water extending up to Buenos Aires to be land rather than water." That's not quite correct. What happens is that the coastline is only used once a day to update the ocean polygon shapefiles, which are used to render the ocean on the "standard" map layer of openstreetmap.org, the Openstreetmap-carto style. But to avoid this problem from occuring in the short term, I suggest this compromise: 1) Extend the coastline up above Buenos Aires
This way, the Rio de la Plata will still be represented as a river (estuary) in Openstreetmap, and the coastline will be at a more reasonable location. - Joseph Eisenberg |