Na co gis comm 2011

472 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
472
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • TriMet is the public transportation service provider in Portland, OR
  • City of Portland resolution directs the city government to open data to outside developers and encourages adoption of open source solutions in technology procurement1. Made as much data available on civicapps – very quickly2. Solicited ideas for applications and voting mechanism2. Held 2 app contests requiring that winning app must be open source
  • Data.gov is a leading example in the open data movement. We were excited about it because it aligns with our moded. Because software development is not the government’s core business,is becoming a new role government – to make public data publicly available and easy to access and use. Software development is not our core business.Developers want RAW digital data and a CATALOG so they can quickly understand what it is they’re working with.
  • The results?  Lots of satisfied customers. We are nearing 40 applications all developed by third parties. Criteria for listing on apps page: Must be using our developer resourcesMust work as it says it doesMust adhere to our Terms of Use so that its clear to the user that the data comes from TriMet but the app is not. Our experience indicates that there is a natural selection process after the initial enthusiasm of an open data release, esp. surrounded by app contests. The good apps get better, and the bad apps are weeded out, which is good.
  • In any IT procurement, we make an effort to look for open source alternatives, and we weigh the risks and advantages against the commercial options. Both have risks, however, open source has the potential for great benefits, esp. for government agencies, as we’re not in competition with each other.
  • We developed a method fo comparing COTS with OSS. We performed an alternatives analysis a couple years ago and looked at commercial off-the-shelf products, free APIs (Google, Yahoo), and open source software like GeoServer and MapServer.  We’re a Java shop so GeoServer complied with all our IT standards, and it fit all of our requirements - both internal agency mapping needs and external customer mapping needs.  Again, my biggest hesitation was support for this product, however, I would say its actually superior. We’ve gotten responses/support from users/developers all over the world. Its amazing. Include Open Source Solutions in Feasibility Studies and Requirement Analysis (in addition to COTS)OS Code/Language – ex. can it be supported and maintained internally, does it adhere to IT standards Developer Base Working Implementations Terms and conditions of the OS license agreement Governance or Foundation Options for support and maintenance contracts No initial fee for the software, however, should calculate and compare long-term operating costs and resources against COTS
  • Maps.trimet.org is powered by all open source technologies, including the OpenGeo Stack:  GeoServer, OpenLayers, and PostGIS.  Its all OGC standards compliant and we’ve been extremely happy with the sophistication of this technology and the level of world-wide support from the development community (and esp. from Open Plans). We wanted the ability to bring information from a variety of sources into one application so that customers can make informed decisions. We’re bringing in streetview, next arrival info, trip planning itineraries, stops and amenity information directly from out database.System Maps have historically been paper, but as soon you print, they’re out of date. The biggest advantage is its always up-to-date with little overhead and maintenance.
  • Real-Time vehicle locations and the measure distance tool.We paid for it once, and not its in the source-code for the benefit of everyone. This is a great model for government – shared resources.
  • It has also replaced all of our map object applications. Once the infrastructure is in place, its very easy to customize apps for a particular business use.
  • Even though our map is pretty, and sophisticated, it is single mode only.
  • Open Plans has experience developing communities around open source software and data. The objective is build a development community around the code and have Open Plans manage it so it’s a very viable alternative for agencies. 
  • collaborative method to software design, development, distribution with access to source code
  • Collaborative method of tracking work and voting on important decisions.
  • Research is valuable, but there is no replacement for getting in there and actually editingExplain the images (the first one is what I thought the data should look like when I began and the second is what I learned it should be through observing others work)OSM users contacted us and (politely) informed us of things that we were doing incorrectlyShare what you have learned through editing with your team
  • Project timeline July 2009- July 2011. TriMet received a grant to build an osmmtps.  The Open Planning Project (TOPP) http://topp.openplans.org/ is the primary contractor and the subs are David Emory/Five Points http://trip.atltransit.com/, Brandon Martin Anderson/GraphServer (Bus Monster) http://graphserver.sourceforge.net/, and TriMet (in-kind).  We're starting with David's code and building from there.  The objective is build a development community around the code and have TOPP/OpenGeo manage it so it’s a very viable alternative for agencies.  We have enough funding, but we need one other agency on board so its a collaborative effort to ensure continued success. In TOPP’s experience, the most successful os projects are collaborations, so this is critical. 
  • Talk about how the trips with no green bars represent trips where ATIS could not plan – limitations of the single mode trip planner. ANY QUESTIONS
  • And now I believe they are the fundamental building blocks for the next generation of GIS. And with everything open, anything is possible. Thank you.
  • Na co gis comm 2011

    1. 1. Open Geo-Data and Open Geo-Software<br />National Assoc. of Counties<br />GIS Subcommittee Agenda <br />July 16, 2011 <br />Presented by Bibiana McHugh<br />IT Manager of Spatial Technologies<br />TriMet <br />
    2. 2. open data<br />City of Portland resolution directs city government to open data and encourage adoption of open source solutions in technology procurement<br />
    3. 3. Just look at the numbers:<br />7 Other nations establishing open data<br />16 States now offering data sites<br />9 Cities in America with open data<br />236 New applications <br />253 Data contacts in Federal Agencies<br />305,709 Datasets available on Data.gov<br />open data<br />
    4. 4. open data<br /> 40 apps developed by third parties using TriMet’s open data<br />PDX Bus sends @ 100k requests/day for next arrival info<br />
    5. 5. open source software<br />Understand and weigh your risks and advantages<br />Not all proprietary is the same, and not all oss is the same<br />
    6. 6. open source software<br />
    7. 7. = $$$<br />open source software<br />Free Hybrid Car!<br />Open Source Software is NOT FREE<br />hardware requirements, training, implementation, customizations, upgrades, additional feature development, support, maintenance, etc.<br />
    8. 8. open source software<br /> Analyzed alternatives for internet mapping<br />Compared open source alternatives with proprietary<br />
    9. 9. open source software<br />TriMet Interactive System Map/Trip Planner maps.trimet.org<br />All open source technologies including GeoServer, OpenLayers, PostGIS<br />
    10. 10. open source software<br />TriMet Interactive System Map/Trip Planner maps.trimet.org<br />Real-Time Vehicle locations , Measure Distance Tool<br />
    11. 11. open source software<br />Internal applications using same open source platform<br />Mobility map, Real-Time Vehicle Mapper, Stops and Amenities Application, Accident & Incident Application, Transit Mapper<br />
    12. 12. trip planning<br />Single-Mode Trip Planners<br />
    13. 13. trip planning<br />Multi-Mode Trip Planners<br />
    14. 14. trip planning<br />2009 Portland, OR <br />trimet trip planner<br />oregon unemployment claim<br />95.5 the game<br />multnomah county jail<br />onpoint credit union<br />mypcc<br />pcc.edu<br />pdx.edu<br />workinginoregon.org<br />blazers edge<br />2010 Portland, OR <br />
    15. 15. the Open Trip Planner (OTP)<br />Metro Regional Travel Options Grant <br />July 1, 2009 – July 1, 2011<br />
    16. 16. the Open Trip Planner (OTP)<br />Project Kick-Off Workshop <br />July 2009<br />
    17. 17. the Open Trip Planner (OTP)<br />OpenTripPlanner.org<br />
    18. 18. the Open Trip Planner (OTP)<br />Open Source Development Method<br />
    19. 19. the Open Trip Planner (OTP)<br />Shapefiles<br />Oracle<br />OSM<br />OpenStreetMap<br />Regional<br />Data<br />PostGIS<br />Adapter<br />Adapter<br />Adapter<br />Adapter<br />Adapter<br />Data API<br />Geocoding<br />Service<br />Address<br />Normalizer<br />Service<br />Etc.<br />Routing<br />Service<br />Client<br />Application<br />Web Services<br />API<br />Open Architecture<br />
    20. 20. the Open Trip Planner (OTP)<br />OTP uses open source datasets (GTFS, NED, and OSM) to build a routable graph<br />
    21. 21. the Open Trip Planner (OTP)<br />The demos are designed for demonstration purposes and are intended to be used as a tool for the developers for testing purposes for both the algorithm and the underlying data. <br />Progress in Year 1 (July 2009 – July 2010)<br />Worldwide interest and participation<br />
    22. 22. the Open Trip Planner (OTP)<br />Progress in Year 1<br />Support and maintenance options<br />
    23. 23. Code Development<br />Code quality and extensibility improvements <br />Improved wheelchair accessibility <br />graph reloading Speed improvements (~10x) <br />Memory usage improvements (~0.5) <br />Code documentation <br />Intermediate stops in API <br />Better extensibility <br />Visualization improvements <br />Making bikes on transit optional <br />Kept up-to-date with changing technology (upgraded Spring) <br />Edge notes <br />Nominatimgeocoder support <br />Cleaner max walk distance support <br />Support for certain common GTFS failure modes <br />Workarounds for OSM data issues (pedestrian islands) <br />Support loading OSM from Protocol Buffers format & bz2 xml <br />OSM future proofing <br />OSM permission bug fixes <br />Traffic circles / roundabouts <br />Much improved transfer support (min transfer times; transfers now routed on walking network) <br />Support for multiple route names on the same stop pattern (typically night buses) <br />Dozens of miscellaneous bug fixes <br />Gvsig visualization <br />Documentation for graph builder <br />Better names for some OSM ways <br />Better slope visualization <br />Slope override for bridges <br />Some integration with OneBusAway<br />Preferred/dispreferred/banned routes<br />Translations from English into the following seven languages: French, Gaelic, Hungarian, Italian, Marathi, Polish, Spanish <br />the Open Trip Planner (OTP)<br />Demos Released:<br />Granada, Spain July 2010<br />Pune, India October 2010<br />Smartrip Transport for Dublin Journey Planner January 2011<br />Ottawa Canada Green Trip Planner January 2011<br />Tampa, Florida May 2011<br />Gipuzkoa Transit Android App May 2011<br />TeleAviv, Israel <br />Translations into: French, Gaelic, Hungarian, Italian, Marathi, Polish, Spanish, Hebrew <br />Progress in Year 2 July 2010 – July 2011 <br />
    24. 24. the Open Trip Planner (OTP)<br />Street Map Data Options <br />Why OSM? Investment in community product for shared benefits<br />
    25. 25. Open Street Map (OSM)<br />Jurisdictional Format<br />OSM RoutableFormat<br />
    26. 26. ESRI – OSM Glossary <br />
    27. 27. Open Street Map (OSM)<br />
    28. 28. Open Street Map (OSM)<br /> SE Water St.<br />SE 1st<br />SE 2nd St.<br /> SE Main St 1 99 101 199 201<br /> 098 100 198 200<br />55 SE Main St.<br /> SE Water St.<br />SE 1st<br />55 SE Main St.<br />SE Main St <br />Address Geocoding<br />
    29. 29. Open Street Map (OSM)<br />Address Search Engines force the user to enter/determine accurate spelling, address, etc. <br />Address Geocoding<br />
    30. 30. Open Street Map (OSM)<br />Phase II Status<br />Goal – to support vehicular and bus routing for TriMet Operations (and future phase of OTP) <br />
    31. 31. Open Street Map (OSM)<br />Attributes to be verified:<br /><ul><li>Legal turn restrictions for cars, bicycles, buses
    32. 32. Speed limits (ranges)
    33. 33. Street names
    34. 34. Street directionality/one-ways
    35. 35. Other impedences (speed bumps, roundabouts, etc.)</li></ul>QC Process <br />
    36. 36. the Open Trip Planner (OTP)<br />Metro Regional Travel Options Grant <br />July 1, 2011 – July 1, 2013<br />
    37. 37. the Open Trip Planner (OTP)<br />On the Horizon<br />
    38. 38. the Open Trip Planner (OTP)<br />OTP Interface Preview – Fall Beta Release <br />
    39. 39. OTP produced a significantly faster trip in all but one case<br />Minutes<br />Planned Trips<br />

    ×