Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Yatayat: Mapping public transportation in Nepal

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.

Yatayat: Mapping public transportation in Nepal

Brown bag presentation to Modi Research Group, 5/29/2013.
Talking about the Yatayat project and the Monsoon Collective that created it.

Avatar for prabhasp

prabhasp

May 29, 2013
Tweet

Other Decks in Technology

Transcript

  1. Yatayat   Mapping  public  transportation  in   Kathmandu,  Nepal.  

        Prabhas  Pokharel,  Monsoon  Collective  
  2. Structure   As  open  as  possible.     3-­‐4  hours.

     Wed  +  Thurs,  Sat  +  Sun.     4  weeks.   -­‐  Intro  week   -­‐  Weekend  1:  mapping   -­‐  Project  week   -­‐  Weekend  2:  mobile   -­‐  Project  week   -­‐  Weekend  3:  exhibition  prep   -­‐  Finish  +  exhibition.    
  3. Even  then  –  transport  was  interesting   (and  we  thought

     doable).   (do   Screenshot,   http://prishtinabuses.info  
  4. OSM   For  us,  the  obvious  choice.     -­‐ 

    Already  working  on  the  baselayer  map  itself  in  OSM.   -­‐  Viral  license  was  a  value,  not  hindrance.   -­‐  The  tools,  the  tools!   -­‐  Prior  art.   -­‐  DB,  synchronization,  multi-­‐users,  all  figured  out.   Alternatives:  GTFS  file  format.  But  no  public  data   infrastructure  around  it.  
  5. Schema   Relations.   (KTM  public  transport  is  all  road

     vehicles.)     Ways  are  already  there  for  roads  already,  we  don’t  touch   their  “core”  attributes.     Stops:  public_transport=stop_position   Relations:  type=route,  route=bus  /  minibus  /  tempo                                        :  all  individual  segments  of  road  that  a  bus                      goes  over  are  put  into  the  relation                                        :  the  start  +  end  stops  are  given  special  “roles”                                within  the  relation    
  6. Points  of  interest   ALL  JS!     Initially,  all

     client  side.     Retrieval  of  data:  overpass  API.      V1.  Overpass  -­‐>  Front-­‐end  JS.     (SMS  +  Mobile  app  experiments,  supported  by  Node.js   as  well!)    
  7. Points  of  interest   ALL  JS!     Data  Quality

     code  can  be  run  by  server  as  well  as  client.     V2.  Overpass  -­‐>  Nightly  pull  -­‐>  Data  Quality  check    [-­‐>]  cached  version  -­‐>  Site.       -­‐  Data  Quality  page  always  fed  off  of  raw  OSM  data.   -­‐  Emails!              
  8. Right  Now   In  Process  of  working  with  Kathmandu  University

      students  and  OSM-­‐Nepal  members  to  continue  data   upkeep.       http://groups.google.com/ group/yatayat-­‐project   Shout  out!  Thanks  Suresh  Shrestha  and  Amrit   Karmacharya  for  keeping  the  project  alive  and  going!  
  9. Next  Steps   Better  routing  (anyone  want  to  help)?  

      Community  building,  more  data  incorporation.     Institutionalization  -­‐-­‐  ?