M
Michal Migurski
mike.teczno.com · Personal blog · on HN since 2008
Michal Migurski is a mapping and data designer who writes about OpenStreetMap, web performance, and software practice.
What HN saysHN links it for OpenStreetMap topics and page-weight data, including the claim that a single tweet page is 2 MB, and for his map tools.
29HN people shared it
7linked it in comments
29stories submitted
428story points
9 years agolast shared
2008people per year2026
Most-shared posts
- 1Openstreetmap: robots, crisis, and craft mappers3 people · 3 points · first shared 2016 · discussion on HN
- 2A single tweet page is 2.0 MB2 people · 293 points · first shared 2012 · 110 comments on HN
- 3Serverlessness2 people · 5 points · first shared 2017 · discussion on HN
- 4Code like you don’t have the time2 people · 4 points · first shared 2015 · discussion on HN
- 5Making the right job for the tool2 people · 2 points · first shared 2014 · discussion on HN
- 6Creating a Open Source Terrain Layer for OSM2 people · 1 points · first shared 2011 · discussion on HN
- 7Foreground2 people · first shared 2011
- 8OpenStreetMap in Postgres1 people · 65 points · first shared 2012 · 3 comments on HN
- 9Gl-solar – WebGL rendering of OSM data1 people · 13 points · first shared 2013 · discussion on HN
- 10Managers are awesome / managers are cool when they’re part of your team1 people · 10 points · first shared 2014 · discussion on HN
- 11Location-Aware chat system?1 people · 4 points · first shared 2008 · 5 comments on HN
- 12Stamen's simple project status visualizing tool ("angry, productive birds")1 people · 4 points · first shared 2011 · discussion on HN
- 13Things I’ve Recently Learned About Legislative Redistricting1 people · 3 points · first shared 2017 · 1 comments on HN
- 14Processing OSM data with Hadoop1 people · 3 points · first shared 2013 · discussion on HN
- 15Building a geocoder in 5 minutes using open data1 people · 2 points · first shared 2016 · discussion on HN
What HN people wrote when they linked it
riordan · 2013-08-28
OSM's been pretty hardcore about their no import policy because of accuracy issues in validation. They want to map these places themselves and don't want to trust others for accuracy, let alone the legal issues that come with importing data (ugh).
We, however are far more lenient (mostly because we can't afford to build a time machine to map the past ourselves).
On the other hand, Mike Migurski's Green Means Go [1] project is fantastic for figuring out where batch imports into OSM will be greeted with confetti and parades for filling out parts of the US without enough coverage to warrant anti-import protectionism.
[1]: http://mike.teczno.com/notes/green-means-go.html
freyfogle · 2011-12-26
Agree, Google does very well with their UI. But so do others. Check out Leaflet for example http://leaflet.cloudmade.com/
More importantly, with OSM you can do whatever YOU want with the actual underlying data. A great example are these beautiful maps: http://mike.teczno.com/notes/osm-us-terrain-layer/foreground.html
richardw · 2013-02-27
"A single tweet page is 2MB. This is one of the big challenges for Single Page Apps."
https://plus.google.com/app/basic/stream/z123j3wxwrm5jb0tv23ajl0pnvnlx…
Source: Comparison of various pages:
http://mike.teczno.com/notes/bandwidth.html
tmcw · 2012-01-03
You can actually do this with TileMill as well, but a common option is GSV - http://mike.teczno.com/giant/pan/ or panojs: http://code.google.com/p/panojs/
maxerickson · 2016-08-19
This space is heating up a bit.
Facebook (!) has developed a system for mapping roads and is working towards using it to add data to OpenStreetMap:
http://forum.openstreetmap.org/viewtopic.php?id=55220
https://news.ycombinator.com/item?id=12150862 (no comments)
There's several other people/groups working on similar projects, like DeepOSM:
http://www.deeposm.org/
https://news.ycombinator.com/item?id=11808639 (some discussion)
And no shortage of feels about how all the parts need to work together:
http://mike.teczno.com/notes/openstreetmap-at-a-crossroads.html
https://news.ycombinator.com/item?id=12187782 (no comments)
http://tomlee.wtf/2016/07/31/introductory-openstreetmap-politics/
http://www.maproomblog.com/2016/08/openstreetmap-at-the-crossroads/
There have been earlier efforts to do automated feature extraction, but it seems that improvements in AI and better, more liberally licensed imagery are moving things towards some sort of tipping point.
andrewljohnson · 2016-08-19
This has been heating up. Here's the seminal paper that kicked off the Cambrian Explosion: https://www.cs.toronto.edu/~vmnih/docs/Mnih_Volodymyr_PhD_Thesis.pdf
And I saw two presentations about this at State of the Map US.
* Anand Thakker of Development Seed had a cool live demo: https://www.youtube.com/watch?v=BftllmqXSpA&list=PLqjPa29lMiE3eR-g…
* Facebook mapped a bunch of roads in Egypt, and has an ongoing effort. Facebook apparently didn't allow their's to be taped.
I have a similar project called DeepOSM: https://github.com/trailbehind/deeposm
There is starting to be a conversation in the OSM community about allowing robot edits into the map, I'm definitely pro robot. Google has been doing it for years. Mike Migurski touched off debate on the OSM Slack and blog comments with his post: http://mike.teczno.com/notes/openstreetmap-at-a-crossroads.html (added this link after maxerickson's comment reminded me what touched of the debate).
http://terrapattern.com is also a related project from some CMU people.
ZeroGravitas · 2012-03-22
There are already tiles like this, including the ones at this link. It seems like Imhof was part of the inspiration for creating them:
http://mike.teczno.com/notes/osm-us-terrain-layer.html
http://mike.teczno.com/notes/osm-us-terrain-layer/foreground.html
Though those are US only, similar tech is available for worldwide maps.
Compare:
http://www.library.ethz.ch/exhibit/imhof/images/d1.1.jpg
http://hikebikemap.de/?zoom=9&lat=46.58402&lon=7.94684&lay…
http://hikebikemap.de/?zoom=9&lat=46.58402&lon=7.94684&lay…
The primary differences are choice of colorscheme and the fact that the OSM examples are targetted at screen DPI and the paper map was probably intended to be wall mounted.
That's not a limitation of OSM, you can target different resolutions and print to large paper too, it's just not as common. Here's an example:
http://wiki.openstreetmap.org/wiki/File:3274048625_815c60625e.jpg