Open maning opened 5 years ago
Komzpa
commented
5 years ago Can OAM export a json in compatible format? Then editor-layer-index can just periodically pull it.
Also, even current 9793 images are good for OSM mapping but probably will break editors trying to download and work with this linearly. Can a global OAM mosaic be exported instead, and just contour of it be updated?
maning
commented
5 years ago Can OAM export a json in compatible format? Then editor-layer-index can just periodically pull it.
AFAIK, yes, https://api.openaerialmap.org/meta
Also, even current 9793 images are good for OSM mapping but probably will break editors trying to download and work with this linearly.
That maybe true.
Can a global OAM mosaic be exported instead, and just contour of it be updated?
Devs can probably chime in, but I like this idea.
grischard
commented
4 years ago Hi, ELI dev here! The corresponding issue on our side is https://github.com/osmlab/editor-layer-index/issues/509.
The json produced by https://api.openaerialmap.org/meta doesn't look like it fits the ELI schema.
https://github.com/osmlab/editor-layer-index/issues/586 might also be part of the solution.
Do you already have a solution that provides imagery only within a certain bbox?
Context We have been adding drone imagery in several areas, latest is Lupang Arenda, in order to make it available to most mappers we are also updating the editor-layer-index so that it will be suggested by editors to mappers even if they are not aware of OAM.
Ask Is possible to auto-generate layer index for consumption of editors via editor-layer-index, for example, if someone uploads to OAM, the user will be asked if they want it shared automatically for OSM editing then creates a PR to the editor-layer-index?