Morten W. Hansen

Sounds like a plan! On Tue, Apr 30, 2019 at 11:06 AM Artem Moiseev wrote: > @mortenwh @akorosov > I would suggest making it a property. Then > we could...

@BabikerM - can you implement this? Remember tests...

Why did you delete the pull request? It hasn't been merged, and there are some things to do still...

Ok - maybe you accidentally deleted your branch? Then you'll have to restart this... It should anyway not take toomuch time

There is separate keyword "model" for platforms, as far as I remember. Then the instrument should be the model name, I think... Check with NCEP, for example by opening an...

The best solution is perhaps to add it as list, as you suggest. This should work fine for Nansat, but I am not sure how we should solve it for...

`source` is the table name in geospaas... Anyway, platform and instrument come in pairs and it may be complicated to have more than one pair in the metadata without major...

I will introduce a hack for OSTIA data in the nansat mapper `mapper_opendap_ostia`: `mapper_opendap_ostia` sets platform to Aqua and instrument to AMSR-E. The issue with multiple sources will then be...

I suggest to solve this by setting platforms and instruments in a list of lists: ``` pi = [ [pti.get_gcmd_platform('noaa-18'), pti.get_gcmd_instrument('avhrr-3')], [pti.get_gcmd_platform('noaa-19'), pti.get_gcmd_instrument('avhrr')] ] self.dataset.SetMetadataItem('platform/instrument', json.dumps(pi)) ``` Django-Geo-SPaaS could be...

- [x] Update opendap_ostia mapper - [x] Update globcurrent mapper - [ ] Update other mappers (?). I suggest that we do this gradually with emerging needs...