Moritz Schott

One solution could be to thoroughly plan one use-case, implement it with the current functionality and add it to https://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/oshdb-examples (with a note saying _please signal your interest in this...

yes, if I remember correctly it the chapter is about spacial data but the first atmospheric task is about a time series with no geographic component

If your goal is to color your COG then the library already includes the required functionality if you use the `readRGB` function: https://github.com/geotiffjs/geotiff.js/blob/4af107db0b0a8b46213d444de924575b5c9255da/src/geotiffimage.js#L646 Note that if you use this library...

this is just a design question so I added the low-priority as it does not affect functionality. If I understand correctly the problem is the lazy creation of geometries, correct?...

related: #52 , https://github.com/GIScience/oshdb/issues/349, https://github.com/GIScience/oshdb/issues/170,

see https://osmcha.org/api-docs/ for another example of how authentication could work

yes, there is no issue with the result itself, each response is unique. It is more about style and ease of user side processing. Most users probably want to link...

> > So what is the difference between the response of /fullHistory vs. the response here of /contributions? > > To me the main difference is that `/elementsFullHistory/` not only...

> we want filters to be based on the full/unclipped size of the features, regardless of the state of clipGeometry sounds good. I suggest to mention this explicitly like: _Note...

regarding the documentation, we might even be more specific and mark ALL post-processing steps as such. E.g. I think the `boundingbox` or `centroid` endpoints add post-processing steps that follow the...