nelsonminar / vector-river-map Goto Github PK

CORS issues! - it looks like whatever web proxy / load balancer you're using isn't configured to forward traffic correctly. Since somebits.com:8080/ is requesting from somebits.com/8001/ without using a CORS handshake, none of the map data is loaded, and many (many) javascript errors are generated.

The map linked https://www.flickr.com/photos/nelsonminar/8747607969/in/photostream/ is currently representing the Platte river as roughly ~250 miles in width.

Vertically from the southern tip of TX to the northern border of the US there are roughly ~1585 miles.

The pixel distance on the map for that same path is 936 px for the 2048x1152 image. The pixel distance from north to south (parallel to the mile measurement) for the Platte River is 6px in the thickest part.

That would mean that in pixels, the plate river is 1/156th of the distance from the southern tip of TX to the northern border, while ~1585 miles / 156 means that the river is represented as being ~264 miles wide.

It seems that this map is largely overestimating the overall river density (width) for the US. The data for width or volume seems to be there, as there are rivers of differing widths.

Could you produce a version that is geographically representative of the actual widths of the rivers, it may have to be a very high resolution but I would be interested to see it.

TileStache VecTiles has been updated and now is expecting a selection named __geometry__. Not sure there's any backward compatibility or whether pip is installing this new thing yet. Details on TileStache changes: TileStache/TileStache#136

live map does not have any riveres or is it supposed to be this way? o.o

All of this could run on OpenShift and I would like to make it into a quickstart. How big is the data (including the tile cache) when all is said and done?

Thanks for a great project!

Hi,

I hope you can help me.

I try to figure out why the perfomance of http://www.somebits.com/rivers/rivers-d3leaflet.html is so much than the performance of http://www.somebits.com/rivers/rivers-leaflet.html (at least in Firefox 26). I'm talking about the performance while moving the map with the mouse not while loading the tiles.

Background: I'm working on an leaflet based app, where I need to draw many polylines. But I can use a GeoJSON-Layer for it, since the information for the polylines comes from a javascript object of another module of the app. So I need to draw my polylines manually. I use L.polyline(latlngs, {...}).addTo(map); But when I move the map with the polylines attached to it, the performance is very bad.

So what's the difference with having d3 draw the polylines?

Regards,
kermit-the-frog