When we arranged the import, we knew that the buildings were slightly misaligned from Bing. However, we knew that Bing was likely to be the one offset. Plus, the misalignment was very slight, so we considered the city data authoritative. It's possible that the city data is also offset, but I warn against changing it, only because it would result in inconsistent alignment with the rest of the city. Aligning everything to Bing would mean reviewing and offsetting every building in the city.

The address does show up in the city's address database (https://gis.sanjoseca.gov/maps/publicgisviewer/?view=desktop).

This changeset also moves the building to be misaligned from all of the surrounding buildings.

If 2922 Saint Florian Way isn't here, then where is it? This seems like potentially useful information that could be fixed rather than just removed.

This changeset spans a very large geographical area. Please try to keep your edits local by clicking "save" before moving to a new location.

Please don't reuse nodes from a road to define a woods boundary. Please learn to delete bad data instead of making it worse.

This, or another one of your changesets, seems to have broken the continuity of the San Jose border, at least in Overpass. Can you fix it? I don't have a validator on hand to tell what's wrong but I did notice that way ID 777559010 sticks out, and might double back on itself as well.

Why did you move the existing bike shop out of the way and then add a duplicate?

On the wiki and elsewhere, an asterisk ("*") is usually not literal, rather it means that that part of the tag can be anything, and a literal asterisk is incorrect. I've changed this to highway=residential to match the surrounding roads.

Hello. Thanks for your contributions. Please consider using more descriptive changeset comments, so that other mappers can know what you changed at a glance. It doesn't have to be detailed, something like "Add access restrictions to paths," but just "updates" doesn't really say what changed or why. See here for more information: osm.wiki/Good_changeset_comments

Hello! Thanks for helping out with the SDP import. Unfortunately it looks to me like you've added the name of a boutique to an apartment building. Normally if there are multiple POI in a building, they would each be their own object, rather than one on the whole building. And each point should have more descriptive tags than just a name. Finally, it looks like this could just be a residential address, in which case we don't need business information on it at all—I try to use street-level imagery to confirm these cases.

Did you really reuse a farmland as a lake? I guess they're sort of next to each other but it's not like the farm was flooded and then teleported. It would have been better to just delete the bad data than to make it worse.
---

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

Just so you know, there was some discussion in changeset 96645593 about a railway crossing you added back in as way 963292609.

Perhaps it's technically related in that it's still a wooded area, but I still don't like that way 39641899 and all of its nodes were relocated from somewhere else. An easy way to fix it without damaging data would have been to use JOSM's "Join overlapping areas" feature, then drawing the new wooded area separately.

That's one idea. There are lots of things you can do to improve the map by just adding tags: researching business contact information, adding etymologies, fixing deprecated or conflicting tags—Maproulette has plenty of "tag fix" challenges. You could also stick to using the in-browser iD editor, which makes it harder to make mistakes like these.

This appears to be the wrong location. You added the point to a house on Ramita Court, but my search says that it's on Hamilton Avenue.

This changeset changes a wetland into a woods in a different location. Please don't reuse objects for unrelated things.

Reverted in changeset 108830757.

There is clearly some sort of road here visible in imagery. The City of San José also has a rural access road here in their database. Perhaps it is not named that, or it is not public access, but those things can be fixed without removing it from the map.

This changeset used nodes from a forest to create street-lining trees. Please do not reuse nodes for unrelated objects.