I'm surprised I don't see more implementations caching and serving vector tiles. I know some (most?) large mapping companies do this.
I maintain a heavily used map of the US, and I found that storing data/serving in vector format seems to be the most efficient (on AWS s3 / DO spaces), and converting to raster in the browser or with a service call / lambda really opens the doors to a lot more use cases. I suspect parent can talk more about this than I can.
After watching this, I made the connection that the French "Bois d'arc" for Osage Orange refers to its use in bows. It turns out that Osage Orange really is one of the best woods for bows.
I had a TV that did this exact same thing! Except I was given it as a color "monitor" for an Apple IIE. I would spend hours building my own antennas and spinning the fine tune knob to try to bring in far away signals.
National Park Service (contract position) | Frontend Web Developer | Denver, CO or REMOTE
We are building the next generation of web map authoring tools using Angular, TypeScript, JavaScript, Python, PostgreSQL/PostGIS, CARTO and Mapbox, and other open source tools.
There is also a good buildings dataset from DRCOG that we're (OSM Colorado) importing into OSM. Reach out to us, or come to our next meetup if you're interested.
Really great idea to compress the spatial data into Paths.
I would suggest using Natural Earth data instead of OSM so you could drop the ODbL license.
It’d also be really cool if you included the tool that converts the spatial data into Paths.