oshdb extract generator issueshttps://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/helpers/oshdb-extractor/-/issues2020-02-25T13:21:40Zhttps://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/helpers/oshdb-extractor/-/issues/5Implement option of H2 as a backend2020-02-25T13:21:40ZMoritz SchottImplement option of H2 as a backendIt should only be a small change to port this script to H2 where the user can extract a part of a larger OSHDB-H2 fileIt should only be a small change to port this script to H2 where the user can extract a part of a larger OSHDB-H2 filehttps://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/helpers/oshdb-extractor/-/issues/4Add option for .properties file2020-02-25T09:46:59ZMoritz SchottAdd option for .properties fileusing the tool with more and more command line arguments becomes difficult. I would propose to use a `.properties` file (or similar) insteadusing the tool with more and more command line arguments becomes difficult. I would propose to use a `.properties` file (or similar) insteadhttps://gitlab.gistools.geog.uni-heidelberg.de/giscience/big-data/ohsome/helpers/oshdb-extractor/-/issues/2extract by "set of user ids"2020-02-25T09:39:06ZMartin Raifermartin.raifer@heigit.orgextract by "set of user ids"follow-up from #1:
* return all elements edited by a set of userids
The tricky part here is that "edited" would - in general - also include users who only created "minor versions" of an object during an edit (e.g. the squaring of a bu...follow-up from #1:
* return all elements edited by a set of userids
The tricky part here is that "edited" would - in general - also include users who only created "minor versions" of an object during an edit (e.g. the squaring of a building, moving of an intersection, aligning of a river, etc.), which then are not directly observed in the uids associated with the "regular" versions of an entity.