[Geoserver-devel] OGC API, two new conundrums: uber services vs separate services, and where to put tile services (warning, long read)

GeoServer GeoServer Developer
1

Hi all,
I’m writing to discuss a couple of issues in moving forward with the OGC services.

Uber services?

···

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

2

I think split makes much more sense at this stage – smaller, easier to understand, easier to test.

What I saw of the hackathon was pretty limited, but clearly there is a long way to go on everything except features. If we wait for the commons to settle, we could be chasing a moving target for a long time.

If it emerges that there really is a lot to gain by merging into uber configuration, then we can look at it when we have those done.

No position on tile services, but one thing I noted was the ability to use it TMS-style. Possibly the implementation could be split (so the top part – advertising - gets done by gs, and individual tile sets get delivered by gwc). That’ll require some particularly deft OpenAPI though.

Brad

3

I think split makes much more sense at this stage – smaller, easier to understand, easier to test.

What I saw of the hackathon was pretty limited, but clearly there is a long way to go on everything except features. If we wait for the commons to settle, we could be chasing a moving target for a long time.

Indeed, between the WFS 3 Hackaton and the upcoming Feature spec being finalized, we had to wait a year. And it’s just core, does not handling “complex” filtering (e.g., OGC Filter, CQL), transactions,
random paging, reprojection and so on. Common is the minimum common denominator of all specs, so it will have to wait for the slowest spec to be finalized and provide feedback in order to be useful.
A year seems optimistic indeed, but I might be wrong (well, I hope I’m wrong).

If it emerges that there really is a lot to gain by merging into uber configuration, then we can look at it when we have those done.

No position on tile services, but one thing I noted was the ability to use it TMS-style. Possibly the implementation could be split (so the top part – advertising - gets done by gs, and individual tile sets get delivered by gwc). That’ll require some particularly deft OpenAPI though.

Oh… did not thing about it. Yes, the OpenAPI would be somewhat bizzarre, a GetFeatureInfo equivalent is not going to be the same, the i and j parameters will end up in the query string.
And wait, does TMS has featureinfo to start with? Maybe not: https://wiki.osgeo.org/wiki/Tile_Map_Service_Specification

Cheers
Andrea

···

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

4

Hi Andrea,

Didn’t consider the featureinfo part – have been a bit too much in the imagery lately.

Brad