Hi. Why did you add a (Y) to the end of the name for the library? ( osm.org/way/58217608#map=19/53.38421/-6.25459&layers=N )

Hi. I'm not sure what the little area here is ( osm.org/way/248976665 ), but I've removed it because it didn't make much sense

Yes that's incorrect. The Beara Way is a long distance hiking route around this pennisula ( http://www.irishtrails.ie/trail/Beara-Way/3/ ), So it should be tagged as that

The OSM wiki guidelines for `waterway=riverbank` imply that there should be water there. But I can't see much on the aerial? It looks like there's grass there.... What am I missing?

Ummm... I don't think this ( osm.org/way/178568122#map=19/35.14644/-85.27930 ) is a castle, I've changed it here ( osm.org/changeset/48622632#map=6/32.559/-90.407 )

Is this riverbank correct? It doesn't look like the river is that large in the aerial imagery....

Hi , you mapped lots of little campsites around here, But are they all separate? Or are they all part of one big campsite?

Hi. I noticed you added Martin's Castle. You tagged it as `historic=castle`, however I've undone that ( osm.org/changeset/48589873 ) because `historic=castle` is supposed to be for things that were used a long time ago as fortifications, not just things that /look/ like castles. :) Hope you understand.

Hi! I notice you've changed some of the railways so that they are tagged `historic=Chesapeake and Ohio Railway`, but that's not the correct usage of the `historic` tag, right? What are you trying to map here? Is the old name "Chesapeake and Ohio Railway" or something?

Hi, This looks like an import? What's up with the Red/Green/Blue tags you have added to many objects (e.g. here osm.org/relation/5654088 )? That doesn't look like real data/real tags

🙌 😀 Yay for improving the map

Well, let's get philosophical. *What* is "Somerset"? Is it just the building? then add the name tag to the building. Is the whole residential area called Somerset? Then you could draw a `landuse=residential` and add a name tag to that.

Cool. Yes, just because something is called a "castle" doesn't mean it fits `historic=castle`. e.g. the 'castle' at Disneyland is probably not a real castle.

Is it a hotel/guesthouse? Maybe tag it as that? If not you could just add the `name=Somerset` tag to the building way ( osm.org/way/440611516 ). Buildings can have names on their own. y'know

Hi! Welcome to OSM! I don't think this (
osm.org/node/4714336589#map=17/37.13085/-92.10311 ) is really a castle, so I've removed it...

Is the node ( osm.org/node/4383812974#map=18/42.41104/-88.53767 ) really a castle? Should it be tagged that way if it's not a real castle?

Hi! Welcome to OSM! I noticed you added a few things, which I don't think are 100% correct.... You appear to have tagged your house as a castle. I've remove that here ( osm.org/changeset/48332958 ) because when we use `historic=castle` we want that to mean an actual castle. Your home might be your castle, but that's not what most people want when they look for castles! :)

You also added 2 nodes without adding any tags to them ( which I've removed osm.org/changeset/48332968 ). It doesn't really break anything to have untagged nodes, but if you can't say something about them (ie. add some tags), then it probably don't need to be in OSM.

If you have any questions, don't hesitate to ask. Everyone starts off somewhere :)

So there are many ways to solve the "country borders in the sea" issue. Paul Norman has written osmborder ( https://github.com/pnorman/osmborder ) software which allows you to extract the borders as linestrings and will mark if a border is maritine or not. Instead of drawing a blue map and putting land on top as white, you could draw a white map, and put the sea on top in blue. If you order your admin borders right, the blue sea shapes will cover it up. You can get water polygons from openstreetmapdata.com ( http://openstreetmapdata.com/data/coast ), a site from Jochen Topf & Christoph Horman.

I haven't looked into your changes in detail, but I'd advise caution. Many places use osm administrative boundaries, please don't break it for other people.

If you need any help with implementing this other solutions, feel free to ask. :)

No probemo! :)

I was thinking of examples like this: osm.org/node/4672356418/history and osm.org/node/4672356419/history (which were actually in another changeset). :)

Hi there! You've added a few duplicate nodes in this (and other changesets) in this area. I'm not sure how it happens. But it means there are nodes right on top of each other. I'm fixing them up with JOSM. It's no biggie.