Hi, just humble suggestion: you can make this to OSGeo Community standard, like TMS [1] was at it's time and get more publicity and possible more collaborators to the project. Promote and colaborate via standards mailing list [2]
btw: what is the mimetype, we shall stick to? (OGC WebProcessingService and others need one single clear mimeType) Cheers J [1] https://wiki.osgeo.org/wiki/Tile_Map_Service_Specification [2] https://lists.osgeo.org/mailman/listinfo/standards út 30. 8. 2016 v 11:09 odesílatel Jon Blower <j.d.blo...@reading.ac.uk> napsal: > Dear all, > > > > (Second attempt at sending this, I wasn’t subscribed before!) > > > > I’m the leader of the project under which CoverageJSON is being developed > [1]. My colleague Maik Riechert is the main developer of this. Thanks very > much to Bruce for advertising to this list! I’ll pick up on a few of the > points in this thread: > > > > 1. Regarding adoption, it’s early days yet, but I’m aware of a few > applications in development (including our own projects of course, but also > some external folk). We’re building in library support for a few languages > (e.g. Javascript, Python) and some tools (e.g. Leaflet and NASA’s Web World > Wind). > > 2. I think CovJSON can work nicely with O&M (the coverage can be > the result of the observation). O&M could provide the “hooks” on which > other metadata (e.g. provenance) could be hung. > > 3. Regarding compression: yes, this is going to be important. JSON > gzips very well on the wire, which helps a lot with transfer speed and our > tests indicate that it’s typically not very much worse than a compressed > binary format. We’ve worked successfully with rasters of millions of pixels > in size. > > 4. We’d be very happy to help people who want to implement support > for CovJSON in software (e.g. istSOS). Maybe our libraries will be of some > use here. > > > > Any feedback on the spec or tools (positive or negative) is very welcome > and timely, as we are moving towards a stable 1.0 release. > > > > Best wishes, Jon > > > > [1] http://www.melodiesproject.eu > > > > -- > > Dr Jon Blower, > > MELODIES project coordinator, > > University of Reading > > j.d.blo...@reading.ac.uk > > > > *From: *Massimiliano Cannata <massimiliano.cann...@supsi.ch> > *Date: *Thursday, 18 August 2016 09:47 > *To: *Bruce Bannerman <bruce.bannerman.os...@gmail.com> > *Cc: *Jachym Cepicky <jachym.cepi...@gmail.com>, OSGeo Discussions < > discuss@lists.osgeo.org>, Jon Blower <sgs02...@reading.ac.uk> > *Subject: *Re: [OSGeo-Discuss] CoverageJSON > > > > Dear All, > > the coverage in O&M is addressed also at EU level within the SOS but in > XML. > > > > I may be interested in exploring this format and add this capability to > istSOS in the next future... > > > > Maxi > > > > 2016-08-17 22:58 GMT+02:00 Bruce Bannerman < > bruce.bannerman.os...@gmail.com>: > > Thanks Jachym. > > > > I can also see the potential of this format. > > > > I like the potential for tying in the Observations and Measurements > Observed Property with associated community agreed definitions to the > coverage. This has been a missing piece of the puzzle for some time. > > > > I understand that Jon and his team would welcome collaboration to further > test and develop the format. > > > > I expect that Jon will respond when he gets back off his holiday. > > > > Bruce > > > On 17 Aug 2016, at 19:03, Jachym Cepicky <jachym.cepi...@gmail.com> wrote: > > Hi Bruce and Jon, > > > > I went through the spec, and I like it in general (not that it would be so > important) > > > > JSON usage is certainly still growing, so is size of the data. Are you > guys using the CoverageJSON in some application already? I like the > metadata verbosity, and overall readiness for international environment. > > > > Have you been thinking about data compression too? For raster data, this > could be key issue IMHO. > > > > good luck > > > > Jachym > > > > čt 11. 8. 2016 v 0:47 odesílatel Bruce Bannerman < > bruce.bannerman.os...@gmail.com> napsal: > > Hi, > > Are any projects doing any work with the emerging data format, > CoverageJSON? > > See: > > - https://covjson.org/ > > - https://github.com/covjson/specification/blob/master/spec.md > > > I understand that this is still a work in progress, but is in a fairly > stable state at the moment. > > If anyone has looked at the format in detail, what are your thoughts on > its viability for: > > - data exchange; and > > - to underpin spatial and image analysis? > > Bruce > > _______________________________________________ > Discuss mailing list > Discuss@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/discuss > > > _______________________________________________ > Discuss mailing list > Discuss@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/discuss > > > > > > -- > > *Massimiliano Cannata* > > Professore SUPSI in ingegneria Geomatica > > Responsabile settore Geomatica > > > > Istituto scienze della Terra > > Dipartimento ambiente costruzione e design > > Scuola universitaria professionale della Svizzera italiana > > Campus Trevano, CH - 6952 Canobbio > > Tel. +41 (0)58 666 62 14 > > Fax +41 (0)58 666 62 09 > > massimiliano.cann...@supsi.ch > > *www.supsi.ch/ist <http://www.supsi.ch/ist>* >
_______________________________________________ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss
