<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Georgios Mathioudakis on Medium]]></title>
        <description><![CDATA[Stories by Georgios Mathioudakis on Medium]]></description>
        <link>https://medium.com/@gmathiou?source=rss-1af69c38cb69------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oJt4W2SFzNvQgHcTTpViMg.png</url>
            <title>Stories by Georgios Mathioudakis on Medium</title>
            <link>https://medium.com/@gmathiou?source=rss-1af69c38cb69------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 06:01:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gmathiou/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Open Data for Public Transportation]]></title>
            <link>https://medium.com/@gmathiou/open-data-for-the-public-transportation-8148ebaef323?source=rss-1af69c38cb69------2</link>
            <guid isPermaLink="false">https://medium.com/p/8148ebaef323</guid>
            <dc:creator><![CDATA[Georgios Mathioudakis]]></dc:creator>
            <pubDate>Fri, 04 Jul 2014 13:16:37 GMT</pubDate>
            <atom:updated>2015-03-20T05:30:14.330Z</atom:updated>
            <content:encoded><![CDATA[<h4>And why I am building a GTFS manager</h4><p>How many times have you used <strong>Google Maps</strong> to find your way to a place using public transportation? If you live in a big city I guess this will be happening really often. But have you ever wondered how Google Maps is getting this information from the public transportation providers? Well, since last year I couldn’t care less about this, till I had the chance to find out the whole story behind it.</p><p>It was May of 2013 when RATP, the company running the Parisian metro, organised a big event and a hackathon (<strong>#opendatalab</strong>) to celebrate the release of the data for its lines. It didn’t seem very attractive but it was supposed to have free pizza so I was totally in. So me, and some awesome people from my team at work, registered to take part. The day of the hackathon started really tough for me. All the presentations were in French and my French level back then was at <em>bonjour </em>level. However, the presentations were full of links and links are universal. I started typing and exploring what these guys were trying to say. <strong>Et voilà</strong>!<em> </em>In a couple of minutes I was discovering the core of the open data format for public transportation, the <strong>GTFS feeds</strong>. That was the way that Google Maps (along with anybody else) was getting all the information.</p><p><strong>But wait! What is GTFS?</strong></p><blockquote>The General Transit Feed Specification (GTFS) defines a common format for public transportation schedules and associated geographic information. GTFS “feeds” allow public transit agencies to publish their transit data and developers to write applications that consume that data in an interoperable way.</blockquote><p>So the point is this: The public transportation providers expose their data in a <strong>common format </strong>so that anyone could download, understand and use them freely. And that’s really cool if you consider the ways app creators could take advantage of it and develop some awesome apps.</p><p>GTFS is a rather flexible format. The data are formatted in a series of .txt files (which in fact are <strong>.csv formatted</strong>) and describe every aspect of the services provided by the transportation agencies (routes, stops, timetables, fares, etc.). Some files are required and some others are optional, so you can create as many as you like. However the more you have the better you describe your services. Here is the list of the available files:</p><blockquote><a href="https://developers.google.com/transit/gtfs/reference#agency_fields">agency.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#stops_fields">stops.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#routes_fields">routes.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#trips_fields">trips.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#stop_times_fields">stop_times.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#calendar_fields">calendar.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#calendar_dates_fields">calendar_dates.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#fare_attributes_fields">fare_attributes.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#fare_rules_fields">fare_rules.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#shapes_fields">shapes.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#frequencies_fields">frequencies.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#transfers_fields">transfers.txt</a>, <a href="https://developers.google.com/transit/gtfs/reference#feed_info_fields">feed_info.txt</a></blockquote><p>However, even if it sounds so good to have Open Data for public transportation it requires a big effort from the transportation agencies to create these GTFS feeds. This is because the most of them are using <strong>proprietary systems</strong> for managing their network or, even worse, they do not use any system for the network management. So if you were the manager of a transportation company the options would be to either build a way to export the data from your system to the GTFS format or build the GTFS feed manually from scratch. Nevertheless, sometimes the first option is not feasible, thus the manual way is the only way to go. And it’s not an easy way at all.</p><blockquote>What if there were tools for creating and managing GTFS feeds?</blockquote><p>That was my thought from the first moment. There should be some tools doing that, right? In fact there are, but are they good enough to make the service providers use them? Well, I don’t really think so. The fact is that all of them lack in usability, providing either minor functionality or more functionality but with non-intuitive interfaces (see figure bellow).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZGX7GPnYS8dp0NhYzpSkQQ.png" /><figcaption>Example of an existing GTFS manager. By yTransit</figcaption></figure><p>Therefore how we are supposed to convince the transportation agencies to adopt the Open Data if there are no appropriate tools to work with? That’s the reason I started imagining how I would build such a tool. I had in my mind the essentials. A tool like this should be:</p><ul><li><strong>Easy to use</strong>: So you don’t need a Phd to understand how it operates.</li><li><strong>Flexible: </strong>To be able to work on the move, on a pc or your tablet. To monitor in real-time the network or edit the feeds.</li><li><strong>Fast: </strong>Minimum time needed to perform a task. Everything in the UI should make sense + fast computations.</li><li><strong>Scalable: </strong>Because you never know how large your agency can become.</li></ul><blockquote>A new GTFS Manager is born</blockquote><p>Having all that in mind I started building the tool the way I imagined it. I decided to go with a web app (instead of a desktop/native app) to meet the flexibility expectation. <strong>Node.js</strong> was the tool to start since I also wanted my GTFS manager to be fast and scalable. Along with Node.js I was in need for something to store the data on the server side. The most obvious option was to go with <strong>MongoDB </strong>as, at the time speaking, it is the most favourable db for Node.js. By doing this I have a homogeneous flow of data running from the database down to the client in the JSON format, making the parsing process an easy task. Many would argue that MongoDB still has a lot of issues and I can’t agree more. But in overall it performs well and till now I am not regretting of using it. Since a lot of computation will happen on the client side I wanted something really powerful to handle the data. The options were many but I decided to go with <strong>AngularJS </strong>since it is the most promising out of the competition (Backbone.js, ember.js, etc.). For the layout, <strong>Bootstrap</strong> was a wise choice since it brings in some nice elements, so that I don’t have to spend a lot of time writing already existing stuff. But enough with the technical details, let me show you how it looks now!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F99912287&amp;url=http%3A%2F%2Fvimeo.com%2F99912287&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F481242085_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="390" frameborder="0" scrolling="no"><a href="https://medium.com/media/65f5175e6b71fdae087c69fff79bf73b/href">https://medium.com/media/65f5175e6b71fdae087c69fff79bf73b/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F99912285&amp;url=http%3A%2F%2Fvimeo.com%2F99912285&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F481242081_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="390" frameborder="0" scrolling="no"><a href="https://medium.com/media/3320fdea6b13a4c286fcd4db1f2ff7b7/href">https://medium.com/media/3320fdea6b13a4c286fcd4db1f2ff7b7/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F99912286&amp;url=http%3A%2F%2Fvimeo.com%2F99912286&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F481242083_640.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="640" height="408" frameborder="0" scrolling="no"><a href="https://medium.com/media/f8564e4af3aa56dab902ec9e82d1211f/href">https://medium.com/media/f8564e4af3aa56dab902ec9e82d1211f/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F99912288&amp;url=http%3A%2F%2Fvimeo.com%2F99912288&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F481242084_960.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=vimeo" width="1136" height="720" frameborder="0" scrolling="no"><a href="https://medium.com/media/a8bf8aaee53c5f7ec8306d745493990d/href">https://medium.com/media/a8bf8aaee53c5f7ec8306d745493990d/href</a></iframe><p>I am super excited with the progress so far and I believe that soon I will have something that will be really useful. <strong>In the</strong> <strong>Open Data we trust!</strong></p><p><strong>P.S. 1</strong>: At the RATP’s hackathon we won a prize ☺ and it was awesome!</p><p><strong>P.S.2</strong>: In France hackathons end at the end of the day and start again in the morning. No sleeping overs :P</p><p><strong>P.S.3</strong>: You can find some already existing GTFS feeds here: <a href="http://www.gtfs-data-exchange.com/">http://www.gtfs-data-exchange.com/</a></p><p><em>Thanks for reading!!!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8148ebaef323" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Modern Static]]></title>
            <link>https://medium.com/@gmathiou/modern-static-1300b3b928b?source=rss-1af69c38cb69------2</link>
            <guid isPermaLink="false">https://medium.com/p/1300b3b928b</guid>
            <dc:creator><![CDATA[Georgios Mathioudakis]]></dc:creator>
            <pubDate>Sat, 08 Mar 2014 18:22:56 GMT</pubDate>
            <atom:updated>2014-03-10T12:50:42.705Z</atom:updated>
            <content:encoded><![CDATA[<h4>Because the static… is the new dynamic</h4><p>Let me start with a fact, I was technologically raised as a WordPress child. I had some real fun exploring new themes &amp; plugins, creating mine later and in general playing with WP in the LAMP playground. Together we had great times but we also had some difficult ones. I will never forget how many hours spent debugging the most nonsensical errors causing <a href="http://www.wpbeginner.com/wp-tutorials/how-to-fix-the-wordpress-white-screen-of-death/">white screens of death</a> after core or plugin updates. Even more stressful and risky is the process moving a WP site from a hosting provider to another. So, having some demanding projects following I decided to go down to the web technology market and find some new and cool technologies to use.</p><p>At this point, I got introduced to the static website generators, an increasingly popular approach to building websites and blogs. Static website generators<strong> </strong>are <strong>File-based and Database-free</strong><em> </em>CMSs that run locally on your machine providing “dynamic” features and then generate static html files to be easily uploaded on your host. The whole process is automated and is usually executed using the command line. There are <a href="http://modernstatic.com/">quite a few</a> site generators out there to choose, built on languages like Ruby, Python, Node.js or even PHP (who doesn’t love PHP, right?).</p><p>The process to create a new website is trivial. Firstly, you have to create the file structure for your new local CMS. That is done by running the corresponding command at the terminal or just by downloading the whole thing from the creator’s website. Most of the times the structure is pretty clear and leads you on how to start developing your website. From that point the process of creating your webpage or blog should be summarized to these three things: <strong>Templating</strong>,<strong> Styling,</strong> <strong>Automation</strong>.</p><p>Templating is the process of adding some “dynamic” functionality to your static html layout. This is achieved by inserting tags that can be dynamically loaded providing for instance, webpage titles, meta and content from the separated content files. Therefore, you can have one layout file and any number of content files providing the content to that single layout file. The benefit is obvious, that you don’t have to copy the structure of the webpages over and over. Every website generator comes with a set of supported templating engines so you can choose whatever fits best to you. Some good ones I’ve seen or played with are the <a href="https://github.com/sstephenson/eco">eco</a>, <a href="http://haml.info/">Haml</a>, <a href="http://jade-lang.com/">jade</a> and <a href="https://github.com/janl/mustache.js">mustache</a>. There are lots of them so don’t spend much time deciding. Just go with the one that your site generator offers as the default.</p><pre>&lt;% if @projects.length: %&gt;<br>  &lt;% for project in @projects: %&gt;<br>  &lt;a href=”&lt;%= project.url %&gt;”&gt;&lt;%= project.name %&gt;&lt;/a&gt;<br>  &lt;p&gt;&lt;%= project.description %&gt;&lt;/p&gt;<br>  &lt;% end %&gt;<br>&lt;% else: %&gt;<br>  No projects<br>&lt;% end %&gt;</pre><p>Now that the layout and content files are separated we could start writing some content to populate the pages. But content files are html as well, so your will have to write these boring html tags all along. Or maybe not… This is a great point to get introduced to <a href="http://daringfireball.net/projects/markdown/">Markdown</a>, a text-to-html conversion tool for web writers. As the name implies you can write plain text in a specific format and markdown is smart enough to parse and transform it into html. So you can spend more energy on writing and less on putting tags.</p><pre>### Header 3</pre><pre>&gt; This is a blockquote.<br>&gt; <br>&gt; This is the second paragraph in the blockquote.<br>&gt;<br>&gt; ## This is an H2 in a blockquote</pre><p>Since you have the layouts and content already created it’s time for some hardcore css coding, right? No, don’t just start writing your styles. CSS coding is fun but requires a lot of effort. What if you had a more compact and smarter syntax to write your styles easily but still be compatible with the web standards? Well, you have and CSS preprocessors offer this to you. The syntax that the preprocessors offer varies but always remain more compact and powerful than the CSS itself. Take a look at <a href="http://learnboost.github.io/stylus/">Stylus</a> (my favorite), <a href="http://sass-lang.com/">SASS</a> and <a href="http://lesscss.org/">LESS</a>. Each one of them comes with the required tools to convert the <em>CSS on steroids</em> you write in the specific syntax to the old plain CSS. I will not get into detail what exactly they offer but to mention some highlights they support variables, code snippets, functions, conditional statements and more.</p><pre>textarea<br>input<br> color #A7A7A7<br> &amp;:hover<br> color #000</pre><p>At this point you are ready to upload to your host the files created by the static website generator using Filezilla or any other ftp program. But if you also care about performance your files should be concatenated and minified before uploading, right? This doesn’t sound much dificult but since you will be working locally the website you will be probably uploading it very often, making the process boring and tiring. This is why you really need <a href="http://gruntjs.com/">Grunt.js</a>. From my personal experience it is a bit dificult to understand what Grunt exactly does when you start reading about it but by the time you get it you will wonder why you were not using it all that time. In brief, Grunt is a javaScript automator. You define some typical tasks like css minification, file concatenation, ftp-deployment, etc. and when you are ready to deploy you just have to run the command <em>grunt </em>and everything will be executed magically, every time.</p><p>As a conclusion of this post I would say this, it is now easier than ever to create a static-dynamic<em> </em>website and blog. Given the power of the tools they provide you will still have the functionality of a full featured CMS like Wordpress but much less headaches and things to worry about. My personal favourite website generator for the moment is <a href="http://docpad.org/">Docpad</a>. It offers all the required tools like the ones described above and a lot more than them. It is based on Node.js and is totally free. So go get it and start playing now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1300b3b928b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>