Request: Provide imagery capture date on tiles if possible

[bgirardot]

Right now only for Bing, you can use JOSM to right click on a tile and it will show data about that tile. The last data item is always the "capture date" as in this screen shot:

This is really important info and the more we do with OAM the more important easy access to that information from teh tools we are using will become.

Seth pointed out that data is from the http header sent with the image as show here:

If OAM could support sending that header info as well, that would be amazing. Most of us work in JOSM during crisis mapping and coordination and as we get more and more integrated with imagery providers, and start making more and more use of OAM easy, quick access to capture date is really important.

[cgiovando]

I would take this a step further and suggest that we find ways to automatically add source=* and source:date=* to each feature tag set (not just changeset) based on what image tile is displayed when it's being traced.

Manually querying tiles in JOSM is definitely a good start, but structuring the workflow and capturing source imagery info automatically would make things much better in the long term.

If XYZ tiles of each OAM TMS can systematically tie to source OIN images, then the call could be done on the OAM catalog instead of encoding that metadata in the TMS header?

See also https://github.com/openstreetmap/iD/issues/2492#issuecomment-101469913

CC: @bhousel

[bgirardot]

imagery_used I think is the iD tag that auto gets added to changesets. If we could pass that + the date, that would be great. and a reference back to the OIN imagery. As it is now, it might say the imagery, but if I don't know where to find the tms endpoint for it, it does not help a lot. There is a bug somewhere in the Tasking Manager that puts the tms url in for source, which I actually leave in place because it is mroe helpful than just saying "COSMA Drone imagery 2014"

[mojodna]

Depends on #7.

[mojodna]

I'm now exposing all the relevant headers I can think of right now. Sample response:

HTTP/1.1 200 OK
Server: gunicorn/19.6.0
Date: Mon, 23 Jan 2017 19:48:03 GMT
Connection: keep-alive
X-OIN-Metadata-URL: http://oam-dynamic-tiler-tmp.s3.amazonaws.com/58851a5d12c76d0010a745f0/0/26357bb1-0f4f-4f7c-bbec-d72851425e0f_meta.json
X-VE-TILEMETA-CaptureDatesRange: 11/15/2013-11/16/2013
X-OIN-Acquisition-End: 2013-11-16T00:00:00+00:00
X-OIN-Platform: Kite
X-OIN-Acquisition-Start: 2013-11-15T00:00:00+00:00
Content-Type: image/png
X-OIN-Provider: Test Provider
Content-Length: 171196
Access-Control-Allow-Origin: *

I closed this issue as it deals with exposing information for other tools to consume. @cgiovando can you re-open in an appropriate place? (iD, Tasking Manager?)

[mojodna]

Something's missing; JOSM isn't showing the capture dates even though they're present:

curl -I http://tiles.openaerialmap.org/588b75db2be03d001038e380/0/92c680e6-91e9-4456-8478-c204b33e91a6/17/127175/72728.png
HTTP/1.1 200 OK
Content-Type: image/png
Content-Length: 0
Connection: keep-alive
Date: Fri, 27 Jan 2017 18:33:59 GMT
Access-Control-Allow-Origin: *
x-amzn-Remapped-Content-Length: 106929
x-amzn-RequestId: 2a8a6d17-e4bf-11e6-9e1a-b17737156652
X-Amzn-Trace-Id: Root=1-588b9296-6381af6b0f4924cda62954f9
X-OIN-Acquisition-End: 2015-04-06T09:30:00+00:00
X-OIN-Acquisition-Start: 2015-04-06T08:30:00+00:00
X-OIN-Platform: uav
X-OIN-Provider: Government of Vanuatu
X-VE-TILEMETA-CaptureDatesRange: 4/6/2015-4/6/2015
Via: 1.1 4bdd691513290fe917f758cc5b73b9ef.cloudfront.net (CloudFront), 1.1 4a55d86b7263f73c6817c7c25d4b3643.cloudfront.net (CloudFront)
X-Cache: Miss from cloudfront
X-Amz-Cf-Id: V68sTP8fWO0BzxWbBcg3uULqkqY_YtlG0sO-04oFunY9OTphTIFIkA==