Hi Jukka,
is it a problem if, after typing both "hobu" and "sgillies" do not popup
in the suggestion list? I've only found Tim Schaub there. I'm not sure
whether they will actually be mentioned/informed then... We might wait
forever for an answer... while (true);
Carsten
Am 07.10.2022 um 10:27 schrieb Rahkonen Jukka:
Hi,
For my mind it is usually better to ask beforehand that to correct
possible misunderstandings afterwards. The GeoJSON authors are not my
family friends but I have seen that they are responsive in the web.
You can for example tag “hobu” and “sgillies” in GitHub and see what
happens.
-Jukka Rahkonen-
*Lähettäjä:* Andrea Aime <andrea.a...@geosolutionsgroup.com>
*Lähetetty:* perjantai 7. lokakuuta 2022 10.57
*Vastaanottaja:* Carsten Klein <c.kl...@datagis.com>
*Kopio:* Rahkonen Jukka <jukka.rahko...@maanmittauslaitos.fi>;
geoserver-devel@lists.sourceforge.net; bj...@wololo.org
*Aihe:* Re: [Geoserver-devel] Enhancement: WFS Simple Feature Response
in new more compact JSON/JSONP format
On Fri, Oct 7, 2022 at 8:45 AM Carsten Klein <c.kl...@datagis.com> wrote:
GeoServer's JSON is GeoJSON as
its (backwards-) compatible with GeoJSON (the addition of the
inofficial
"crs" object does not prevent GeoJSON clients form reading the
format).
The same is true for OGC's JSON-FG.
GeoJSON is an extensible format, you can add as much as you want, as
long as the bits
mandated by the specification are there. What GeoServer returns is
actually "classic GeoJSON",
the earlier public specification before the RFC one, which recognized
the need for CRS support.
The new Slim format is NOT compatible with GeoJSON as GeoJSON clients
will fail reading it (expecting an object and not an array for the
"properties" key).
Which makes calling it "GeoJSON" is confusing... at the same time GeoJSON
picked the most obvious name, it's difficult to convey that a format
is spatial in nature
and doge that "Geo". "Slim Spatial JSON" does not quite roll off the
tongue,
Brokjson does roll, but unless there is some language specific inner
joke that I don't understand,
it does not recall spatial/geo. Maybe just "SpatialJSON"? Of course it
would not convey
that it's slim. Maybe "TinyGeoJSON"? As a parallel TWKB, Tiny Well
Known Binary
<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTWKB%2FSpecification%2Fblob%2Fmaster%2Ftwkb.md&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C6fb99adc25b14605ca0108daa8399572%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C638007262516807900%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7JDR5g7mQ7%2B4tYjWTm3VZY80lMYbomwP1G9iSmcE8%2F0%3D&reserved=0>,
is also not WKB.
Putting everything in a word may carry out better that it's not
GeoJSON+ but something similar,
yet not quite the original. Just thinking out loud.
As a Porsche *Cabrio* is still a Porsche, I'm sure that a name
including
the term GeoJSON will still be the best option. However, this assumes
that the GeoJSON inventors actually specify that new variant (or
support
it, at least). Since we have several new formats like BrokJSON and
JSON-FG *without* the term "Geo" in it, I guess that the GeoJSON guys
are not really open to such a new variant. Jukka, you seem to know
them
quite a bit, what do you think about it? Is is worth asking them?
Jukka will follow up, but yeah, I would ask them.
Andrea recommended to also maintain a publicly visible site with some
specifications for the new format like https://www.brokjson.dev/
<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.brokjson.dev%2F&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C6fb99adc25b14605ca0108daa8399572%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C638007262516807900%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EGHu1RoT%2Bt5TzXdja6m6x9eDrjMC0x8BTLxhoHFZ9O0%3D&reserved=0>.
That
would be cool, of course. However, I'm first of all running a
software
company and have a couple of B2B projects using such huge GetFeature
responses. I'm just looking for a *simple* solution which is
available
in the next days (not weeks or months). You know what I mean?
Painfully aware of the situation, yes. A community module does not
require a big
specification, and there is no need to wait for a public site either.
Maybe just place
a big bad warning message in a documentation file for the module, stating
"it's not really GeoJSON, format name might change" and be open to amend
as the discussion unfolds.
One last thing: currently the new module "falls back" to GeoServer's
normal response for complex features. With a really new format
(whether
it's BrokJSON or something new), the format should just
reject/fail if
someone requests complex features in that new format, right?
I would suggest throwing an exception, yes.
Cheers
Andrea
==
GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services-us
<https://eur06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Fgs-services-us&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C6fb99adc25b14605ca0108daa8399572%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C638007262516807900%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ejl9e9ul1a6GLyT9t8zmA2WPFQrtXud7gibeZTXN%2BP8%3D&reserved=0>for
more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
https://www.geosolutionsgroup.com/
<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.geosolutionsgroup.com%2F&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C6fb99adc25b14605ca0108daa8399572%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C638007262516807900%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0y8CG8k37NCxOGAti2p5F%2FQqSwrTcVCRS4qSEWBMPBc%3D&reserved=0>
http://twitter.com/geosolutions_it
<https://eur06.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fgeosolutions_it&data=05%7C01%7Cjukka.rahkonen%40maanmittauslaitos.fi%7C6fb99adc25b14605ca0108daa8399572%7Cc4f8a63255804a1c92371d5a571b71fa%7C0%7C0%7C638007262516807900%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xGRWnfajHJV1fv1c9gil60T4xxb0slHqgSMWsuSb3AQ%3D&reserved=0>
-------------------------------------------------------
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
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
