Hola,
porfa no pongas todos los nombres en mayusculas. Queda más difícil a leer. Vease tb osm.wiki/ES:Nombres#Caracteres_en_may.C3.BAsculas

saludos,
Matthias

El camping Sam Miguel está en el medio de la calle?!

La posición me parece equivocada, no se ve nada ahí en Maxar. Será que es más al sur al lado del rio?

Hi,
natural=water is not wrong for reservoirs, AFAIR the recommended tagging is both landuse=reservoir, reservoir_type=water_storage *and* natural=water water=reservoir.

cheers,
Matthias

As I said, please don't invent your own tags. I see you're trying to add something very detailed, obviously with good will and a purpose, but in the context of OSM this is mostly garbage data that other people can't use. "building=abandoned" is deprecated in favor of "abandoned:building=house"; "building:category_of_the_house" doesn't exist; neither does "building:floor_area", and it doesn't even have a value that would count as machine readable. "building:ownership=owner" is completely useless (who owns a house? well the owner of course, who else?) and "building:state_of_the_house=permanent" is redundant - a house is a permanent structure in OSM, otherwise it's a shed at best but probably not something that should be mapped in the first place.

cheers,
Matthias

Hi Ruminda,
please don't invent your own tags, stick to tags and, where applicable, values documented on the wiki. If you're doing data entry on behalf of an LGU or something, please coordinate on whether you could use an own namespace or something. Chances are much of this data (e.g. "building:ownership", category_of_the_house or state_of_the_house) doesn't really belong in OSM anyway though.

cheers,
Matthias

Hi,
have you checked these on the ground? Would be good to have a name for the restaurants and at least a religion for the places of worship.

Cheers,
Matthias

Careful when iD gives you warnings about crossing highways and such, they usually have to be fixed! It may look sort-of OK on the rendered map but routing gets confused and generally a map like this will not be very usable.

cheers,
Matthias

Hi,
I suppose things like psychiatry are not exactly a specialty of the government veterinary? I changed it to amenity=veterinary; healthcare=* is for humans.

cheers,
Matthias

Hi Aurore,
for information like this, you can just open a map note. "tourism=information" is meant for signboards or information offices that exist as physical objects. For yours, I just added a "direction" attribute to the paths leading to Yensabai and Tad Mook.

cheers,
Matthias

Oops, sorry, disregard that - just noticed you were the one who fixed some of the mess Karunanithy1973 made :)

cheers,
Matthias

Hi,
please don't use descriptive pseudo-names like "Road" or "Path".

cheers,
Matthias

Hi, are you sure about that classification change? Would be nice if you added a bit more descriptive comments to your changesets, because you can't really see from Bing whether something is a tertiary or secondary road.

cheers,
Matthias

Hi, thanks for your additions!
You don't have to use so many nodes though - if a stretch of way is straight, additional nodes don't add any useful information, they just increase the data volume. Also, please make sure to actually tag your ways and possibly connect them to existing streets, otherwise they won't be very useful.

cheers,
Matthias

Careful with the tag values, they are case sensitive! junction=yes works, junction=Yes doesn't. I just fixed it.

Hi,
careful, I just checked with several aerial images, and those don't appear to be roads at all, they're canals! You can distinguish them by the dark color; highways are usually unpaved and dust/sand-colored in this area.

cheers,
Matthias

Hi Nilantha,

that's somewhat unusual tagging there, please don't do it like this. For one thing, "0+647" is surely not the name of the stream as local people know it? If it's some reference number from watershed management, it should go into a "ref" tag. The other thing is, there are separate tags to map a culvert. The culvert is a section of the stream, not part of the highway, so it shouldn't be tagged on the highway. Just make a separate section of the stream and tag it layer=-1 (so we know it's *under* the highway - if you had an aquaeduct it would be on a layer above the highway) and also add "tunnel=culvert". That way it's even properly rendered on the map instead of scattering obscure numbers all around.
I've done it for the stream you just added.

cheers,
Matthias

Hi Nick,
highway=unclassified is a bit of an overstatement for these ways. Maybe they could pass for tracks or living streets (surface=unpaved smoothness=bad/very_bad) but most seem barely suitable for an enduro motorcycle or an offroad jeep. An unclassified highway is expected to have some through traffic, too. If something is just an access to a residence, highway=service, service=driveway is a good guess.

cheers,
Matthias

Hi Dimesh, thanks for your additions!
Keep ind mind though that nodes on a straight way don't add anything useful - you can get basically the same rendered result with fewer than a quarter of the nodes you used. Have a look how it is now that I used JOSM's "simplify" function on your ways. Also, fewer nodes means an easier job for the renderer, faster routing and less data to download for offline maps.

cheers,
Matthias

Hi, thanks for your additions!
I noticed you're quite generous with the "highway=unclassified" tag. Most of those I'd say are residential streets at best - unclassified highways are usually interconnections, and something being a dead-end street is a pretty good indication that it's not on the unclasssified level.

cheers,
Matthias