OpenAerialMap: A Distributed Commons for Searching and Hosting Free Imagery
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 183 | |
| Author | ||
| License | CC Attribution - NonCommercial - ShareAlike 3.0 Germany: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this | |
| Identifiers | 10.5446/32065 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language | ||
| Producer | ||
| Production Year | 2015 | |
| Production Place | Seoul, South Korea |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
00:00
Category of beingTexture mappingAdditionMappingSelf-organizationFreewareOpen setExpert systemMultiplication signProcess (computing)Computing platformSubject indexingResultantBitRoundness (object)Open sourceMereologyPhysical systemSatelliteFormal grammarPoint (geometry)Computer animation
03:16
Open setMoment (mathematics)Beta functionMappingSubject indexingProcess (computing)SoftwareImplementationBuildingRepository (publishing)AreaSymmetry (physics)Texture mappingWordMedical imagingStandard deviationConnectivity (graph theory)MetadataXMLUML
05:26
Multiplication signGroup actionOpen setCASE <Informatik>Server (computing)DiagramShared memoryOnline helpComputer animation
06:39
DiagramMappingCASE <Informatik>Web 2.0Dependent and independent variablesInternet service providerConnectivity (graph theory)Computer configurationProgram flowchart
07:16
Open setComputer programmingOpen sourceBitPlug-in (computing)Texture mappingFlow separationUser interfaceConnectivity (graph theory)Repository (publishing)Server (computing)Personal digital assistantOnline helpSoftware testingRight angleMetadataQuicksortGroup actionPerturbation theoryLibrary catalogWeb browserTesselationProcess (computing)Source code
10:48
Repository (publishing)Point (geometry)Local area networkMultiplication signSoftware testingProcess (computing)SoftwareNeuroinformatikDifferent (Kate Ryan album)AreaOnline helpBand matrixTime zonePoint cloudCASE <Informatik>Open setEmailMappingGroup actionLattice (order)Direction (geometry)Uniform resource locatorFile archiverElectronic data processingTexture mappingSelf-organizationPhysical systemCloud computingRoutingElectronic mailing list
13:45
Subject indexingOpen sourceOpen setMoment (mathematics)Right angleMappingCASE <Informatik>Different (Kate Ryan album)QuicksortMereologyCuboidGoodness of fitPresentation of a groupBounded variationEmailSoftware developerWhiteboardReal numberAreaMedical imagingTesselationTexture mappingPoint (geometry)Attribute grammarCovering spaceServer (computing)Latent heatSoftwareIdeal (ethics)Set (mathematics)Unitäre GruppeComputing platformMultiplication signView (database)TheorySoftware testingField (computer science)Library catalogPhysical systemXML
21:40
BitGroup actionRevision controlQuicksortBuildingRight angleTexture mappingOpen sourceOpen setOnline helpAveragePrototypePoint (geometry)Scaling (geometry)Service (economics)Web browserServer (computing)Process (computing)SatelliteMoment (mathematics)AreaIntegrated development environmentBit rateLatin squareMoment <Mathematik>MappingFlagRow (database)Medical imagingXMLUML
25:52
SoftwareStandard deviationImplementationLibrary catalogMetadataOpen setTexture mappingDifferent (Kate Ryan album)Beta functionMultiplication signMappingVideo gameWeb crawlerRepository (publishing)XMLUML
27:05
Multiplication signGroup actionAreaMappingCASE <Informatik>Open setShared memory
27:46
CASE <Informatik>Streaming mediaDiagramAreaBand matrixNeuroinformatikRaw image formatCartesian coordinate systemTesselationQuicksortProgram flowchart
28:36
Plug-in (computing)Set (mathematics)TesselationCodeSoftwareServer (computing)Group actionProcess (computing)CodeLibrary catalogComputer programmingOpen sourceTexture mappingAttribute grammarOnline helpMereologyMultiplication signWeb browser1 (number)Different (Kate Ryan album)Connectivity (graph theory)SphereBitOpen setComputer animation
30:52
Touch typingTesselationOpen setMappingConnected spaceOpen sourceWeb applicationMedical imagingCASE <Informatik>Process (computing)BuildingSubject indexingDependent and independent variablesQuicksortPhysical systemPoint cloudTexture mappingSearch engine (computing)SoftwareRight angleVapor barrierEmailLattice (order)BitInternetworkingPointer (computer programming)Repository (publishing)Personal digital assistantCartesian coordinate systemShared memoryUtility softwareComputer configurationGoogolGroup actionCopyright infringementWeb pageArithmetic mean
34:22
Open setFormal languageTexture mappingMaxima and minimaCategory of beingTemplate (C++)MetadataRight angleCASE <Informatik>Natural numberPoint (geometry)Perturbation theoryDesign by contractQuicksortSoftwareArithmetic meanMoment (mathematics)Raw image formatChainMedical imagingInformationVector potentialSelf-organizationProcess (computing)Mobile appLatent heatInternet service providerEndliche ModelltheorieOpen sourceStreaming mediaSingle-precision floating-point formatDistanceWave packetIntegerDecision theoryState of matterLengthFood energyMassComputer animation
41:41
Computer animation
Transcript: English(auto-generated)
00:03
Thank you. Just to introduce myself, I work for the Cadastre Foundation. We help communities document their property rights, primarily in places where people don't have formal land cadastral systems. We are interested in open aerial map because part of that process is you need
00:26
imagery to enhance your mapping. I'm going to start off with a little bit of history and background on open aerial map. The idea of creating a commons for sharing free and open imagery came
00:44
about around 2006. There were people that were beginning to fly UAVs and drones, but it was really mostly just an idea at that point. Then in 2010, there was a large earthquake in Haiti and a lot
01:01
of imagery became readily available. For example, the World Bank flew imagery through aircraft and made that available under an open license. But there wasn't really a good platform to share that, to process it, to index it. A lot of technologists were just doing, were spending large amounts of time processing and making that imagery available.
01:24
So this idea of open aerial map, once again, became very important. Then there's been other major disasters as well, but we're also beginning to see more imagery being available just because there's more commercial satellite agencies, governments are launching satellites and providing that data for free under open licenses as well as UAV usage.
01:58
As we see this, technical experts are able to access that imagery, but the average person, there's not really a way to do that.
02:09
So that's really what we're trying to do. Open aerial map was rebooted last year by the Humanitarian Open Street Map team.
02:20
One thing I should have prefaced is until April of this year, I was executive director of the Humanitarian Open Street Map team. So I was involved in obtaining a grant from the Humanitarian Innovation Fund to build out a pilot of open aerial map. And that one year grant is ending in October next month of this year.
02:44
In addition to HOT, the Humanitarian Open Street Map team, there's also quite a few organizations involved in the open aerial map community. We've come together because people were working on their own imagery indexing tools as well as processing tools,
03:04
and we thought, why don't we work together, one of the beauties of open source, rather than continuing to do things on our own. And this is all powered by the Open Imagery Network.
03:21
So the Open Imagery Network is a distributed index of open imagery. It actually is just a GitHub repository. So if you had imagery and you had it hosted somewhere, you can go register on GitHub your bucket of imagery,
03:41
and then it would be registered in the Open Imagery Network. The idea of that index is then people can build tools on top of it. So it's essentially just pointing to where the imagery is. And there's a very lightweight metadata standard that's a component of that. And so the way the Open Imagery Network and Open Aerial Map work together is that
04:05
Open Aerial Map is the first implementation of imagery tools using the Open Imagery Network. It's a little confusing, but the Open Imagery Network is the actual imagery, and then Open Aerial Map is the tools to index and process and use that imagery.
04:27
I forgot to check in with the Open Aerial Map team, so I'm not sure if we're out of beta yet. Open Aerial Map's been in beta for the past couple months. So you can try going to this URL, but beta.openaerialmap.org is where it may reside at the moment.
04:46
But we're switching over out of beta sometime in the next week or so. And you'll see up there, there's not a ton of imagery yet, but there's certainly imagery for an assortment of areas the whole world has not covered.
05:05
Primarily a lot of imagery related to work the Humanitarian OpenStreetMap team was doing, or related to disasters that have happened where there's been imagery released. So there's imagery of Nepal, for example, and there's also imagery of Tanzania taken by UAV through a World Bank project this year.
05:28
So in building Open Aerial Map, we were looking at two major use cases. The first is those users that are not highly technical who need to find and use imagery.
05:41
And then there's this other use case where there's people who actually want to share, but sharing imagery is hard. I mean, you have gigs and gigs of data, and people maybe don't have a server to host it on, for example. So we wanted to give them somewhere that they can upload it. Because when people want to open up their data, there needs to be a way to say,
06:02
oh, thank you very much, and then help make it useful. Neither of these groups are highly technical remote sensing specialists, though. And the one I think is particularly interesting is the users with imagery that need to upload and share. One user group in there is hobbyist drone pilots who go take imagery,
06:26
and then, you know, there's not really a commercial value. They'd like to share it, but they're not going to take the time if it's difficult to share it. So we're giving them a place where they can upload it.
06:40
And so this is a diagram of how one might discover the imagery. There's two situations that we think about, especially open aerial maps primarily started for humanitarian and disaster response. It's not the only use case, but it's the first use case. So you'll notice we focus on both online and offline.
07:03
So we provide web tiles, for example, that you could use online, but if you actually needed to download the imagery and take it with you, that's an option as well. So there's three major components to open aerial map.
07:21
So there's a web interface browser, which is what you see if you go to openaerialmap.org. There's also a catalog, which is more of an API of that index. And then there's also a server component that does processing. Primarily, it can take raw imagery and turn it into tiles. And these are all separate projects within GitHub that you could contribute to.
07:48
Then there's another, we're starting to build a bit of an ecosystem around open aerial map. There's also a QGIS plugin that allows you to both search imagery, download it, as well as upload it.
08:00
This was developed through a program called Outreachy. Outreachy used to be called the Gnome Outreach Program for Women. It is very similar to Google Summer of Code, and it's a paid internship where you work with an open source project given to women and other minority groups in open source.
08:23
So one of the projects that HOT sponsored this year was building of a QGIS plugin. And the GitHub repository is right there, and then I'm going to show a couple screenshots.
08:41
So it essentially allows you to both, maybe it's a bit hard to see, but there's buttons for searching, browsing, as well as downloading imagery. It's meant to be sort of a wizard, be easy to use. And here is where, if you were uploading data,
09:03
you can see the JSON metadata requirements, as well as you can pick where you're uploading it to. Currently, we only support Amazon Web Services for the upload buckets. And in this case, they're just using a test one,
09:22
but the Humanitarian OpenStreetMap team provides one, because we want people to share imagery. But you could also use this with your own bucket of imagery as well. So the big reason I'm here is also to help recruit.
09:43
There's lots of ways to get involved. There's quite a few people coding, but of course, pull requests are always welcome. Testers would be great. Doing community outreach. So I'm contributing to the OpenAeromap community right now. Documentation.
10:01
And another one that I don't see a lot of projects asking for help with so much these days is legal help. And the reason I mention that is we're getting imagery under an open license. So sometimes legal assistants could help discuss with companies how they might do that. You probably don't even need to be a lawyer.
10:22
An open data advocate could certainly help. And the final one, do you have imagery? We're continuing to build out a repository of open imagery. Like I said, there's not a ton there now, but there will continue to be more and more added.
10:41
So if you can help contribute, allowing other people to use your imagery, that would be great. So if you do want to contribute imagery, there's a couple different ways. One, if you go to GitHub and the Open Imagery Network organization, there's a repository there
11:00
that walks you through how to register. And you essentially are just adding yourself to your Amazon S3 bucket, your bucket of imagery, you're adding it to this. And then it allows anyone who would want to go and crawl your imagery to be able to do that.
11:21
This is another way of doing it. You can simply just upload through Open Aerial Map. And in this case, what that does is you're contributing your imagery to the Humanitarian OpenStreetMap team bucket. So if you don't want to mess around with getting an Amazon account or you don't have the time or any other reason,
11:41
you can just contribute it directly there as well. This is still in testing and it's going to be released more formally in the next couple of weeks. And so if you want to get involved in Open Aerial Map in general, there's quite a few GitHub repositories
12:00
for the various pieces of the project. But if you go to this one, it's the main one, it'll point you in the right direction. We also we also meet weekly on Gitter. So if you go to that GitHub that GitHub URL there's a button that says Join Gitter.
12:22
It's just a chat room where you can log in with your GitHub account. It's very easy to use. So there's live meetings at 1800 GMT for about an hour every Thursday. We usually have about 5 to 10 different people participate. And you can always, if it's not time zone friendly for you, you can always read the archives as well.
12:43
We also have a mailing list, a Google group. You can join for offline discussion there as well. There's a few things we're thinking about in the future. One of the big things is right now we're only integrating with Amazon, but we want to be able to use
13:00
other cloud based systems as well. As well as having an offline appliance. So one of our major use cases for this was after a disaster, people needing imagery. And so it can, it's great if you have a ton of imagery available online, but if people can't access it because they have very little
13:21
bandwidth or no bandwidth due to a disaster, it doesn't do much help. So we want to be able to deploy this on a computer where it could go to a disaster area and imagine someone is flying a drone to take pictures of it. And then you could upload it directly onto your local computer and your local area network and then actually have it, process it and make it available.
13:46
So that's Open Aerial Map. Are there any questions? Some questions over there. At the moment, we're sort of doing
14:10
best case scenario. I think that Tyler will handle converting over to different reference systems, but
14:20
to be honest, I think you can define them in the metadata, but because if you go, but to be honest, I can't remember exactly how we're dealing with them. Any other questions over there?
15:00
So the moment
15:01
we're not creating a mosaic, it's more so if you go look at the catalog, you can see what imagery is available and it overlaps and you can pick which either download as a geotiff or use, but we're not trying to create a mosaic right now.
15:21
The idea would be if someone wanted to build their own, we have a source, we have an index where they could go look and find the best sources. Yeah, you can do, you could do a combined set,
15:41
but in most of the case, the major use case right now is the needing to load a tile set to edit an open street map, basically. So you probably are editing a small area and you just need that one image. Right.
16:02
Any other questions? Yes, Kari, please. Sometimes the real big need for imagery is in countries that don't want you to publish any open imagery. What kind of
16:20
scenarios do you anticipate these cases? Well, OpenStreetMap runs into the same problems. As a board member of the OpenStreetMap Foundation, I see a lot of those emails. I think the best, honestly, I think it's going to be a matter of having a policy.
16:42
And, you're right, it's sort of a political slash legal question depending where the servers are as well. I don't think we've really thought a lot about it, to be honest, so far. But yes, definitely that will potentially be an issue.
17:00
Other questions from the floor? There, in the back. Sorry, we were running ahead, but if anyone wants to talk to me afterwards, we can definitely discuss.
17:22
I actually have one question myself. So, do you recommend any specific kind of licensing for the imagery? So, that's a good point, and something I should have covered. With the open imagery network, we are doing one license, which is us doing ideal best case scenario, and we're doing a creative
17:42
commons attribution license. With Open Aerial Map itself, it uses the open imagery network, but it also uses other imagery under other licenses as well, because we realize that, if we're negotiating for open imagery, we can say hey, you should use this license, but if it's
18:02
already open, then it would be difficult to try to change that. Over there? I do love chickens.
18:21
So, I apologize for those arriving at this point to this session, because we are just about to close this work session. We have already had our wonderful presenters ahead of time, actually, complete their talks, and actually, I must
18:41
say that this is something that proves the capability of open source and open data to actually help facilitate development in the world, and also even save people's lives in the end. So that's a very supportable initiative.
19:01
So, basically, do you have any questions for any of the speakers at this time? So, about OSCARI mapping platform, about aerial imagery, or about the geoprocessing tool for UNIC.
19:21
So we have heard three great presentations and very varied topics, or different kinds of projects, and I think this also tells about the diversity of open source. We are engaged in so many kinds of activities. This is a good example. This session is a good example of that.
19:44
In case there are no further questions, I will ask you to applaud to the three presenters. And before you go, I'd like to give you a little something to take with you back from Seoul.
20:00
This is actually a little box of penis liquorice. So be careful if you have never tasted it. And if you want OSCARI stickers, Hannah will hand out them for you. Thank you very much for your participation.
20:21
Not on.
21:17
By popular demand,
21:20
and people in the hallway, Kate's going to reprise her talk because we've got a lot of folks who missed it. So, without any further ado, open aerial map part two, or part one again.
21:45
I'll be fine. Thank you. This is good. There's a couple of people who have been involved longer than I have who have now come into the room as well. So
22:02
open aerial map is a distributed commons for searching and hosting free imagery. And I wanted to go a bit into the history and the background. I think this became an idea in 2006. I said that very authoritatively in the first version of the talk because Jeff Johnson wasn't in the room to correct me.
22:22
And so it started as this idea of people were flying UAVs, UAVs were starting to produce imagery, and the question was, what do you do with that imagery if you want to have it under an open license? And so this idea of open aerial map became mostly an idea at that point.
22:42
And then in 2010 there was the large earthquake that happened in Haiti, and a ton of imagery became available. There was very detailed 6 to 8 centimeter imagery of the earthquake affected area that the World Bank flew and then released under a permissive license. And then there was some of
23:01
the satellite companies and just a lot of imagery. And people were staying up all night to process it, to make it available in a pretty manual process. And it was all going on some telescience servers that was sort of a sort of the wild west of imagery services.
23:22
And the question then was, could we make this easier on ourselves? And then there were quite a few other large scale disasters where a bunch of imagery was available, but still not open aerial map didn't really exist. There was a brief little bit of funding from MapQuest to
23:41
build it out, but it was mostly a prototype at that point. And so imagery has continued to be available under more and more open licenses. And so this need for open aerial map has become
24:00
greater. And we're really focused on your average web browser user. We're not focused necessarily on remote sensing specialists, because they can go find the free imagery. But let's say even if you go find the imagery and you don't know how to use it, that's not real helpful.
24:20
So we're really focused on the non-experts. So open aerial map was rebooted last year by the Humanitarian OpenStreetMap team through grant funding from the Humanitarian Innovation Fund. I was at the Humanitarian OpenStreetMap team when this happened,
24:42
and I was involved in obtaining this grant funding, essentially. I left hot in April of this year. I'm still up here waving the open aerial map flag, because my role at the Kadasta Foundation is we're building open source tools to help communities document their land rights.
25:00
Turns out you need imagery for that as well. so open aerial map has started very focused on disasters and humanitarian use, but there's other groups like myself at Kadasta who need it as well and are very interested. This is sort of the main OAM community at the moment.
25:24
With the grant funding from the Humanitarian Innovation Fund, a few of these groups have been involved in actually building things out. And we've also been working with OpenDroneMap. Stephen is around the conference, I believe giving a talk on this tomorrow.
25:44
OpenDroneMap actually does all the processing, so you end up with a nice GeoTIFF, which you could then put into open aerial map, so we're working closely together. So this is all powered by the open imagery network. So when we were designing open aerial map, the question then
26:01
was, what is it? It's been talked about since 2006. So it means a lot of different things to different people. And we wanted to create the open imagery network, which is actually a network of the open imagery. Essentially it's a GitHub repository, where you can go register your bucket of imagery. There's a
26:21
GeoJSON metadata standard that goes with it. You register your bucket of imagery there, and then someone could go crawl it. So open aerial map is one of the first implementations of software using the open imagery network. So I didn't check between giving this talk the first time and the second
26:40
to see if this is live. They were supposed to release it out of beta. It was at beta.openaerialmap.org until well, maybe still. But we're leaving beta sometime this week. I don't know if they, like I said, flipped the switch. I should have checked before my talk. But you can go there and see
27:01
how the catalog works and actually use open aerial map. And that's focused on these two main use cases. Users of imagery that need to find and use imagery. This could be a humanitarian worker. This could be a group doing community mapping. And then those users
27:21
that have imagery that want to upload and share it. A lot of those users are imagine your hobbyist drone pilot or professional drone pilot for that matter who's paid to fly an area and then they're allowed to release the imagery under open license. They don't want to take the time to figure out how to share it
27:41
so we're trying to make it really easy so we can say thank you for your contribution. And this is sort of a diagram of those use cases. A lot of our use cases are really focused on open street map right now. How can you get imagery and download it into
28:02
JOSM or use OpenStreetMap.org to edit. But also there's other use cases where if you just essentially need imagery tiles for your application. Both online and offline were important to us. So that you can always download the raw imagery. So you can take that with you in the humanitarian
28:21
use cases. For example you don't necessarily have enough bandwidth to be accessing imagery. But you can imagine downloading that onto your computer prior to deploying to a disaster area and then using it there. There's three major components. So there's the browser which is what you would see at open aerial map
28:42
dot org. There's a catalog which is essentially the API. And then there's a server that does processing. For example tiling. We also have a QGIS plugin. I like to pitch the QGIS plugin a little bit. One of the main reasons
29:00
is it was developed through the Outreachy program. Which is a program through the Software Freedom Conservancy. Which allows which gets underrepresented groups involved in open source. It works very similar to Google Summer of Code in that it's a 12 week paid internship. But it can be doing anything in open source.
29:22
It can be marketing, documentation, coding. So it's a little wider and it runs twice a year. So it's also Southern Hemisphere friendly as well. Which is one of the big complaints sometimes about GSoC. And this is the first desktop tool for OAM. But we're hoping that other
29:42
software will begin to integrate with it as well. So it's a pretty typical QGIS plugin. You can go search for imagery. You can upload your imagery. And then you can do some basic editing of your settings as well. So
30:03
hopefully you're all here because you want to help. There's lots of different ways to help. I put coding at the top but to be honest there's some of these other ones that would be really great. I think community outreach is something where we could really use help. Because we want people to share imagery. So just asking
30:20
a lot of times is a good way to get that. Documentation. Always important. As well as legal help. And that's part of if groups do want to open their imagery, what's it mean to release your imagery under a Creative Commons attribution license for example. Fairly
30:41
typical open data problems. And do you have imagery? Looking for contributors in that way as well. So one of the ways to get involved in sharing imagery is you can go to github.com, open imagery network.
31:03
And if you're willing to host your own imagery you can go register your bucket of imagery there. And what this does is it's just essentially a text index where someone can then crawl all the imagery buckets, index them, picture sort of how a search engine works. And then
31:20
build tools on top of it. Open aerial map for example being one of those tools. Not the greatest screenshot I've taken but you can also upload. So the Humanitarian OpenStreetMap team is providing an S3 Amazon bucket where you can upload your imagery and it goes into
31:41
Hotz bucket in this case. I would envision this use case being more like you flew your drone and you have one image to upload. The bucket use case would be you have a ton of imagery that you want to share. You can also get in touch with us as well. If you go look through the Open Aerial Map
32:02
GitHub tickets, there's people who have imagery who open tickets and ask for assistance as well. And so this is sort of the pointer project. I feel like these days a lot of open source projects, it gets a bit confusing because you end up with 10 GitHub repositories
32:21
for essentially one web application. So this is your starting place. So if you want to connect to the community we have weekly meetings at 1800 GMT. We meet on Gitter. If you're not familiar with Gitter it's kind of like our IRC. Basically if you go to the Open Aerial Map
32:40
GitHub page, there's a big button that says Join Gitter. And if you click on it, you're in Gitter. And we've found that's a little bit easier as far as barrier to entry to get non-technical people involved in essentially IRC. You can also join the mailing list. There's an
33:04
option. So there's a couple other things we're thinking about in the future. Right now it's heavily dependent on S3. We want to make it deployable and integratable with other cloud systems as well to give some options. As well as have offline appliances. The offline appliance
33:20
scenario is primarily focused on humanitarian response. I'm sure there's other use cases where more and more UAVs are flown after a disaster now. But then that imagery isn't always that useful these days. People either can't get it off the ground
33:40
to the internet so that they can do processing because there's no connectivity. Or people might be really good at flying UAVs but they aren't so good at doing anything with the pictures once they have them. So this offline appliance, someone would be able to take it with them to a humanitarian crisis. Fly their imagery, put it on the
34:00
offline appliance, it would tile it, index it and they could use it on their own network is the idea behind this. Not requiring internet access. It's easy to forget I think sometimes that internet access still is definitely a problem. I'm sure it won't be forever but we can still save lives with this use case.
34:23
Any questions? Yes? So we want
34:41
GeoTIFs. The open drone map project is creating an open source tool chain to do that. You're taking the pictures off the drone and then ending up at GeoTIF which is why we're working with them. Because we're not focused on that at all. We're sort of doing the best case scenario where you're giving us a GeoTIF.
35:06
What's the nature and the searchiness of the metadata associated with any of this imagery? What metadata properties are you trying to capture? What's the minimum viable dataset?
35:21
It's actually pretty lightweight. I think there's seven or eight attributes. I'm drawing a blank on what they are but I can just pull it up.
36:06
Actually, maybe I'm in the wrong place and I've said this is too easy. Let's see.
36:23
There's no gatekeeper right now. Originally when we were discussing it it was getting really complicated. We're using the model of anyone can contribute. I suspect what will happen is let's say in a perfect
36:43
scenario that we have so much imagery that it's hard to figure out what you want to use that I hate to say reading the imagery but they'll probably preferred providers or something I could see at some point. To go back to Erin's question
37:01
so this is the metadata. You see there's not a lot. It's basically where is it a picture of a few little details about the actual imagery and some contact information.
37:20
Jeff. Can you explain more the intersection between Open Imagery Network and Open Air Map? I'm particularly interested in the policy side. On several different projects I work on we acquire imagery. It'd be nice to have some standard legal language to stick into these contracts when we purchase it so that
37:40
it can be open. I'm just on the policy side. Less about technical. This is what I think is going to happen. I think they'll end up being an Open Imagery Network Foundation at some point to support that when I don't know.
38:01
There's things needed like that. The technical problems are coming together on their own but the policy is actually the main issue.
38:21
I really think that advocacy and template language is what's going to be key to change that. I think an organization is probably going to have to support that. The Humanitarian Open Stream App team has been supporting this as it is now, but that's a really specific
38:41
use case in an organization with a specific mission. I suspect this will end up as its own thing at some point. We have a ton of process images from landscape, maybe
39:01
paint shaft and also generates like geotiff. Is that the imagery you want to share? Or why? Potentially. With Landsat I suspect
39:20
at least Landsat 8 which is already hosted on an S3 bucket. Ideally we'd want to just point to that bucket basically. But if there's other imagery that's not conveniently stored like that we would definitely be interested. By means you want to
39:44
create original imagery not processed imagery? We want raw imagery geotiffs. For this we said we're just focusing on
40:00
visible right now. That's a pretty common question. I suspect that could change but it was a matter of you have to start somewhere. To be honest I don't know. I haven't been
40:22
as involved in this project as I was when I worked for HOT. I'm not responsible for the Amazon bill anymore or that sort of stuff so I'm not sure.
40:50
That's true. There's actually, so at the moment there's only two buckets. I was thinking about the majority of it is in HOT's bucket. You could figure out
41:01
if you went to everyone's bucket you could figure it out. Since it's only two it would be easy right now. Aaron? And maybe it's too soon but has anyone thought about how the data gets replicated so that it's not just in a single bucket?
41:21
Yeah we haven't really worked on that but yeah definitely the offline use case definitely needs it and there's plenty of others as well. Thanks everyone. Applause