How else were you going to do it than ingesting the new data constantly, if you're a company who needs regular updates? You need a server, either to pull the whole planet file over and over or to pull the trickle of minute by minute diffs. Might as well opt for diffs
Yeah there's lots of tuning to do on the commit messages (like filtering out bots). I really believe by having access to git diffs and commit messages you can fully automate a standup.
> These billing changes make some self hosted tile users go from $0 to tens of thousands of dollars a month in usage. It’s shady, don’t lie to yourself.
This only happens if the developer deliberately upgrades and adds a token. If you do nothing and you keep using v1 - nothing changes for you.
That's the implied threat. Our business puts serious engineering efforts behind maps, such that it takes months of effort to change out mapping clients. We do this across three platforms. It will continue working for a while, but that $250k we just spent will need to be re-spent in the next 1-2 years as the old library falls to the wayside.
The frustrating thing is that we just went through this with google. We paid a reasonable amount, but then got extorted to pay more or jump ship. We jumped ship to a reputable company, mapbox, and we paid a reasonable sum of money for how we used the software, and now the cycle continues. To be clear, I am not complaining that we are paying $0 and we should get the benefits for free. I am saying that we shouldn't be jumped up multiple orders of magnitude in cost, which isn't in-line with our actual usage. That's the shady part.
No not really. The goal is to stay simple - just display polygons, linestrings, points and their associated metadata.
It is really meant for prototyping SQL queries quickly with immediate feedback.
What might make sense is to support to display several SQL queries at once. So you can show the the objects within a cluster and the cluster bounds at the same time.
For complex visualizations you can use e.g. QGIS with PostGIS as data source.
I used PostGIS editor before to prototype clustering SQL queries. I assign cluster values as attributes and inspect them like this.