https://en.wikipedia.org/wiki/Non-motorized_access_on_freeways
Wikipedia states that in Washington, bicycles can use interstates wherever they are not specifically banned.

According to national standards, bicycles are *only* allowed on interstates in some few cases where using that interstate is the *only* way to get from one point to another without a huge detour (such as 100 miles). Bikes (and mopeds, horses, etc.) are not allowed on most interstates.
I think that bicycle=no might be better fit than bicycle=discouraged, but it doesn't matter too much. Choose whatever you think is most appropriate.

That's not a huge issue. I do have a suggestion, though: use iD for tasks like this one. iD recently was updated to include a new type of validation that can automatically convert POIs tagged with names of chain stores into those chain stores. It adds the correct tags, such as amenity=fast_food, and also wikidata and cuisine tags as appropriate.
Thanks for contributing!

Tak! Det havde jeg vidst ikke lagt mærke til.

> Like I said in my other comment, you don't have to add anything above addr:street, since most software will "guess" it by using the surrounding boundaries.

In many places, the administrative boundaries don't match the postal boundaries, so adding addr:city is actually very useful. addr:postcode isn't currently added as areas in osm, so it's always a good idea to add it too.
addr:state, however, is not very useful, but adding it does save data consumers the additional step of adding it before they use the data.
I've imported 300,000 addresses and have helped with importing 500,000 more, and I made sure to include addr:city and addr:postcode on every single one.

I've been mapping subdivisions like this: osm.org/way/338345923

I see no problem with this, but would recommend also adding place=neighbourhood to the landuse polygons.
Thanks for your contributions!

> 1. If decide to put a bee hive in my backyard that I then cultivate honey from to sell at the local farmers market (which my city permits me to do), in your opinion would it then be better to re-tagged my property as landuse=farmland from landuse=residential?

I have bee hives, and I've marked my neighborhood as residential, just like it should be :)

"squared" is probably the wrong word for this - iD let's users "square" buildings by taking almost 90° angles and making them 90°. Complex shapes aren't just turned into 4 nodes squares. If a T shaped building is now a square shape, it's because it wasn't T shaped to begin with, and the contributor simply didn't notice that.

Fixed!
osm.org/node/4657748074

Hi,
I've added Domain Pest Control back to the map.
osm.org/node/6475197483
The reason that it got deleted was that it had some incorrect formats for the opening hours and address, which is hard to avoid if you're not familiar with OSM. The bot edit that deleted it is trying to help mitigate the companies that add thousands of low quality edits about businesses, and your edit seems to have been a false positive.
Thanks for contributing to OpenStreetMap!

That's awesome! It's amazing how many unexpected uses there are for OSM data.

Floodplains should not be mapped as wetlands - there is a proposal for mapping them here: osm.wiki/Proposed_features/floodplain

Also, it appears that most of the addresses you've imported don't have addr:city or addr: postcode. These tags are very useful for ensuring that no two addresses are duplicated. This isn't the biggest issue, but if the source data has this information, it should most certainly be added.

Jeg har forresten en spørgsmål: jeg har skiftede nogen af vejene med tagget crossing=zebra om til crossing=marked, of har tilføjet nogen nye med crossing=marked + crossing:signals=yes I stedet for at bruge crossing=traffic_signals. Er det OK, eller skal jeg skifte dem til crossing=zebra & crossing=traffic_signals?

OK. Jeg vidste om botten, og at den kun virker vis adresserne er noder, så jeg har ikke gjort adresser om til områder. Tak for tippet om SDFE luftfotos! Jeg havde nogen problemer med at skifte til SDFE halvvejs igennem andresætet. For en aller anden grund blev laget helt sort når jeg zoomed inde mer an z17 eller 18.
Tak for kommentarerne!

^ Incorrect comment. Actual comment: Added landcover and fixed JOSM validator warnings.

First off, this wasn't really a mechanical edit. I used the ToDo plugin for JOSM to allow me to paste the tags to each object individually, and I fixed a ton of inaccurate data in the process. The reason for using the ToDo plugin was that many of the areas (and occasionally non closed ways) were actually lakes, ponds, streams, or basins. I did not want to mistag anything.
"osm.wiki/Tag:waterway=riverbank is not officially discouraged" - interesting. I had read in some water related wiki page that it was, and for some reason thought that page was official. I'll try to find it again if someone hasn't changed it.
The reason I have seen for using natural=water + water=river is that there would be fewer tags for data consumers (like Overpass turbo users) and renderers to use: landuse=pond, landuse=basin, landuse=reservoir, waterway=riverbank, and natural=water are all rendered the same way in most maps.
Thanks for contacting me,
Leif

osm.org/changeset/68231317

Yikes, I thought that I had caught all of those. That key was accidentally created by me when using the Todo plugin in JOSM to scroll through each crossing. Using ] will go to the next crossing to add tags to. Unfortunately, I somehow added that character as a key to some crossings. I'll delete them now.
Thanks for noticing that!
Leif