thanks for replying and giving OSM a go! remember that OSM data needs to be publicly verifiable--if these addresses are not used publicly, they're not verifiable (and probably wouldn't be of much use to people anyway). if the platforms have different addresses, then the address should be on each platform itself (ie way/126228993), not on the station node. transit tagging is not the easiest, but if you have an interest, I think the consensus these days is found at osm.wiki/Proposed_features/Public_Transport (actually, looking at that, I wonder if the station nodes should be turned into ways covering the whole area?) cheers!

some questions: 1) what is the source for the addresses you added for these platforms? even station data from Metro Transit doesn't have an address. 2) you repurposed the general Snelling Ave station node into something just for the EB platform, which is different from all other MT LRT stations--is there a reason for this? thanks

Hi, just an FYI, if you're testing for an import, you'll want to check out osm.wiki/Import/Guidelines If not, for future I'd recommend camel-casing attributes (such as city name and street names), and making sure street names are unabbreviated. Either way, thanks for adding to the map!

This is advertising through vandalism. I am deleting the tags you added to this way.

hi, just wanted to let you know that the best tag for fitness centers is leisure=fitness_centre (see osm.wiki/Gym_/_Fitness_centre)

hi, just wanted to let you know that the best tag for fitness centers is leisure=fitness_centre (see osm.wiki/Gym_/_Fitness_centre)

Noticed that you are tagging some areas around farmhouses with landuse=grass. this seems incorrect on two counts: 1) farmhouses should be included in landuse=farmyard landuse=farmyard, and 2) landuse=grass is for public space, not private landuse=grass. Maybe you want to use surface=grass or landcover=grass for these private grassy areas instead?

it appears many of these buildings are duplicates of your previous changeset--it'd be great if you could take a look and correct (for ex, on S 5th btw Bridge and Ferry)

wow, are you planning to do all of these? :)

Cool idea to put in construction dates for these buildings. I'd suggest spelling out Hennepin County in the source:building, though

Hi, this edit seems more like advertising than entering actual verifiable data: 1) it doesn't include OSM tags for what "Web Design in Minneapolis" supposedly is (office? shop?), 2) this node is in what looks like an apartment building, 3) a similar node with same phone # was entered recently in this changeset changeset/35981007, which also seems to be in a residential building, 4) the overly long description (and "keywords" in the other changeset) are not standard OSM practice. I suggest you see osm.wiki/Good_practice for some tips on this, and make some modifications to your nodes.

I changed the tag on this to amenity=dojo based on the name, but later realized this might not be accurate. if it is indeed a multi-sport sports centre (leisure=sports_centre) then please change it back!

I did not, but that would be a better plan. Thanks for the reminder!

Hi, curious why you put access=no on this way. This seems counter to what you stated in your changeset comment about improving routing. Is it under construction or something?

Welcome to OpenStreetMap, and thanks for contributing! Please remember that information you add is for all users of OSM data, so your changing the name of the building from "Parklawn Estates" to "Home" is not helpful and actually removing information from the map. Looks like there might still be plenty of other things to map in this area, though!

shop=shopping_centre is rarely used, probably because it's not really clear what it means (sparse wiki page) and therefore what information it adds beyond the landuse=retail tag. thoughts?

Hi, I think the tag for fitness places is coalescing around leisure=fitness_centre (see osm.wiki/Gym_/_Fitness_centre)

Thanks for fixing, hope it didn't confuse anyone that was going to maptime! :)

Thanks for fixing this! I made these relations and just saw the error via OSMI, but you beat me to it. :)

1) calling your attention to the messy golf course outline (see http://tinyurl.com/psrj2jy), and 2) a reminder that it is best practice in most cases to NOT attach landuse nodes to the highways surrounding them (see here for a logical explanation: http://tinyurl.com/qhr4gla)