morgenkaffee

Yes, this dataset is not CC BY-NC 4.0. Be careful.

Well done. Every conpany with maps otherwise needs their own daily diff server.

The challenge tho is running it over years reliably especially if something in upstream OSM breaks.

I use Docusign cause it looks official and grown up. With this product I worry about the name and domain name looking like phishing or a typo.

I am a fan of replacing docusign as a principle though.

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.

I really want to keep it a standalone style editor. The advantage is exactly that it is not bound to any external service.

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.

It is all magic of Clang or GCC. Once you call the template with T1 the C++ compiler will enforce that your passed type supports the <= operator.

Yes you would have to program in a subset of python. But type annotations are not always needed.

For the array I do a little hackery. You can define the array without an initial value in the container and I can guess the value type.

  arr = []
  arr.append(1)

it will spit out

  std::vector<decltype(1)> arr{};
  arr.push_back(1);