How We Mapped 1.3M Data Points Using Mapbox
source.opennews.org
How We Mapped 1.3M Data Points Using Mapbox
1–10 of 22 posts
Re: How We Mapped 1.3M Data Points Using Mapbox
#2It's interesting seeing the process they went through to work around MapBox's hosting limitations, but the map doesn't feel terribly usable to me. The chart doesn't update on pan/zoom (at least for me in Firefox) and the raster area is a little funky, I wish it was using a standard interpolation that covered everywhere instead of selective areas.
Also, I am loading a ton of data on this page. Interactive maps are nice and I love them but it's totally not usable on a mobile network for a ton of people (ironically given the content of the map). Very curious why they are using React at all, seems like extra page bloat for just one interactive map + chart. Do they test usability on 3G networks? I did not have great load times when off wifi. I think this would be better on a stand-alone page so you can read the article without having your load time impacted by the extra JavaScript.
Re: How We Mapped 1.3M Data Points Using Mapbox
#3Actual map is here: https://ig.ft.com/gb-broadband-speed-map/
Re: How We Mapped 1.3M Data Points Using Mapbox
#4I'm surprised they didn't consider hosting their own vector tile server, instead of painstakingly rasterizing their entire dataset and optimizing it over and over to fit into the Mapbox data caps.
My company recently hit the need for maps showing several of our own proprietary layers at various zoom layers, and considering how much of the data is already in GeoJSON, converting that to the Mapbox Vector Tile binary format (MVT) was a breeze to implement on our own servers, compared to rasterizing all of the layers and re-rendering whenever any part of our datatset changes.
Re: How We Mapped 1.3M Data Points Using Mapbox
#5I'm surprised they didn't consider hosting their own vector tile server, instead of painstakingly rasterizing their entire dataset and optimizing it over and over to fit into the Mapbox data caps. My company recently hit the need for maps showing several of our own proprietary layers at various zoom layers, and considering how much of the data is already in GeoJSON, converting that to the Mapbox Vector Tile binary fo…
I'm surprised about this as well. Even if they didn't want the overhead of running their own tile server, one of the best parts of the MVT format in my mind is that one-off tilesets like this layer can trivially be thrown into S3 and served extremely cheaply as well. That removes a ton of the effort they put into circumventing MapBox's limitations and is cheaper to host.
Re: How We Mapped 1.3M Data Points Using Mapbox
#6I'm surprised they didn't consider hosting their own vector tile server, instead of painstakingly rasterizing their entire dataset and optimizing it over and over to fit into the Mapbox data caps. My company recently hit the need for maps showing several of our own proprietary layers at various zoom layers, and considering how much of the data is already in GeoJSON, converting that to the Mapbox Vector Tile binary fo…
I'm surprised about this as well. Even if they didn't want the overhead of running their own tile server, one of the best parts of the MVT format in my mind is that one-off tilesets like this layer can trivially be thrown into S3 and served extremely cheaply as well. That removes a ton of the effort they put into circumventing MapBox's limitations and is cheaper to host.
And presumably be cached through a service worker, which might be very useful.
Re: How We Mapped 1.3M Data Points Using Mapbox
#7It's interesting seeing the process they went through to work around MapBox's hosting limitations, but the map doesn't feel terribly usable to me. The chart doesn't update on pan/zoom (at least for me in Firefox) and the raster area is a little funky, I wish it was using a standard interpolation that covered everywhere instead of selective areas. Also, I am loading a ton of data on this page. Interactive maps are nic…
To be fair, it’s a journalistic exercise not a long running webapp project, if the page loads a second later but development time is significantly reduced, it might be worth the tradeoff. The map works well for me, using mobile on wifi.
Re: How We Mapped 1.3M Data Points Using Mapbox
#8Next time they better talk to experts for their own sanities' sake...!
> We set the interpolation process running in QGIS on a Mac Pro and, a mere 11 days later, found ourselves the proud owners of a raster 250m2 grid layer
Probably done in minutes to hours with a properly setup PostGIS database and one query. "Data Journalists" seem to love it when things take long, thinking they are doing something super innovative and novel. Often it's just that they were using the wrong hammer...
> 1. Don’t use GeoTIFFs for geometric visualization
What? I am not sure what exactly the image is supposed to show but it seems like some rescaling/filtering. Not the fault of GeoTIFF.
Why not render the raster tiles locally? gdal2tiles or Tilemill can do that for you.
Why does Mapbox recommend LZW for compression? DEFLATE is usually much smaller and with the horizontal differencing predictor it should be even more smaller.
> 2. Your GeoJSON can probably be way smaller
Does Mapbox not support TopoJSON? That helps a lot for local data with quantisation.
> Because nothing in GIS is straightforward, attempting to round the values of 2.7m polygons using the field calculator in QGIS invariably resulted in the application crashing, even on a high-end Mac Pro. After several attempts using QGIS 2.16, 2.18 and 3.2,
Did they ask the community or even just provide a bug report? This should not happen from a QGIS fault.
Re: How We Mapped 1.3M Data Points Using Mapbox
#9Next time they better talk to experts for their own sanities' sake...! > We set the interpolation process running in QGIS on a Mac Pro and, a mere 11 days later, found ourselves the proud owners of a raster 250m2 grid layer Probably done in minutes to hours with a properly setup PostGIS database and one query. "Data Journalists" seem to love it when things take long, thinking they are doing something super innovative…
Yea, as someone who does this sort of thing for a living much of that was quite painful to read. I mean hats off to them for getting a nice result, but they could have done it so much more efficiently by using the right tools.
Re: How We Mapped 1.3M Data Points Using Mapbox
#10It's interesting seeing the process they went through to work around MapBox's hosting limitations, but the map doesn't feel terribly usable to me. The chart doesn't update on pan/zoom (at least for me in Firefox) and the raster area is a little funky, I wish it was using a standard interpolation that covered everywhere instead of selective areas. Also, I am loading a ton of data on this page. Interactive maps are nic…
Yes, the top-line emphasis on MapBox when all the actually useful work was done by other tools to get around MapBox API limitations. A little funny.