OL3 requirements

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

OL3 requirements

nuest
Hi all!

Another follow-up on the user meeting from last week:

Alexey has pointed out in his FOSSGIS presentation [1] (German only) the
current OL3 implementation dealing with XML, which is all manually
written statements. JSONIX would of course improve this, and even more
so would a wrapper around it (i.e. ows.js) to be used ob OL3.

Are OL3 comitters on this list who could formulate requirements for
ows.js based on the OL3 perspective? Or should we contact OL3 developers
directly? And what would our suggestion be?

I am not an OL3 user at all, but I think it there is some great guidance
for where to head with ows.js if we could build it in a way to support
(or be compatible with) one of the most prominent mapping libraries.


Best regards,
Daniel

[1]
https://www.youtube.com/watch?v=6Wtc08_uNeI&index=61&list=PLTli5-lbeoiYopkK5ixkgt1Uzh_0v6Z6T

--
Daniel Nüst
52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: [hidden email]
Fon: +49-(0)-251–396371-36
Fax: +49-(0)-251–396371-11

http://52north.org/
Twitter: @FiveTwoN

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
_______________________________________________
owsjs mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/owsjs
Reply | Threaded
Open this post in threaded view
|

Re: OL3 requirements

Bart van den Eijnden (OSGIS)-2
Hi Daniel,

I think several ol3 developers are on this list. One of the areas that has come up is how to integrate with Closure Compiler.

I think we would need several adapters (but the question is where would these live), e.g. to bridge the gap between Web Map Context and actually feeding layers into an ol.Map.

We could also try to see what’s involved in replacing the existing WMSCapabilities parser of ol3 with a JSONIX implementation.

Best regards,
Bart

> On 16 Mar 2015, at 11:19, Daniel Nüst <[hidden email]> wrote:
>
> Hi all!
>
> Another follow-up on the user meeting from last week:
>
> Alexey has pointed out in his FOSSGIS presentation [1] (German only) the current OL3 implementation dealing with XML, which is all manually written statements. JSONIX would of course improve this, and even more so would a wrapper around it (i.e. ows.js) to be used ob OL3.
>
> Are OL3 comitters on this list who could formulate requirements for ows.js based on the OL3 perspective? Or should we contact OL3 developers directly? And what would our suggestion be?
>
> I am not an OL3 user at all, but I think it there is some great guidance for where to head with ows.js if we could build it in a way to support (or be compatible with) one of the most prominent mapping libraries.
>
>
> Best regards,
> Daniel
>
> [1] https://www.youtube.com/watch?v=6Wtc08_uNeI&index=61&list=PLTli5-lbeoiYopkK5ixkgt1Uzh_0v6Z6T
>
> --
> Daniel Nüst
> 52°North Initiative for Geospatial Open Source Software GmbH
> Martin-Luther-King-Weg 24
> 48155 Münster, Germany
> E-Mail: [hidden email]
> Fon: +49-(0)-251–396371-36
> Fax: +49-(0)-251–396371-11
>
> http://52north.org/
> Twitter: @FiveTwoN
>
> General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
> Local Court Muenster HRB 10849
> _______________________________________________
> owsjs mailing list
> [hidden email]
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/owsjs

_______________________________________________
owsjs mailing list
[hidden email]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/owsjs