GOwin's Comments
Changeset | When | Comment |
---|---|---|
37428405 | over 9 years ago | Thank you for the prompt response. Much appreciated. I brought this changeset to the attention of some of the local OSM mappers and mentioned that it's premature to modify the boundaries based on a bill. Please check out the `proposed:` life cycle tag prefix which seems appropriate in this case: osm.wiki/Lifecycle_prefix With reference to Agusan Marsh, as a protected area, the Ramos-era Executive Order is the prevailing law, and defines the AMWS boundary. The marsh, as a natural feature, is still undefined until we obtain better data or imagery. Please join the informal, online discussions of the local OpenStreetMap community at http://is.gd/osmphchat Sorry for the short reply. I'm mobile. I'll elaborate when I get back to my computer. |
37413232 | over 9 years ago | What do you mean by your "Fix me" comments? What kind of help do you need? |
37428405 | over 9 years ago | Hello. Can you provide a link to your source? This appears to be just a *bill* and is not a law, and will not have any legal weight. |
37321139 | over 9 years ago | Hi Eli. It's not necessary to tag hydrants with name, like
For details, check out:
Great to see you using OsmAnd now. :) |
35677966 | over 9 years ago | What are the sources of these edits? |
37118053 | over 9 years ago | Try this grid, Lucas: http://tasks.hotosm.org/project/1509#task/62 |
37239025 | over 9 years ago | As long as the data you're mapping is on-the-ground, and can be validated, i don't see why it should be a problem. |
37242448 | over 9 years ago | what do you mean by "this edition" and what "important study" are you referring to? |
37118053 | over 9 years ago | Hello Lucas. You might want to wait for the Paypay tasking before you update this area, which should utilize the new MapGive imagery. |
37174889 | over 9 years ago | Am glad to see you still mapping! If you're looking for mapping tips, check out the wiki pages: * [PH Mapping Convetions] (osm.wiki/Philippines/Mapping_conventions)
For questions or concerns, you may reach out to other OSM-PH contributors through any of the following: * [Discourse Chat](https://goo.gl/X2XeQE)
We all look forward to more edits from you. Please feel free to get in touch any time. Regards,
|
36904555 | over 9 years ago | Here, check out an existing route:
|
36904555 | over 9 years ago | Cool! I hope you'd complete the Green Frog bus route relation, too. :) For your reference: osm.wiki/Public_transport#Buses If you need anything, ping other mappers for a hand:
|
36874534 | over 9 years ago | Are you sure about that tag for a "stage"? A public building looks alright, but a `shelter` doesn't look appropriate.
In the Philippines, a "stage" is probably best tagged as amenity=theater. |
36871993 | over 9 years ago | @rukku
|
36871739 | over 9 years ago | @rokku highway=bus_stop tags are not incorrect, and is usable for routing apps and software. If this node is also a shelter, simply add:
Removing bus_stop is unnecessary. Kindly revert, and simply add the shelter tag. For reference, see: osm.wiki/Tag:highway%3Dbus_stop Thank you. |
36871993 | over 9 years ago | Rukku,
|
36753743 | over 9 years ago | Name tags are not necessary to tag features, so there is no need to add them, as is the case here. In an ideal network route map, both physical railways can be added. But, taking advantage of the flexibility of OSM relations make this unnecessary. I hope I understood your question correctly. Thank you. |
36753743 | over 9 years ago | @vichwinn re nodes tagged as `public_transport=stop_position` are not, at all, superfluous. It may appear like that in OsmAnd (which, btw, I use and recommend, too) but those nodes are functional and exist in the real world, and follows the OSM precept of `one feature, one element`. The only reason those "dots" are not visible in other stations is that they haven't been mapped yet. Besides, we never, ever should map for the "renderer." The mapping process is never complete, and the OSM platform generously allow us to store these data, even if they're considered as work in progress. As for the case of stations being stop positions by default, that is not always a safe assumption. We have (or used to? I dunno these days) LRT "express trains" that only load/unload passengers on select stations. A *completely* tagged public transport route, can make use of stops, routes, trips, schedules, etc. to develop "ideal" routes. OSM data is not just used for rendering maps, they are also usable for many other routing apps - elements of which are not always visibly apparent for other users - but the data, the building blocks are there. If you feel this case needs to be discussed more extensively, we have several community channels where this can be done: * [Chat Room](https://goo.gl/X2XeQE)
Kindly consider reverting the affected changesets. |
36297070 | over 9 years ago | Nice to see you mapping again, Mars. :) Happy new year. |
36292688 | over 9 years ago | Hi Albayano. Kindly spell out "St." as "Street", per OSM naming convention, we don't abbreviate. See here for more: osm.wiki/Editing_Standards_and_Conventions#Don.27t_use_abbreviations |