OpenAerialMap/Meeting Feb 19, 2015

Feb 19 19:00:01Cristiano: Good morning, we're are about to start the OAM weekly meetingFeb 19 19:00:10Cristiano: (and good evening)Feb 19 19:00:10BlakeGirardot: Good morningFeb 19 19:00:47Cristiano: Here's the link to the agenda: https://docs.google.com/document/d/13oKAO9V0P33GW6nx3YiNu3wRxHfp24iklOu_mUHmmrQ/edit?usp=sharingFeb 19 19:00:58smathermather: Hi.Feb 19 19:01:13Cristiano: Hi smathermather!Feb 19 19:01:30Cristiano: Please add anything else that you would like to talk aboutFeb 19 19:02:26dodobas: I'm semi-AFK... will keep an eye on the chat... might not respond immediately Feb 19 19:02:31smathermather: Just reading through now.Feb 19 19:03:24Cristiano: Hi jj0hns0n!Feb 19 19:03:32jj0hns0n: hi Cristiano Feb 19 19:03:38Cristiano: Is wildintellect here?Feb 19 19:04:50Cristiano: Well, let's start. First, here's the link to the published tech challenge: http://hot.openstreetmap.org/get_involved/openaerialmap_catalog_tech_challengeFeb 19 19:05:47Cristiano: Please help to spread it. There's a two week period for proposalsFeb 19 19:06:21BlakeGirardot: Did we share it on the hot and osm email lists?Feb 19 19:06:37smathermather: Will share.Feb 19 19:06:55Cristiano: Not yet, please go ahead BlakeFeb 19 19:07:00smathermather: (in response to christianoFeb 19 19:07:01BlakeGirardot: Ok, will do.Feb 19 19:07:19Cristiano: I asked OSGeo to post on their @jobs list, but haven't received approval yetFeb 19 19:07:41Cristiano: but I guess we can post on @discuss if the job list is not used anymoreFeb 19 19:08:02Cristiano: (there hasn't been any post since October)Feb 19 19:08:52Cristiano: Anyway, any other community of open source devs that may be interested, please circulate, thanksFeb 19 19:09:59Cristiano: jj0hns0n: I'm sure you'll forward to Geonode and Django's :-)Feb 19 19:10:21jj0hns0n: most of the geonode folks have already looked at it, not sure if there is a geodjango specific list anymore?Feb 19 19:10:38jj0hns0n: I guess there is, not that activeFeb 19 19:10:52jj0hns0n: will alert the eoxserver guysFeb 19 19:11:03Cristiano: Cool, looking forward to their proposals!Feb 19 19:11:49jj0hns0n: Im curious if its intended to for only people who want to do the work to make proposals?Feb 19 19:12:42Cristiano: No, of course anyone's proposal is welcome. Here, through the list or GitHubFeb 19 19:12:57jj0hns0n: ok, sounds goodFeb 19 19:13:50Cristiano: I would also like to get your input on how to evaluate proposalsFeb 19 19:14:16wildintellect: technical and practicalFeb 19 19:14:33Cristiano: I would like to make that process as open and collaborative as possible, but making sure to preserve sensitive informationFeb 19 19:14:39jj0hns0n: yeah, 2 separate things as wildintellect mentionsFeb 19 19:14:47wildintellect: just assign them some score on a set scale for each propertyFeb 19 19:15:00wildintellect: technical - do they have the background and skillsFeb 19 19:15:20wildintellect: practical - work history, prev community experience, likelihood of completionFeb 19 19:15:47Cristiano: yes, I was not talking about the evaluation process per se, but how to form the evaluation groupFeb 19 19:15:49wildintellect: you can put the proposals with Names redacted into a a google doc folderFeb 19 19:15:56jj0hns0n: and I think it makes sense to consider the techical aspects of the proposal separatelyFeb 19 19:16:19wildintellect: then it's up to you and HOT to pick a group to score each sectionFeb 19 19:16:21jj0hns0n: is it a sound implementation, is it likely to be sustainable over timeFeb 19 19:16:51jj0hns0n: fwiw, I have used http://screendoor.dobt.co/ for a few projects to evaluate proposalsFeb 19 19:17:02Cristiano: I would like the process to be participatory, so I will think of the best method to involve you guysFeb 19 19:17:03wildintellect: so I would suggest Cristiano you pick or invite people to score each sectionFeb 19 19:17:32Cristiano: That's a good idea, I will check it outFeb 19 19:17:40jj0hns0n: Im sure they would give us a free subscription if we wantFeb 19 19:17:50jj0hns0n: code for america folksFeb 19 19:17:58wildintellect: obviously the people here are a portion of possible scorersFeb 19 19:18:14jj0hns0n: I guess the question is how many proposals do you expect?Feb 19 19:18:28wildintellect: with only 2 weeks to submit there might not be manyFeb 19 19:18:38jj0hns0n: I realize maybe its a bit too late in the game, but its good to do a kind of "Expression of Interest" firstFeb 19 19:19:27Cristiano: Yeah, unfortunately we needed to get things rolling, so hopefully we get enough good proposals in two weeksFeb 19 19:19:49Cristiano: and we may decide to extend it if we need toFeb 19 19:20:04jj0hns0n: yeah, makes sense to wait and see what you getFeb 19 19:20:17Cristiano: The application should not take longFeb 19 19:21:05Cristiano: 1 page for describing the proposal, 1 page resume and 1 page cover letterFeb 19 19:21:49Cristiano: Anyway, now unless there's any other comment about the tech challenge, should we start brainstorming the API?Feb 19 19:23:28Cristiano: wildintellect: please go ahead and edit the agenda with your proposalFeb 19 19:23:57Cristiano: or should we have a separate doc for dumping and sketching ideas?Feb 19 19:27:06Cristiano: wildintellect: I'm looking your proposed design in the agenda how do you define "node"?Feb 19 19:27:07wildintellect: its fine where it isFeb 19 19:27:20wildintellect: Node is a discrete computerFeb 19 19:27:32jj0hns0n: I would say single container whether virtualized or bare metalFeb 19 19:27:38wildintellect: yes containerFeb 19 19:27:39Cristiano: in my understanding there could be catalog and processing on the same computerFeb 19 19:27:44wildintellect: yesFeb 19 19:27:49Cristiano: (for the portable options)Feb 19 19:27:52wildintellect: but they are independentFeb 19 19:27:55wildintellect: of each otherFeb 19 19:27:58Cristiano: OK coolFeb 19 19:28:25Cristiano: because I feel node may be confused with instanceFeb 19 19:29:19jj0hns0n: wildintellect "Distributed tile processing" you mean tile generation right?Feb 19 19:29:39wildintellect: not sure I just moved itFeb 19 19:30:07wildintellect: but in the old OAM there was some processing to convert images into most usable formatFeb 19 19:30:09jj0hns0n: well, the question is more whether you would want to do actual imagery processing here or simply tile generationFeb 19 19:30:17wildintellect: not necessarily tile seedFeb 19 19:30:19jj0hns0n: ok, that would be image pre-processingFeb 19 19:30:26jj0hns0n: not done on the tiles but on raw imageryFeb 19 19:30:38Cristiano: I would not include other image processing other than reprokjecting and tilingFeb 19 19:30:40jj0hns0n: reprojection, stretches, clipping etcFeb 19 19:31:06jj0hns0n: so, Im going to edit thisFeb 19 19:31:07wildintellect: right, the classic example is the conversion of from RGB to YC...Feb 19 19:31:21wildintellect: to get huge file size savingsFeb 19 19:31:27jj0hns0n: hows that?Feb 19 19:31:44wildintellect: you familiar with the telascience NAIP 2009Feb 19 19:31:46jj0hns0n: there you goFeb 19 19:31:48jj0hns0n: yes :)Feb 19 19:31:55wildintellect: that processes and stuff like itFeb 19 19:31:56jj0hns0n: you should ask winkey all the stuff he had to doFeb 19 19:32:04jj0hns0n: yeah, I think I listed the main ones nowFeb 19 19:32:11wildintellect: I plan to since new NAIP is outFeb 19 19:32:25Cristiano: any process that is not fully automatic should not be part of the processing nodeFeb 19 19:32:38Cristiano: it should be done before by the submitterFeb 19 19:32:49jj0hns0n: nah no wayFeb 19 19:33:02jj0hns0n: you cannot ask them to give you files in the optimum format for tilingFeb 19 19:33:05wildintellect: Cristiano, we're talking about optimizationsFeb 19 19:33:07jj0hns0n: they will give you jp2k or mrsidFeb 19 19:33:07smathermather: Any need / intent to handle feathering / seam matching / histogram matching... ?Feb 19 19:33:08jj0hns0n: etFeb 19 19:33:09Cristiano: ideally we only ingest ready-imagery (or almost ready) and just compress it, convert it, reproj and tile itFeb 19 19:33:19smathermather: (between datasets)Feb 19 19:33:30jj0hns0n: ready imagery can be a huge jp2k that is in a strange projectionFeb 19 19:33:45jj0hns0n: and you still have to convert that to the most optimal format for quickly rendering tilesFeb 19 19:33:48Cristiano: that's fine, then it's all automatic processing to make it readyFeb 19 19:34:04jj0hns0n: yeah, it more or less goes in the order we have there under UploadsFeb 19 19:34:12Cristiano: right. I'm saying, we should not include functions that require user interventionFeb 19 19:34:17jj0hns0n: oh noFeb 19 19:34:32smathermather: There are good out of the box tools for automatic translation of format and projection -- not for all use cases / uploads, but for a lot.Feb 19 19:34:38jj0hns0n: whether uploading an individual file or indexing a directory, it should just 'go' from thereFeb 19 19:35:07jj0hns0n: yeah, crschmidt figured out the really most optimal formats for rendering tiles as quickly as possible, gdal can do everything necessaryFeb 19 19:35:45jj0hns0n: its very inefficient to render off of things like mrsid or jp2k especially if reprojectingFeb 19 19:37:27wildintellect: right you'd have to decompress it firstFeb 19 19:37:47jj0hns0n: yepFeb 19 19:37:56jj0hns0n: so all of that stuff goes on in pre-processingFeb 19 19:38:03jj0hns0n: but requires no user intervention if done correctlyFeb 19 19:39:02jj0hns0n: you should make it clear that a tile 'node' could also just be something like S3Feb 19 19:39:14smathermather: So if there are standards for upload format that are restrictive, I assume there will be good, easy to use tools to point people to for client side pre-processing... .Feb 19 19:39:29jj0hns0n: smathermather I think that would be backward thoughFeb 19 19:39:49jj0hns0n: to put the onus on the imagery submitter, better the processing node is smart and can deal with whatever is thrown at itFeb 19 19:40:04jj0hns0n: if its proper orthoimagery, regardless of format, projection etcFeb 19 19:40:04smathermather: Oh good -- agreed.Feb 19 19:40:11smathermather: Yup.Feb 19 19:40:15Cristiano: well, that could be challengingFeb 19 19:40:20jj0hns0n: nah, not reallyFeb 19 19:40:41Cristiano: well, we should def suggest formats for uploadFeb 19 19:40:41wildintellect: of course we'd still make suggestions on easiest things to uploadFeb 19 19:40:42jj0hns0n: it becomes an iterative thing ... if someone throws something at it that doesnt work, you write a test that demonstrates the failure, fix it and ask them to re-uploadFeb 19 19:41:12Cristiano: and encourage development of plugins for other tools (e.g. QGIS, Pix4D, ODM, etc)Feb 19 19:41:26jj0hns0n: I think we should also be clear in the processing node that you could also just point it at a dropbox, s3 dir, ftp dir etcFeb 19 19:41:36wildintellect: Cristiano, sure that's the point of the apiFeb 19 19:41:39jj0hns0n: and the processing node would slurp that or if possible access it over FTPFeb 19 19:41:42jj0hns0n: http I mean :)Feb 19 19:42:06jj0hns0n: i.e. with vsicurlFeb 19 19:42:22Cristiano: right, or what if we to upload ready-tiles (eg in Dropbox)? What's the best workflow there? Compress for transfer and then deflate on server side?Feb 19 19:42:47jj0hns0n: thats on the other sideFeb 19 19:42:56Cristiano: assuming that the contributor already run gdal2tilesFeb 19 19:42:58jj0hns0n: its commonly called "clip and ship" stillFeb 19 19:43:09jj0hns0n: ah, thats different I guess, I would not encourage thatFeb 19 19:43:19jj0hns0n: better they give oam the raw imagery then some tiles of unknown originFeb 19 19:43:45jj0hns0n: it would be rare to have someone that had tiles and not the raw imagery (which would be smaller and easier to transport)Feb 19 19:43:56Cristiano: Well, If someone already has a QGIS plugin to prepare and tile imager, then they could just send it up to an OAM instance along with a metadata fileFeb 19 19:43:58jj0hns0n: Im thinking someone saying "here is my dropbox folder with a bunch of raw imagery in it"Feb 19 19:44:14jj0hns0n: but by definition the tiles will be much bigger than the raw imageryFeb 19 19:44:23wildintellect: I think the QGIS plugin would be an upload to OAM pluginFeb 19 19:44:24jj0hns0n: better they send raw imageryFeb 19 19:44:50Cristiano: well, yes, that's prob the most common situation. But would be nice if we can offload some of the processing on the client side :)Feb 19 19:44:53jj0hns0n: ah, so then in theory you could run the processing node _inside_ qgis and just uploadFeb 19 19:44:55jj0hns0n: that is betterFeb 19 19:45:05Cristiano: rightFeb 19 19:45:11wildintellect: sure that is an option, since anyone can run a processing nodeFeb 19 19:45:15jj0hns0n: but I would not be in favor of accepting a random zip of tiles that someone madeFeb 19 19:45:29jj0hns0n: well, one more +1 to do this in python then ... so it runs as a qgis plugin :)Feb 19 19:45:42smathermather: hehe.Feb 19 19:46:22wildintellect: if someone does use a processing node locally then there are only 2 steps after that - 1. push them to a tile node, 2. notify the Catalog once they are on the tile nodeFeb 19 19:46:24jj0hns0n: so, does the use case I mention make sense though? "here is a remote directory of raw imagery, please download it and make tiles from it"Feb 19 19:46:30jj0hns0n: correct wildintellect Feb 19 19:46:31wildintellect: yesFeb 19 19:46:46jj0hns0n: and again "push to tile node" could just be to S3Feb 19 19:46:51wildintellect: I expect plenty of people will just have a dir of images somewhereFeb 19 19:46:57jj0hns0n: and then you just let the catalog node know "they are here"Feb 19 19:46:58wildintellect: ie thats how we pull NAIPFeb 19 19:47:02jj0hns0n: rightFeb 19 19:47:09jj0hns0n: thats the dream to just point it at NAIP and say "go"Feb 19 19:47:50Cristiano: Or the L8 on S3 CHolmes just mentioned :)Feb 19 19:48:03jj0hns0n: yeah, but they are going to preprocess all thatFeb 19 19:48:20jj0hns0n: we should just be able to add that to the catalog somedayFeb 19 19:48:29smathermather: So does OAM ever optionally return raw imagery in cases where only tiles have been uploaded?Feb 19 19:48:42jj0hns0n: I would say that is a totally secondary concernFeb 19 19:49:03jj0hns0n: I think by and large it is not the goal of OAM to ever return 'raw' imageryFeb 19 19:49:13jj0hns0n: right?Feb 19 19:49:19Cristiano: It would be nice (in the future)Feb 19 19:49:43Cristiano: so that users can do stuff with the imagery other than looking at it or tracingFeb 19 19:50:02jj0hns0n: ok, but if you _really_ want to do that kind of thing, you should just look at OMAR and OSSIMFeb 19 19:50:18jj0hns0n: OAM should be primarily about tiles IMOFeb 19 19:50:27Cristiano: I guess so :)Feb 19 19:50:35jj0hns0n: omar/ossim or eoxserver Feb 19 19:50:56jj0hns0n: that is a very different use case right?Feb 19 19:51:25wildintellect: L8 would still be we just want the RGB, and to process that into tilesFeb 19 19:51:30jj0hns0n: i.e. having access to the raw imagery is important to an analyst or scientist, and not to the ordinary user who just wants tilesFeb 19 19:51:38Cristiano: Yes, but it would be nice if there's a list some metadata entry so that people can eventually go find the raw data if neededFeb 19 19:51:39smathermather: Can those tools ingest a set of tiles and do processing on them?Feb 19 19:51:57wildintellect: Cristiano, sure the Catalog should say where the data came fromFeb 19 19:52:06jj0hns0n: yeah, I would make sure that whenever possible the link to the raw imagery should be stored in the catalog, but it should not be the goal of OAM to actually serve that stuff upFeb 19 19:52:18jj0hns0n: yeah, both canFeb 19 19:52:58tomkralidis: catalogue is simply yellow pages w/ linksFeb 19 19:53:01jj0hns0n: omar/ossim in particular is a very robust automated image processing toolchain and catalogFeb 19 19:53:15Cristiano: ideally the "central" OAM should be a place where people can find, view and use tiles, but also just find/link free imagery that is available anywhere in the worldFeb 19 19:53:21jj0hns0n: right, tomkralidis what I mean is that OAM should link back to the raw imagery, but not be concerned with trying to serve it upFeb 19 19:53:33tomkralidis: exactlyFeb 19 19:53:33jj0hns0n: i.e. OAM is not a WCSFeb 19 19:53:49jj0hns0n: if you want a WCS, use eoxserver or omar or whateverFeb 19 19:54:18Cristiano: Right, so that brings us to the catalog and metadata. How much PyCSW can we just use straight off?Feb 19 19:54:27jj0hns0n: 100% of itFeb 19 19:54:28jj0hns0n: :)Feb 19 19:55:09Cristiano: I'm not 100% familiar with it, so how do we plug it in and how do we use its APIFeb 19 19:55:16Cristiano: ?Feb 19 19:57:07dodobas: pycws sohuld be just another 'endpoint'Feb 19 19:57:15tomkralidis: Cristiano: pycsw's a Python library that you deploy standalone CGI or mod_wsgi (latter is better), or embed into your own framework like Django, Flask, etc.Feb 19 19:57:20tomkralidis: like GeoNode didFeb 19 19:57:22jj0hns0n: yeah, it has to have a datastore tooFeb 19 19:57:33jj0hns0n: but then yeah, you just have to stick http in front of it somehowFeb 19 19:57:35dodobas: that will 'publish' OAM metadata...Feb 19 19:57:36jj0hns0n: various ways to do thatFeb 19 19:57:45tomkralidis: jj0hns0n: agree. Either u can use pycsw's datastore OR it can bind to an existing datastore.Feb 19 19:57:46dodobas: no need to integrate anythingFeb 19 19:57:49jj0hns0n: rightFeb 19 19:57:59jj0hns0n: in the smallest possible case it can just be a sqlite db right?Feb 19 19:58:10tomkralidis: jj0hns0n: yupFeb 19 19:58:10jj0hns0n: and uses sqlalchemy in that case? I cant rememberFeb 19 19:58:27tomkralidis: yes, sqlalchemy, lxml, OWSLib, geolinks are the deps.Feb 19 19:58:56jj0hns0n: so yeah, its pretty straightforward IMOFeb 19 19:59:05Cristiano: PyCSW handles metadata and other catalog harvesting right? How do you search all that and use it through a Web UI? Is it straight forward or there's some other middleware?Feb 19 19:59:05jj0hns0n: tomkralidis is eoxserver using pycsw now too?Feb 19 19:59:48Cristiano: I'm saying, can we just expose PyCSW API for all catalog functions?Feb 19 19:59:48tomkralidis: Cristiano: yes, harvesting and transactions via HTTP. OWSLib is typically the Python based CSW client used.Feb 19 20:00:00jj0hns0n: Cristiano the interface is a csw which can be queried, but you have to put some UI on it, its just an http endpoint that returns json or xmlFeb 19 20:00:27jj0hns0n: tomkralidis to do harvesting you have to spin a new process in a cron or some queue right?Feb 19 20:00:39tomkralidis: for webui you can put simple js together to do the opsFeb 19 20:01:05Cristiano: OK, cool. So there's no need of things like elasticsearch to handle searches right?Feb 19 20:01:15tomkralidis: jj0hns0n: to do harvesting, you harvest a resource, and set a time interval by which the harvester fetches/refrehsesFeb 19 20:01:26tomkralidis: Cristiano: IMHO no.Feb 19 20:01:50jj0hns0n: tomkralidis the question there is how well does that scale?Feb 19 20:02:10tomkralidis: ask data.gov :)Feb 19 20:02:10Cristiano: Right, that was my next question :)Feb 19 20:02:15jj0hns0n: tomkralidis how do you daemonize the harvester or is it in a cronFeb 19 20:02:27jj0hns0n: in data.gov the db is in postgres?Feb 19 20:02:41jj0hns0n: are you using postgres full text search or something similar?Feb 19 20:02:42tomkralidis: jj0hns0n: cronFeb 19 20:03:01jj0hns0n: tomkralidis ok, but that could also be done with something like django-celery or any other queue right?Feb 19 20:03:03tomkralidis: jj0hns0n: data.gov is PostgreSQL + PostGIS + PostgreSQL fts, yes.Feb 19 20:03:06tomkralidis: jj0hns0n: sureFeb 19 20:03:11jj0hns0n: ok, so yeah, fts then for sureFeb 19 20:03:25jj0hns0n: so yeah, I would say that obviates the need for elasticsearch et alFeb 19 20:03:31Cristiano: and is there a way to sync two or more PyCSW on different OAM isntances?Feb 19 20:03:46tomkralidis: Cristiano: harvesting Feb 19 20:04:00Cristiano: so, they harvest each other?Feb 19 20:04:08jj0hns0n: yeah, its got to be the same methodologyFeb 19 20:04:19Cristiano: I though harvesting was one wayFeb 19 20:04:32jj0hns0n: tomkralidis how is it now handling a distributed search across several catalogs that may not ever be in sync?Feb 19 20:05:34tomkralidis: distributed search can be sync or async, it's a CSW thingFeb 19 20:06:18jj0hns0n: yeah, I guess the real question in my mind is can we do _everything_ within the formal csw protocol or is there something else necessary to make it easier for mere mortals to understandFeb 19 20:06:26jj0hns0n: in geonode at least, we have a separate more simple APIFeb 19 20:06:36jj0hns0n: using tastypieFeb 19 20:07:03tomkralidis: IMHO it can, but people have disagreed with me on that :)Feb 19 20:08:01jj0hns0n: this is much easier to work with than csw :) http://demo.geonode.org/api/layers/?limit=1&offset=0Feb 19 20:08:14Cristiano: And the OAM metadata schema will also be somehow simpler than OGC EOFeb 19 20:08:16tomkralidis: jj0hns0n: FYI pycsw supports OpenSearch. Which is dead easy.Feb 19 20:08:37jj0hns0n: yeah, I guess it boils down to who is going to consume the APIFeb 19 20:09:00tomkralidis: IMHO you want a cross cutting offering. for the specialists/GIS crowd CSW, for mass market OpenSearch.Feb 19 20:09:39jj0hns0n: yepFeb 19 20:09:48jj0hns0n: in geonodes case we use this other api to drive the UI in a lot of placesFeb 19 20:09:57jj0hns0n: but it all comes from the same data sourceFeb 19 20:10:41jj0hns0n: thats the real key is binding whatever apis you are going to provide to the same datasource and not keep multiple copies of the same catalog data on the same node/instance whateverFeb 19 20:10:46tomkralidis: true. Single data source is important. And so is single search design pattern. You don't want someone to use CSW with diff search results than, say UIFeb 19 20:10:59jj0hns0n: I think we have found that not to be a real problem so farFeb 19 20:11:00Cristiano: The set of metadata to index will be very small compared to other catalogs with full text searches and complex spatial geometriesFeb 19 20:11:41jj0hns0n: yeah, should beFeb 19 20:11:52tomkralidis: I think pycsw + sqlite3 covers the light use caseFeb 19 20:12:09Cristiano: the only spatial data in the database will be the dataset footprint, either BBOX or polygon coverageFeb 19 20:12:42tomkralidis: so the other part here is the metadata modelFeb 19 20:12:59jj0hns0n: yeah, but should we not just follow ISO completely?Feb 19 20:13:31nhv: maybe BBOX, and CRSFeb 19 20:13:37Cristiano: I would at least do a subset. And then extend with specific OAM namespacesFeb 19 20:14:18Cristiano: Here's the initial draft: https://github.com/hotosm/OpenAerialMap/wiki/MetadataFeb 19 20:14:42jj0hns0n: you should try to shove everything into an existing formal standard as much as possibleFeb 19 20:15:07tomkralidis: Cristiano: the OAM namespaces: need to be aware that extending the metadata model with 'local' elements is fine, but then that affect queryables by standards based things like CSW.Feb 19 20:15:21tomkralidis: agree w/ jj0hns0n on leveraging an existing standardFeb 19 20:15:31jj0hns0n: ebRIM would be pushing things too far IMOFeb 19 20:15:45tomkralidis: that's like a sledgehammer trying to crack a nutFeb 19 20:15:48Cristiano: Yes, that was more an abstract level list. It would be nice to fit it to a standard :)Feb 19 20:15:58tomkralidis: Dublin Core is a good start.Feb 19 20:16:13jj0hns0n: yeah, but just going ISO is the best right?Feb 19 20:16:19jj0hns0n: I mean thats the tact we take in geonode for usreFeb 19 20:16:21jj0hns0n: sureFeb 19 20:17:05tomkralidis: jj0hns0n: vanilla ISO is best/safe, albeit a bit more complex than DC.Feb 19 20:17:24tomkralidis: like we do in GeoNode yesFeb 19 20:17:29jj0hns0n: yeah, but not sure you can cram everything we need in DC right?Feb 19 20:18:15jj0hns0n: but -0 on doing anything that extends an existing profile unless there is a very very good reason for doing soFeb 19 20:18:40tomkralidis: agree. vanilla ISO like we do in GeoNode would yield better results.Feb 19 20:19:03tomkralidis: -1 on extending, push into ISO 19115/19139 properFeb 19 20:19:14jj0hns0n: yep, I would not be -1 but certainly -0Feb 19 20:19:21tomkralidis: based on https://github.com/hotosm/OpenAerialMap/wiki/Metadata, I don't see any gaps in vanilla ISOFeb 19 20:19:27jj0hns0n: I didnt eitherFeb 19 20:20:12jj0hns0n: then the real question in my mind is do you also stick another API or do everything through CSW and OpenSearchFeb 19 20:20:29jj0hns0n: but I think that can be thought through when building a UI and not beforeFeb 19 20:20:31tomkralidis: how important are facets here?Feb 19 20:20:39jj0hns0n: could potentially be very importantFeb 19 20:20:41tomkralidis: jj0hns0n: agreed, true.Feb 19 20:21:48Cristiano: So, how to include e.g. datasource (raw files, WMS, TMS, MBTiles) would be defined when building the UI?Feb 19 20:22:11jj0hns0n: not sure I understand that questionFeb 19 20:22:49Cristiano: or is that something that you can already define in vanilla ISO to start?Feb 19 20:23:19jj0hns0n: you mean how would you reference those kinds of attributes in vanilla iso?Feb 19 20:23:24jj0hns0n: I think thats totally doableFeb 19 20:23:26Cristiano: I'm just wondering if we can define the complete metadata schema before implementing the UI and the other componentsFeb 19 20:23:35Cristiano: OKFeb 19 20:23:50jj0hns0n: tomkralidis may get irritated at me for saying this ;) but some people are now shoving a json dict into something like a supplemental_information fieldFeb 19 20:23:59jj0hns0n: and then you can do what you like to 'extend' if you need something for the UIFeb 19 20:24:04jj0hns0n: without breaking ISOFeb 19 20:26:14nhv: mumbles something about if we also consider video STANAG 4609 maybe worth investigating
Feb 19 20:25:29jj0hns0n: nhv wouldnt we just go the ossim/omar route if we wanted to do that?Feb 19 20:25:30Cristiano: That's probably OAM 2 :)Feb 19 20:25:43nhv: that is the OMAR route :-)Feb 19 20:25:51nhv: or part of itFeb 19 20:25:52Cristiano: live earth video feed?Feb 19 20:26:14nhv: yesFeb 19 20:26:14jj0hns0n: yeah, or doing something with all the go pro video from every DJI user out there :)Feb 19 20:27:03jj0hns0n: that would be something to get STANAG 4609 from a gopro video and a pixhawk log :)Feb 19 20:27:03Cristiano: All right, lots of good ideas, thank you guys! We should wrap upFeb 19 20:27:34jj0hns0n: I gotta get going too, thanks for leading crisFeb 19 20:27:37tomkralidis: jj0hns0n: json in supplemental_information yikes! But yes doableFeb 19 20:27:48Cristiano: Please send your comments and ideas to the list or open it in githubFeb 19 20:27:49jj0hns0n: yeah, better to do that than break ISO :)Feb 19 20:28:24Cristiano: Thank you all and see you next week!Feb 19 20:28:40BlakeGirardot: Thank you all !Feb 19 20:28:44smathermather: thanks!