I was kinda expecting a reference to https://blog.transitapp.com/how-we-built-the-worlds-pretties... but I didn't find any while skimming it, even though the content seems to be very similar
Large-Scale Generation of Transit Maps from OpenStreetMap Data
31–40 of 48 posts
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#32Online demo: https://loom.cs.uni-freiburg.de/global
And the code: https://github.com/ad-freiburg/loom
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#33Online demo: https://loom.cs.uni-freiburg.de/global
And the code: https://github.com/ad-freiburg/loom
Thanks for pointing out in the paper that lot of Spain and Italy is untagged !!
It's interesting to see the first high-speed train line in spain (Madrid-Seville) doesn't appear. I'll see if I can fix that.
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#34Online demo: https://loom.cs.uni-freiburg.de/global
Really cool, but what is happening in Taiwan in the long distance rail map?
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#35It seems like it's missing most of Tokyo? Granted, Tokyo has a blended commuter / subway through-service system (eg, Fukutoshin-line trains continue into the Toyoko-line), but those trains don't seem to show up in either Rail or Subway views.
It is missing most of Tokyo. All they did is look at the subways, specifically the Tokyo Metro system, and maybe a few other lines. The JR rail lines aren't on there, and no transit map of Tokyo is complete without those. The Yamanote line, in particular, is a crucial piece of Tokyo's transit infrastructure, and it's perfectly normal for people to transit between the underground Tokyo Metro and above-ground JR East l…
More generally if you try to do the whole world in one go you are not going to reach useful quality because every place has something unique about it in the transit network itself and also the map is curated by different people who do things differently. The map might look similar to an outsider but the particular codes, conventions and methods will be different.
The answer for this, I think, is that either the OSM data (input) needs to adapt to fit what this system can read or patch rules and patch data can be applied to fix up the output.
Either way it is a distributed project, people in Tokyo or Hannover or any place where it is wrong are the people who would know what is right so they should be engaged in the solution.
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#36I was kinda expecting a reference to https://blog.transitapp.com/how-we-built-the-worlds-pretties... but I didn't find any while skimming it, even though the content seems to be very similar
A 2018 paper by the same authors [0] (referenced in this work) references an earlier blog post by the transitapp people on Medium, but the link is no longer working.
> One approach that seems to use a model similar to ours was described by Anton Dubreau in a blog post
[0] https://ad-publications.informatik.uni-freiburg.de/ACM_effic...
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#37This is really excellent work! It does seem to be missing commuter train/rail systems in Canada, such as the GO Train system in Ontario.
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#38Amazing stuff at so many levels. Would live to hear more about the motivation for using RDF/SPARQL in the technology stack as these are frequently seen as arcane and here is a very intuitive use case.
If you can get the math right you can frequently develop a very good system for representing data in RDF and writing SPARQL queries against it. A week of high-quality thinking can save you six months of time developing an alternate query system; the custom query system might be better but it probably won't be. It's easy to make something that is faster for specialized queries but unlikely you can build something that will let you write complex and versatile queries better than SPARQL.
The key though is coining good identifiers, developing a good set of properties, and understanding how datatype properties work and using them well. It's very easy to develop a bad standard like Dublin Core that, unfortunately, perpetuates the bad stereotypes people have of the RDF world.
The SPARQL spec is dense reading
https://www.w3.org/TR/sparql12-query/
but it's a tiny spec. The SQL spec on the other hand is broken up into numerous $200 documents and if you did look at them you'd find it's much much messier. If you felt SPARQL needed something extra it's a good base to work from to develop some kind of SPARQL++ and the same is true with the RDF model. (e.g. add something to every triple to record provenance, for instance)
My two complaints with SPARQL are: (1) there are two official ways to represent ordered collections and a third unofficial one; if you are good at SPARQL you can write queries that can do the obvious things you want to do with ordered collections (like you'd see in JSON query languages like N1QL or AQL) but there ought to be built in functions that just do it, (2) you can write path queries like
?s (ex:motherOf|ex:fatherOf)+ ?o .
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#39What's novel/interesting about this? Speaking as an ignorant outsider, it seems like they're 'just' querying existing data and plotting it. Obviously this is a gross simplification, but I'd be really interested to hear what's hard about this problem.
From the introduction, Since the days of Harry Beck, transit maps have mostly been created manually by professional map designers (Garland Citation1994; Wu et al. Citation2020). The primary focus was on static maps, either distributed in print or electronically. These maps are typically schematic, and the classic octilinear design (network segment orientations are multiples of 45∘) is still prevalent. In the late 199…
ok yes BUT .. a reason that transit maps were carefully composed is because people "who probably need assistance when using transit" plus "people who do not speak this human language" plus "people who depend on completeness and accuracy to a high degree" are all, at the same time, using one and only one map.
hurrah for computer science BUT this is also graphic design, with human factors, and simultaneously authoritative data that does matter to many real people. Easy tag-on criticism is "who needs all transit maps worldwide at all times" ? Isn't it obviously more important to have reliable, accurate, readable maps for the people who are using the system heavily in that area, instead of stretching all of those qualities to get a toy-prize for armchair readers and the world cloud servers on the Internet? common sense plays a role in the guaging accolades here IMHO
Re: Large-Scale Generation of Transit Maps from OpenStreetMap Data
#40Very cool, I've been working on getting Qlever setup and using it as my main triple store. Was excited to see this hit my feed