Rosario Trischitta

I already needed to create new attributes because I could not update the size of attributes. Please consider adding the feature.

It could be included here, but we didn't discuss it further since these are all breaking changes that we will introduce with the release 2.0 of the ohsome API. This...

related to #30

You can find two issues related to that here: #30 and #219. You are probably right, we could provide a link to osm-boundaries (the website is not related to us)...

> java.lang.RuntimeException: The timerange metadata could not be retrieved from the db. Regarding this error, [avoiding to extract](https://github.com/GIScience/ohsome-api/commit/feb534c47074ce8b7bf26bbf133ca6d42ca7f308#78) metadata for every request should solve the problem.

IMO, I think in case of hex grids and rectangular grids would be difficult to say how big a cell should be. The risk is that too big or too...

Solutions more or less out-of-the-box are [Spring Boot Actuator](https://docs.spring.io/spring-boot/docs/current/reference/html/actuator.html) and [Dropwizard](https://www.dropwizard.io/en/latest/getting-started.html#creating-a-health-check) (or maybe only the [Metrics](https://metrics.dropwizard.io/4.2.0/index.html) library) which is customizable for working with HikariCP. Both of them offer health checks...

Since the `clipGeometry` variable is set to `true` for all data aggregation endpoints, only data extraction endpoints are affected. The problem should be related to the filters themselves. @tyrasd what...

> **Would it be possible to explicitely add the `clipGeometry` parameter to the other endpoints and maybe rename it to `clipResult`? This would enable users to decide e.g. if they...

I also am for having it added to all endpoints. I think this is a coherent and expected behavior. I am not sure regarding the name since it is the...