karson_'s Comments
Changeset | When | Comment |
---|---|---|
82909073 | over 4 years ago | You mapped, osm.org/way/786459222, jumping over a curb, going through hedges, and across a pedestrian area. |
100599732 | over 4 years ago | You should never manually draw a circle. This loop has a clearly defined radius. Use the circularize tool in the editor.
|
100220138 | over 4 years ago | Great stuff! If you are at all interested in mapping public areas like WMA or parks you could try this query in https://overpass-turbo.eu/. It will show nodes imported from GNIS which have not been converted to areas. [out:json][timeout:25];
|
99419073 | over 4 years ago | Bshea38, It appears that there are 2 Reno Memorial Dog Parks marked on the map. The one you added, osm.org/node/8430654390. And another a block away mapped as an area, osm.org/way/605108717. Can you confirm which is the correct location? Or are there two separate areas for the dogs? |
99059047 | over 4 years ago | Tarheelfan, In this changeset you accidentally changed a portion of US Highway 6 to a golf cartpath. Another editor has corrected the edit, but you should be more careful in the future. |
99401215 | over 4 years ago | It looks like you accidentally dragged a node at the intersection of 1st Avenue and 1st Street and attached it to the IC admin boundary. I went ahead and corrected the positioning of the node. I would recommend disabling map features you don't plan on editing, like boundaries. You can do this in iD by going to the Map Data tab and then enabling/disabling what you need in the Map Features section.
|
99270246 | over 4 years ago | The residential polygon you marked was already contained inside a larger one for the whole Stratford Crossing neighborhood. I went ahead and tried to make the landuse a bit more granular and add some of the roads to the northwest which will probably be constructed at some point. |
99274836 | over 4 years ago | Hi, A road like this would be best described as a frontage road. A road which is parallel to a higher priority road and where all buildings are addressed with the higher priority road. Usually caused by road realignment. In this case, the front entrance to these houses is off the frontage road. Usually the front entrance is highway=residential and the back entrance is service=alley. It doesn't make that much sense to have to drive down an alley to get to your house. I assume these houses are addressed XXXX MLK Jr Pkwy. Usually there will be a street sign to mark the name of the frontage road. Not sure if there is one in this case? In my opinion, even if the street doesn't have a street sign, it is best practice to give it the name=* tag so that routers can find there way to the buildings.
|
87008146 | over 4 years ago | Not a building passage |
83287598 | over 4 years ago | I know this edit is a bit old, but I have to point out that you used the tunnel=building_passage tag incorrectly. |
99058450 | over 4 years ago | Also, you shrunk the extent of Heritage Wesleyan Church's landuse=religious area despite them owning and using the grassy area next to the church nearly every day.
|
99058450 | over 4 years ago | You are using the natural=wood tag a bit too freely. Just because an area has a tree canopy does not mean it deserves the natural=wood tag. If the area is mowed underneath, then it shouldn't be mapped, or can be mapped as individual trees. Also, the landuse=forest is a contentious tag. Opinions differ on accepted practice, but I only use that tag for managed forests being planted for timber production.
|
98954981 | over 4 years ago | I'm confused on why you are calling osm.org/way/905316667 a building passage. Per the wiki, building passages are enclosed on 2 sides by walls of the building and above by interior parts of the building. In a case like this, the "passage", as you are calling it, has a wall on one side and is open on the other 3 sides and does not have any part of the building above it, just a roof. It should be very obvious from the aerial imagery that this is the case. |
98930089 | over 4 years ago | You placed a church in the midde of what appears to be cornfield in all imagery sources. Are you sure there is actually a church here?
|
98837483 | over 4 years ago | While the maxspeed tag was clearly false as you mentioned, you didn't have to remove it. A simple check at the edit history should have told you that the speed is 35 and lanes is 2 and that the 352 was a typo.
|
98397463 | over 4 years ago | I went ahead and disconnected Mokena Terrace from 24th Street. This means that no traffic should be routed between the two streets.
|
98268971 | over 4 years ago | Hi, this road was correctly labelled Banbury Circle Northeast. The on the ground street sign reads Banbury Circle Northeast and the county GIS portal shows these houses addressed with Banbury Circle Northeast.
|
98041987 | over 4 years ago | The auditor's site still shows a road easement here. Are you sure it isn't a class B or C service road? In that case it should be marked highway=track.
|
97323115 | over 4 years ago | In this situation, the road osm.org/way/772941530 should be name="2nd Street". Name is supposed to refer to the commonly used name, typically found on the street signs. So the name of the street is 2nd Street, but is also Highway 6. Notice the tag ref="US 6". The ref tag is used to denote highway networks which are posted with route shields. This tag is rendered in the standard Carto layer in addition to the name tag. The ref tag can be used for interstates as "I ##", US highways as "US ##", state highways as "IA ##", and county roads as "CR ##" |
97320169 | over 4 years ago | Heads up, when making names don't use abbreviations. So something like, "hwy 6", should be written in full as, "highway 6". This allows the renderer to judge when the road name should be abbreviated or not. It also prevents confusion in abbreviations. For instance, consider osm.org/way/15933860. This street was abbreviated as "Heim Str" which someone assumed meant "Heim Street". In reality, "Str" was short for "Strasze"
|