Hi Wotan. Thanks for fixing those culvert issues. I think a different water area tag should be used for the canal though.

Waterway=riverbank is a tag previously used for boundaries and areas of rivers, but it was voted to be deprecated in 2011, despite JOSM still having it as a preset (osm.wiki/Proposed_features/Water_details)

It would be more appropriate to tag rivers as natural=water + water=river, as now a vast majority of the world's rivers use this system. It also allowed canal areas like this to be tagged as natural=water + water=canal for better clarity.

For more information about the global efforts to improve and modernize river tagging, there's a wiki page here: osm.wiki/WikiProject_Waterways/River_modernization

Aw no problem. Already fixed the four riverbank tags from yesterday. They're easy to spot because they stick out like a sore thumb in Canada on TagInfo: https://taginfo.openstreetmap.org/tags/waterway=riverbank#map

JOSM has still been slow to adopt the new tagging presets, so it's hardly your fault. For more info on the global phasing-out of waterway=riverbank, there's a wiki page for it here. osm.wiki/WikiProject_Waterways/River_modernization

It also isn't necessary to add a name=* tag for river areas if there is already a waterway drawn though it that has the name. That way the same POI isn't named twice.

Hi Kevo. Thanks for adding more natural terrain detail for river.

Just wanted to note that waterway=riverbank is now considered a deprecated tag for river areas, despite still being a present in JOSM. Since all of Canada's rivers now use natural=water and water=river for river areas, I'd suggest you use those tags to future-proof your work and keep everything consistent with the national standard.

I don't think this entire area should have been tagged with "building=yes". It's inaccurate, and it creates numerous overlap conflicts with the actual buildings on the lot.

Ah! That makes a lot of sense you were experimenting with apps/rendering a bit. Right after I left the first comment, I was noticing how all the segments had slightly different variants of tags.

If you plan on doing more detailed waterway mapping, you might enjoy this recent talk the author of the wiki project gave on river tagging. Goes deeper into the functionality and history than I could describe in a message.
https://youtu.be/c5YwXDKGr2Y

Hi Jerry, appreciate your work micromapping the natural landscape! Just wanted to point out a small issue with the tags you used for river areas.

There are currently two tagging systems for river areas: the legacy "waterway=riverbank" scheme and the new "natural=water" + "water=river" scheme which was created in 2011 and has recently gained enough traction to become the dominant system globally for river tagging. While JOSM still tends to default to the older system, the iD editor actually will mark waterway=riverbank as an outdated tag.

At this point in time, many countries (including the US) have standardized all of their river area tags under the new system, so in order to future-proof your work moving forward, it is highly recommended to use the newer tagging scheme.

I fixed the tags in from this changeset, but I saw in your bio that you prefer feedback in changeset comments, so I thought I'd give you the full story behind it. If you want to see more about the global project to modernize river tags, there's a wiki page about it here: osm.wiki/User:ZeLonewolf/Procedure/River_modernization

At this point, it appears that 55% of the river areas in Panama actually use the new scheme, which may be a good thing, considering most countries in the Americas also currently favor it.

If you have any concerns about some outside contributors recklessly handling Panama's rivers, so should take it up with the user Zelonewolf, as he has been working with the local communities of many countries to "modernize" their river data in a careful non-mechanical way which fixes many more issues than just switching tags around. You can read more about his efforts on this wiki page: osm.wiki/User:ZeLonewolf/Procedure/River_modernization

Hi Mario, it's alright. Although the iD editor considers the tag deprecated, it is still a valid tag on JOSM and the general OSM wiki community for now. Since 2016, there has been a very gradual global transition from the classic waterway=riverbank tagging scheme to natural=water + water=river for river areas.
For that reason, I did not want to call the classic tags "deprecated" in my changeset comment. The main reason I converted these river areas to the newer tagging system was because I noticed other river areas along this river used the new tags, and data-reading issues can occur when two tagging systems are mixed.

Hi Tom,

I wanted to give you a heads up regarding the tagging scheme for river areas. There has been a global initiative to expedite the standardization of river tagging in OSM. At this point, many countries including the US have fully replaced all instances of the waterway=riverbank tag with the modern scheme of natural=water+water=river, checking each feature individually.

New uses of the waterway=riverbank tag in the US will likely be subject to reversion, either by global project contributors or mappers using the iD editor (which currently displays an error warning, considering waterway=riverbank to be an outdated tag). Hence, I would strongly advise using natural=water+water=river for any new river areas you add, in order to best future-proof your work.

If you like, you can read more about the river modernization project here: osm.wiki/User:ZeLonewolf/Procedure/River_modernization

Nice work and attention to detail with these river areas. I just wanted to give you a heads up that there is an ongoing global collaborative project to phase out the waterway=riverbank tag in favour of using natural=water + water=river as the modern standard. (The iD editor actually already considers waterway=riverbank to be an "outdated" tag when displaying error warnings.)

Since Ireland has already fully switched over to the new tagging scheme in February, I would recommend avoiding the use of waterway=riverbank for consistency's sake.

Here is a link to the project wiki for more information: osm.wiki/User:ZeLonewolf/Procedure/River_modernization

https://overpass-turbo.eu/s/15UJ

@Horza It pretty much already has been retired, in the US at least. Judging by the overpass query, this seems to be the only use of the waterway=riverbank tag present in the country.

This changeset definitely did more good than harm, but it might be worth changing the river area tags back to natural=water + water=river for consistency's sake.

Hi. I have no connection with the Apple Data Team. I'm sorry if I mistraced something. I have been updating several coastal river outlets in Africa that have appeared to shift in recent satellite imagery. If you have more local knowledge of this area, I will leave it alone moving forward.

Nice work! These indoor maps really help the shopping center feel more complete!

Out of curiosity, what made you stumble upon this mall-mapping project here in Staten Island? Noticed a lot of editing traffic lately and was wondering if there's been some recent promotion somewhere.

Hey there. I'll look into re-tagging the mutlipolygons, since like you said, they're pretty cumbersome and tricky to edit (especially in iD) without doing more damage.

There's a similar instance of this a few miles north in Hoboken, where roadway polygons were not removed, but they were re-tagged to be a "Road Area" instead of "Highway Feature".

Hi Daniel. Nice work with these bus routes! As a local, just wanted to give you a heads up that a few southbound bus stops along Richmond Avenue in the New Springville neighborhood (near the Staten Island Mall) have recently been relocated from the west side of the street to the center median. Several medians have been completely redesigned to accommodate a new separated bus-only stopping lane.

This construction has occurred very recently and is not visible in most satellite imagery yet. Since this may be too complex (at least for me) to map out from field notes alone, I may message you when Esri or Mapbox put out new imagery, if I need a hand updating the relations for a few routes like the S79.

Thanks again for taking the time to polish up Staten Island's transit map!

Thanks for the tip. Hopefully there's some decent data visualization features I can utilize in the app. I want to be sure I don't leave any roadways or terrain polygons inconsistently tagged, but there's definitely a lot to keep track of. 😅

I getcha. This wasn't just about the render, though I see how you inferred such from the edit-description. This was more of a minor "groundwork" edit.

I have to add surface data in a future edit, and it would not be ideal to have the pedestrian area (to be tagged as concrete) overlapping the parking lot (to be tagged as asphalt).

I really appreciate it! Been wanting to tackle this behemoth of a shopping center for months. Once I finish the mall's final parking lot section, outdoor plaza, and pedestrian features, I plan to open a discussion on the OSM Reddit to address any other possible oversights.

Alright. I'll take care of that. Should be an easy fix.