Good, three is already a group!
The strategy will be to define the data model and the templates while in
parallel requiring formal endorsement from OSGeo. A project like this can only
succeed if backed by the foundation.
Please send me your GitHub handles. I would also ask you to link to your
OK. I want to join the new github group, too.
Best regards,
Manfred
-Original Message-
From: "Julien Moquet"
Sent: Tuesday, August 30, 2016 1:04pm
To: "Luís de Sousa"
Cc: discuss@lists.osgeo.org, manf...@egger-gis.at
Subject: Re: [OSGeo-Discuss] Detect and define the coordinate system
Set me into !
Julien.
Le 30 août 2016 11:34, "Luís de Sousa" a
écrit :
> Hi Julien et al.,
>
> My experience with Wikis is mostly negative, however, the GitHub
> "database" could work very well. The project could be hooked up to
> ReadTheDocs and folk would just commit their .rst and .md files
Hi All,
As Jon pointed out, this work is being discussed in the joint OGC/W3C Spatial
Data on the Web Working Group. Also, Jon will be presenting the work formally
to the OGC membership at our Opening Plenary next month. I encourage interested
parties to attend in person (Orlando, FL USA) or re
Hi,
should there not be a decision by OSGeo to promote a database before we start
to collect data in github?
Best regards,
Manfred
-Original Message-
From: "Luís de Sousa"
Sent: Tuesday, August 30, 2016 5:34am
To: "Julien Moquet"
Cc: "manf...@egger-gis.at" , discuss@lists.osgeo.org
Hi Jachym,
That’s good to know, thanks. We’ve done all our development on GitHub so far and communicated via issues and wikis there. It could be a good idea to move discussions somewhere
like OSGeo in future, but for now I’d like to encourage anyone who is interested to join us on Git
Hi,
afaik, we as OSGeo, do not have formal procedure regarding standards, we
offer some infrastructure (wiki, mailing list, maybe gitlab) and you can
just "call for action" - you can then collaborate like any other project.
It is very simple and gives you big freedom. That does not exclude you fro
Hi Jon,
In the longer term, I think that you will have more take-up if this is a joint
OGC/ W3C standard.
While you go through this process there is the opportunity for refining the
format through practical implementations.
Bruce
> On 30 Aug 2016, at 19:29, Jon Blower wrote:
>
> Dear Jachym
Hi Julien et al.,
My experience with Wikis is mostly negative, however, the GitHub "database"
could work very well. The project could be hooked up to ReadTheDocs and folk
would just commit their .rst and .md files. Preparatory work would go around
defining the templates to submit projections, d
This is good to see Jon.
@All how can we make this happen within OSGeo?
Bruce
> On 30 Aug 2016, at 19:09, Jon Blower wrote:
>
> 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].
Dear Jachym,
We define the MIME type as “application/prs.coverage+json”. See [1] for more information about this and about our concept of “profiles”.
Currently CovJSON is being discussed in the context of the joint OGC/W3C “Spatial Data on the Web” working group, although there is n
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 WebProcessingSer
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
Dear Luis,
At this moment, the best way to go on is the following:
Depending on the type of proposal.
For marketing support, you should address your proposal to the marketing
committee. Marc Vloemans (in cc) is the contact person.
For other proposals, you should address the board. The idea is to
14 matches
Mail list logo
