Re: [talk-ph] intro to Kaart initiative in PH
Glen, thank you for sharing. Road surface types, and lanes, is one of the attributes we hope to collect and add into the the OSM database. The challenge of "how" to collect these, is another matter altogether. We have limited street-level imagery (and that's one way of doing that), and in many urban areas, users can use aerial imagery to distinguish paved and unpaved roads. /Erwin On Wed, Jan 17, 2018 at 7:13 PM Glen Scottwrote: > Nothing to offer by my own personal experiences > > I'm a regular user of GPS for navigation at home (Australia) in urban and > country environments. I've noted in OSM (Philippines - specifically N-W > Pangasinan) two things that are undefined in 99% of roads, but used by the > routing engine - road surface and speed limit. With 99% of roads undefined > for surface and speed limit the route chosen by the GPS will be a lottery > as far as driving experience goes. I guess the most critical would be the > ability to chose to avoid unpaved roads? I've had a number of Garmin GPSs > and they always assume 80 km/h where the map has no defined limit. Maybe > 10+ years ago I had some experiences where the GPS would attempt to take me > on "short-cuts" over long-unused dirt tracks (in preference to the > highway!). I guess this is the potential result of not defining the > surface at the very least. Hard to tell the speed limit from satellite > imagery! > > In the urban environment the most common and frustrating errors (Garmin > maps) would be undefined one-way streets. > > My one attempt to navigate in the Philippines on OSM (~2008-2009) led me > into a military camp and some interested military personnel who directed me > back out the way I came in! Gates are important but no always so easy to > see from space > > Cheers > Glen > > On Wed, Jan 17, 2018 at 5:40 PM, Erwin Olario wrote: > >> >> Thank you for bringing this up, Maning. This is also a concern I've >> discussed with other mappers in the past, and this doesn't just apply to >> road navigation, but with other features, as well. >> >> The Mapbox data team is a pioneer in this road network initiatives in >> OSM, and we look up to your team for inspiration. >> >> Our current (in the next few months) interest in PH road network >> improvement are low-hanging fruits (missing geometries, restrictions, >> turning lanes, etc), but in due time, we'd like to explore how to further >> improve road network data from OSM for naviation, etc. PH is only one of >> the many countries we're working in, so we need a more inclusive >> understanding of tagging nuances, too. >> >> I hope such a discussion can attract more inputs from the wider >> community, especially those who've been lurking in the background, who >> follows the exchanges here, but for reasons known only to them, doesn't >> engage publicly. >> >> /Erwin >> >> On Mon, Jan 15, 2018 at 8:35 PM maning sambale < >> emmanuel.samb...@gmail.com> wrote: >> >>> Hi Erwin, >>> >>> Thanks for leading this work. As many of you know, I work in Mapbox >>> and my primary focus is to make OSM navigable. >>> I wonder what would be the best approach in the context of driving in >>> the Philippines. >>> Would love to share notes and approaches. One thing I have in mind (I >>> shared this during the meetup), while every country >>> has specific nuances tagging, there is a danger of making the tags too >>> specific as its difficult to create routing engines for each country. >>> >>> >>> On Thu, Jan 11, 2018 at 11:58 AM, Erwin Olario wrote: >>> > Happy new year everyone. >>> > >>> > In case some of you are wondering about some of my recent changeset >>> comments >>> > with the phrase, "Better PH data with #Kaart", I've recently linked >>> up with >>> > Kaart [0], and their initiative to improve OSM data in the Philippines. >>> > >>> > One of the things we'd like to tackle is road network improvement, >>> initially >>> > in Metro Manila, and later (maybe soon?), expanding to other regions. >>> > >>> > Improvements that are intended to be addressed include the following: >>> > * Adding missing roads >>> > * Improving road attributes (names, lanes, restrictions, etc.) >>> > * Correcting road connectivity issues >>> > * Improving road classification consistency according to OSM >>> guidelines and >>> > local convention >>> > * Correcting road alignment issues >>> > * Other one-off fixes >>> > >>> > Of course, we intend to work closely with the community, and other >>> > stakeholders, especially at the local level. >>> > >>> > We also hope to organize, or lead, activities for developing technical >>> > skills, and enhancing collaboration, and community mapa-thons. Think >>> of >>> > this as an extension of my earlier MapAmore [1] initiatives. >>> > >>> > The tasking for Metro Manila [2] is now up, and is hosted by HOT >>> Tasking >>> > Manager instance, and open to all interested contributors. >>> > >>> > In tomorrow's
Re: [talk-ph] Mayon Volcano Eruption Jan 2018
The objective of the area I created was to include evacuation centers I mapped before that were used by APDRRMO in 2014 [0] for the phreatic eruption event plus covering the pyroclastic flow and lahar flow hazard area released by PHIVOLCS [1]. Might be a good idea in the future to map it for navigation to the evac centers and escape routes too. [0] http://www.s1expeditions.com/2014/09/164-mayon-2014-zones.html [1] https://reliefweb.int/map/philippines/philippines-mayon-volcano-hazard-map-and-population-16-january-2018 Ervin M. Schadow1 Expeditions On Wed, Jan 17, 2018, 9:54 PM maning sambale,wrote: > Ervin, > > Thanks, this is so much bigger than the EDZ [0]. I feel its too much > too big AOI for mapping. > If we can have detailed poly that identifies at risk areas, that's much > better. > > [0] > https://user-images.githubusercontent.com/353700/35045993-ab1fce48-fbbb-11e7-9a98-51930ebc17c0.png > > On Wed, Jan 17, 2018 at 6:52 PM, Ervin Malicdem > wrote: > > Here it is, Maning > > > > https://owncloud.cxsmedia.com/index.php/s/xI7M2yqVI0Zrrs0 > > > > Ervin M. > > Schadow1 Expeditions - A Filipino must not be a stranger to his own > > motherland. > > http://www.s1expeditions.com > > > > On Wed, Jan 17, 2018 at 8:46 PM, maning sambale < > emmanuel.samb...@gmail.com> > > wrote: > >> > >> Ervin, > >> > >> > A poly file [0] was created to prioritize its southwest quadrant where > >> > the > >> > magma initially flowed and also to include evacuation centers we > mapped > >> > back > >> > during its phreatic eruption in 2014. I suggest we can also make this > as > >> > the > >> > bounds for the HOT task. > >> > >> I can't find my poly to geojson coverter right now, can you share > >> geojson or shapefile? > >> > >> -- > >> cheers, > >> maning > >> -- > >> "Freedom is still the most radical idea of all" -N.Branden > >> https://epsg4253.wordpress.com/ > >> http://twitter.com/maningsambale > >> -- > > > > > > > > -- > cheers, > maning > -- > "Freedom is still the most radical idea of all" -N.Branden > https://epsg4253.wordpress.com/ > http://twitter.com/maningsambale > -- > -- Ervin Malicdem for Schadow1 Expeditions A Filipino must not be a stranger to his own motherland. http://www.s1expeditions.com ___ talk-ph mailing list talk-ph@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] Mayon Volcano Eruption Jan 2018
Ervin, Thanks, this is so much bigger than the EDZ [0]. I feel its too much too big AOI for mapping. If we can have detailed poly that identifies at risk areas, that's much better. [0] https://user-images.githubusercontent.com/353700/35045993-ab1fce48-fbbb-11e7-9a98-51930ebc17c0.png On Wed, Jan 17, 2018 at 6:52 PM, Ervin Malicdemwrote: > Here it is, Maning > > https://owncloud.cxsmedia.com/index.php/s/xI7M2yqVI0Zrrs0 > > Ervin M. > Schadow1 Expeditions - A Filipino must not be a stranger to his own > motherland. > http://www.s1expeditions.com > > On Wed, Jan 17, 2018 at 8:46 PM, maning sambale > wrote: >> >> Ervin, >> >> > A poly file [0] was created to prioritize its southwest quadrant where >> > the >> > magma initially flowed and also to include evacuation centers we mapped >> > back >> > during its phreatic eruption in 2014. I suggest we can also make this as >> > the >> > bounds for the HOT task. >> >> I can't find my poly to geojson coverter right now, can you share >> geojson or shapefile? >> >> -- >> cheers, >> maning >> -- >> "Freedom is still the most radical idea of all" -N.Branden >> https://epsg4253.wordpress.com/ >> http://twitter.com/maningsambale >> -- > > -- cheers, maning -- "Freedom is still the most radical idea of all" -N.Branden https://epsg4253.wordpress.com/ http://twitter.com/maningsambale -- ___ talk-ph mailing list talk-ph@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] Mayon Volcano Eruption Jan 2018
Here it is, Maning https://owncloud.cxsmedia.com/index.php/s/xI7M2yqVI0Zrrs0 Ervin M. *Schadow1 Expeditions* - A Filipino must not be a stranger to his own motherland. http://www.s1expeditions.com On Wed, Jan 17, 2018 at 8:46 PM, maning sambalewrote: > Ervin, > > > A poly file [0] was created to prioritize its southwest quadrant where > the > > magma initially flowed and also to include evacuation centers we mapped > back > > during its phreatic eruption in 2014. I suggest we can also make this as > the > > bounds for the HOT task. > > I can't find my poly to geojson coverter right now, can you share > geojson or shapefile? > > -- > cheers, > maning > -- > "Freedom is still the most radical idea of all" -N.Branden > https://epsg4253.wordpress.com/ > http://twitter.com/maningsambale > -- > ___ talk-ph mailing list talk-ph@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] Mayon Volcano Eruption Jan 2018
Ervin, > A poly file [0] was created to prioritize its southwest quadrant where the > magma initially flowed and also to include evacuation centers we mapped back > during its phreatic eruption in 2014. I suggest we can also make this as the > bounds for the HOT task. I can't find my poly to geojson coverter right now, can you share geojson or shapefile? -- cheers, maning -- "Freedom is still the most radical idea of all" -N.Branden https://epsg4253.wordpress.com/ http://twitter.com/maningsambale -- ___ talk-ph mailing list talk-ph@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] Mayon Volcano Eruption Jan 2018
Thanks everyone for finishing the task really quick! We have 100% mapped and 57% validated as of this time. Also thanks to the mappers before us who already mapped a lot before this event. We created a new task to include the expanded danger zone [0], reference material [1]. Compared to the previous task, this needs more effort since these areas are more populated than the permanent danger zone. This continues to be a local response, but anyone is welcome to participate [0] https://tasks.hotosm.org/project/4037 [1] http://www.ifrc.org/docs/appeals/rpts09/PHvol221209.pdf On Tue, Jan 16, 2018 at 10:16 AM, Ervin Malicdemwrote: > Schadow1 Expeditions has initiated producing a humanitarian version of GPS > navigation map for this area a few hours after its magmatic eruption in > January 14. > Let me know if the HOT activation needs a daily update for this one. > A poly file [0] was created to prioritize its southwest quadrant where the > magma initially flowed and also to include evacuation centers we mapped back > during its phreatic eruption in 2014. I suggest we can also make this as the > bounds for the HOT task. > > Map is available on site [1] > > > [0] https://owncloud.cxsmedia.com/index.php/s/zEQ1ZAyM9AyTg0b > [1] > http://www.s1expeditions.com/p/the-gps-navigation-map-of-philippines.html > > > Ervin M. > Schadow1 Expeditions - A Filipino must not be a stranger to his own > motherland. > http://www.s1expeditions.com > > On Tue, Jan 16, 2018 at 11:55 AM, maning sambale > wrote: >> >> Mayon Volcano in the Philippines erupted this week. Local community >> is mapping from pre-event imagery. >> This is not yet a full HOT Activation. We are still assessing the >> needs of responders, but if anyone has spare time, >> we have a task [0] ready for the permanent danger zone. This mapping >> is focused on mapping infrastructure (roads and buildings) and >> waterways. >> >> [0] https://tasks.hotosm.org/project/4027 >> >> -- >> cheers, >> maning >> -- >> "Freedom is still the most radical idea of all" -N.Branden >> https://epsg4253.wordpress.com/ >> http://twitter.com/maningsambale >> -- >> >> ___ >> talk-ph mailing list >> talk-ph@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/talk-ph > > -- cheers, maning -- "Freedom is still the most radical idea of all" -N.Branden https://epsg4253.wordpress.com/ http://twitter.com/maningsambale -- ___ talk-ph mailing list talk-ph@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-ph
Re: [talk-ph] intro to Kaart initiative in PH
Nothing to offer by my own personal experiences I'm a regular user of GPS for navigation at home (Australia) in urban and country environments. I've noted in OSM (Philippines - specifically N-W Pangasinan) two things that are undefined in 99% of roads, but used by the routing engine - road surface and speed limit. With 99% of roads undefined for surface and speed limit the route chosen by the GPS will be a lottery as far as driving experience goes. I guess the most critical would be the ability to chose to avoid unpaved roads? I've had a number of Garmin GPSs and they always assume 80 km/h where the map has no defined limit. Maybe 10+ years ago I had some experiences where the GPS would attempt to take me on "short-cuts" over long-unused dirt tracks (in preference to the highway!). I guess this is the potential result of not defining the surface at the very least. Hard to tell the speed limit from satellite imagery! In the urban environment the most common and frustrating errors (Garmin maps) would be undefined one-way streets. My one attempt to navigate in the Philippines on OSM (~2008-2009) led me into a military camp and some interested military personnel who directed me back out the way I came in! Gates are important but no always so easy to see from space Cheers Glen On Wed, Jan 17, 2018 at 5:40 PM, Erwin Olariowrote: > > Thank you for bringing this up, Maning. This is also a concern I've > discussed with other mappers in the past, and this doesn't just apply to > road navigation, but with other features, as well. > > The Mapbox data team is a pioneer in this road network initiatives in OSM, > and we look up to your team for inspiration. > > Our current (in the next few months) interest in PH road network > improvement are low-hanging fruits (missing geometries, restrictions, > turning lanes, etc), but in due time, we'd like to explore how to further > improve road network data from OSM for naviation, etc. PH is only one of > the many countries we're working in, so we need a more inclusive > understanding of tagging nuances, too. > > I hope such a discussion can attract more inputs from the wider > community, especially those who've been lurking in the background, who > follows the exchanges here, but for reasons known only to them, doesn't > engage publicly. > > /Erwin > > On Mon, Jan 15, 2018 at 8:35 PM maning sambale > wrote: > >> Hi Erwin, >> >> Thanks for leading this work. As many of you know, I work in Mapbox >> and my primary focus is to make OSM navigable. >> I wonder what would be the best approach in the context of driving in >> the Philippines. >> Would love to share notes and approaches. One thing I have in mind (I >> shared this during the meetup), while every country >> has specific nuances tagging, there is a danger of making the tags too >> specific as its difficult to create routing engines for each country. >> >> >> On Thu, Jan 11, 2018 at 11:58 AM, Erwin Olario wrote: >> > Happy new year everyone. >> > >> > In case some of you are wondering about some of my recent changeset >> comments >> > with the phrase, "Better PH data with #Kaart", I've recently linked up >> with >> > Kaart [0], and their initiative to improve OSM data in the Philippines. >> > >> > One of the things we'd like to tackle is road network improvement, >> initially >> > in Metro Manila, and later (maybe soon?), expanding to other regions. >> > >> > Improvements that are intended to be addressed include the following: >> > * Adding missing roads >> > * Improving road attributes (names, lanes, restrictions, etc.) >> > * Correcting road connectivity issues >> > * Improving road classification consistency according to OSM guidelines >> and >> > local convention >> > * Correcting road alignment issues >> > * Other one-off fixes >> > >> > Of course, we intend to work closely with the community, and other >> > stakeholders, especially at the local level. >> > >> > We also hope to organize, or lead, activities for developing technical >> > skills, and enhancing collaboration, and community mapa-thons. Think of >> > this as an extension of my earlier MapAmore [1] initiatives. >> > >> > The tasking for Metro Manila [2] is now up, and is hosted by HOT Tasking >> > Manager instance, and open to all interested contributors. >> > >> > In tomorrow's meet-up, I'll take the opportunity to elaborate on this >> > initiative tomorrow. I'm looking forward to hear your feedback, and to >> > answer any questions here, or directly by email. >> > >> > I also hope for your usual helpful collaboration, and support. >> > >> > Kind regards, >> > Erwin >> > >> > >> > [0]: http://kaartgroup.com/ >> > [1]: https://github.com/mapamore >> > [2]: https://tasks.hotosm.org/project/3997 >> > >> > >> > -- >> > >> > /Erwin Olario >> > >> > e: er...@ngnuity.xyz | v/m: https://t.me/GOwin | s: >> https://mstdn.io/@GOwin >> > >> > >> >