HikeAndMap's Comments
| Changeset | When | Comment |
|---|---|---|
| 145996146 | over 1 year ago | Same here, why would we do pole:colour instead of colour:pole but we do colour:text, colour:back, colour:border, etc. Seems inconsistent to me.. maybe it's not, maybe there's a logical reason which I'd like to know. Thank you
|
| 145996139 | over 1 year ago | Hi there, may I ask why you changed the colour:pole into pole:colour? It is my understanding that we need consistency on OSM? We have colour:back, colour:text, colour:border, etc. So why would we do pole:colour now suddenly instead of colour:pole? I thank you in advance for explaining this to me.
|
| 148524826 | almost 2 years ago | good one! I didn't realize this one but yeah it's paving stones as surface and material marble |
| 145290878 | almost 2 years ago | We recommend not using the "-" and just write
|
| 145285398 | almost 2 years ago | Please keep in mind Baguio is administratively not part of Benguet. The boundaries are set properly on OSM with official data from the Assessor's office, which comes from the DENR.
|
| 145284298 | almost 2 years ago | Hi, again, please read the wiki articles on relationships. We don't add road infastructure relationships to churches ;) Again if you wish help - I'm in Baguio I can live show how mapping is done properly. I'm always willing to help newcomers.. telegram: HikeAndMap
|
| 145283285 | almost 2 years ago | Hi there, thanks for joining OSM! Please continue mapping :) There were some issues with syntax which I corrected. Also please follow the general rule 1node/way/polygon per 1 feature. That's not mandatory, but it's advisable. Please if interested in continuation of mapping, I live in Baguio too and can assist you finding your way in the mapping jungle. If interested feel free to contact me on
|
| 145283123 | almost 2 years ago | Hey, thanks for your contributions to OpenStreetMap in Baguio. I also live in Baguio and always willing to help new mappers. If you like I can show you how to use JOSM and how the wiki works, because it can be kinda of a jungle to be honest LOL Feel free to contact me, I'm also in Baguio and a more seasoned mapper. telegram: HikeAndMap
|
| 145254286 | almost 2 years ago | Hi there, thanks for the contribution! And please do keep mapping! I'd like to ask you if you change a building, please don't delete the original polygon. Just adjust it, so we keep track of changes. If you delete a building, it's going to be hard near to impossible to figure out the history of the object and what mappers over time did with it. If you need help how to map buildings, correct them, without destroying the history to the object, I'm more then willing to show you how to do that properly. Feel free to contact me if you'd like some guidance how to map. telegram: HikeAndMap
|
| 145237052 | almost 2 years ago | Hi there, thanks for the contribution! Please do continue adding data.
Most importantly are actually house number and street name, so if you're not sure, then just add those two additionally to the addr:city tag. Anyway, thanks for the contribution and please do keep mapping :)
|
| 145098850 | almost 2 years ago | Hi Mae, thank you for joining mapping! But please before changing information first check the wikipedia on mapping. There's some correct information which you replaced with false information. No problem, I'll rectify it. Please reach out to me if you're into mapping and I'll help you with the starters.. I'm located in Baguio and we're always happy with new mappers so please contact me. Feel free to contact me on my mappers account HikeAndMap on OSM
|
| 144716306 | almost 2 years ago | Hi there, please don't set these to "limited' you really don't wish to go into a jeep with a wheelchair! We're talking about lifting the wheelchair 1m at least and squeezing it through a narrow opening. What are jeeps?
you wouldn't want to try to get into one with a wheelchair.
|
| 144581142 | almost 2 years ago | Hi, I dare to contest the "no" as there are cars actually driving there so I suggest there's at least permit/permissive status. What's the source of your information?
|
| 146932746 | almost 2 years ago | Hi thanks for fixing this one. Back then I wasn't sure according to the data privacy act if we're allowed to add personal private names to commercial establishments. Now I know we are allowed for commercial. Thanks for fixing this
|
| 146932759 | almost 2 years ago | Hi thanks for the contribution. The ***** stands for a personal private name part of the company. Back then I wasn't sure if we are allowed to add that information due to the data privacy act. The real correction is not to remove the **** but to add a fixme something is missing here) In this case since I live here I know it's Oto Mike.. I'll do that then and correct that - now I know for commercial establishments we are allowed to add the full personal private names thank you and please keep helping OSM :)
|
| 144462847 | about 2 years ago | Hi can you tell me why you changed this from "no" to "limited" ? The step into PUJ here is definitely >7cm, more like 20-30cm or more. And putting a wheelchair into the Jeeps.. I think you'll find out it's going to be impossible even if you get assistance from 2 or 3 adult male. Thanks for looking into this
|
| 144462852 | about 2 years ago | Hi can you tell me why you changed this from "no" to "limited" ? The step into PUJ here is definitely >7cm, more like 20-30cm or more. And putting a wheelchair into the Jeeps.. I think you'll find out it's going to be impossible even if you get assistance from 2 or 3 adult male. Thanks for looking into this
|
| 141758678 | about 2 years ago | btw the values are not JOSM estimated by surveyed and measured locally using measurement tape. So it's fairly accurate. And the data provided to me by the field teams is in cm - how they always end up with a nice 0 at the end is beyond my knowledge - but I follow the osm.wiki/Map_features/Units here which says if the data provided to you is in 2 digits after the decimal delimiter then that's how you enter it into the database so that's what I do. Because to the best of my knowledge that's the data available to me. |
| 141758678 | about 2 years ago | As some more information for you why the colon isn't just restricted or limited to languages: width:carriageway
I really see a wide-use tendency here to use colons for a lot more descriptions than just languages |
| 141758678 | about 2 years ago | Hi thanks for answering! Yeah I know the key maxwidth - but that's a different meaning. It's the maxwidth for vehicles to pass through. That's not the case here, width:max describes the maximum width of the physical properties of the road. width is the basic width of the road. or minimum width, if any, maxwidth (for vehicles) would reflect exactly that. ehm, rephrase:
width = physical width of the actual object/polygon in this case roads. the widths I enter are" from width" to "width:max" as physical description to the object. I see no such description in the wiki, as the wiki only uses "width" as physical description and no other keys. if you are aware of other keys - I'll happy to learn about them. I think why you see 47k maxwidth - because I use them too according to the wiki, is because they describe the legal per traffic sign maxwidth for vehicles, most mappers will map that for sure, as I do too. but again - this is about the physical properties of the road itself, and not the legal max width for vehicles. And I think most mappers don't map that detailed to go into that depth for mapping physical reality on the ground as to say the road is "from" and "to" when it comes to width. But physical reality on the ground is a core principal of OSM right ;) as for the :... where after the colon should only be a language key - that's new to me. There's so many examples on osm where colons are being used for a lot more than just languages. Everywhere throughout the wiki I see colons being used for other tag definitions than language. It's new to me this is restricted only to languages. A good example here, to stick with the widths, would be: maxwidth:physical here too after the colon is not a language. Sadly this again describes basically the maximum for the objects passing through - not the actual physical maxwidth of the object. I think generally this is on OSM missing, but please point me out the proper keys if you know them, the proper maximum and minimum of the physical width of the object itself .. not from the perspective of the object passing through. Thank you for contacting me about this. you're right the width:max is ambiguous in its meaning, so is the maxwidth:physical since it isn't really the physical property of the object but basically the same as simply maxwidth but the width:max I'm referring to is really different from both maxwidth and maxwidth:physical - hence I'm using it since it's not the same. |