[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgis-users
Subject:    Re: [postgis-users] Wrong format: PostGIS misses a " " in it's WKT output?
From:       Rémi_c <remi.cura () gmail ! com>
Date:       2021-04-26 14:54:15
Message-ID: CAJvUf_udCYCtC3bn9ip_n60cyz3KpYPQgCKyhr6vFR7G8c=1Bg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Thanks @Paul Ramsey <pramsey@cleverelephant.ca> !
Remi

Le ven. 23 avr. 2021 Ã  16:24, Paul Ramsey <pramsey@cleverelephant.ca> a
écrit :

> Since hopefully most parsers will consume either version (and kind of have
> to) just go with emitting whatever makes you feel good, no?
>
> > On Apr 23, 2021, at 1:21 PM, Rémi c <remi.cura@gmail.com> wrote:
> >
> > Hey Paul, great to hear from you!
> > Yeah I agree this is a bit confusing :-/
> >
> > The standards are here, page 54.
> > The interesting line is ```<polygon tagged text> ::= polygon <polygon
> text>```
> > Where `<polygon text>` is then refined into EMPTY or a list of
> linestrings between parenthesis.
> >
> > It looks like the python lib Shapely enforces the space.
> > Not sure what to do here, I'd like to follow the standard,
> > but the PostGIS is kind of the standard way to follow the standard.
> >
> > Remi
> >
> >
> >
> > Le ven. 23 avr. 2021 Ã  15:50, Paul Ramsey <pramsey@cleverelephant.ca> a
> écrit :
> > Reference please? In general the OGC standards have a lot of room for
> interpretation in them.
> > Certainly we've done it this way for 20 years, so :)
> > P.
> >
> > > On Apr 23, 2021, at 12:44 PM, Rémi c <remi.cura@gmail.com> wrote:
> > >
> > > Hey dear list,
> > > I'm looking at ST_asWKT() function.
> > > I noticed an issue here:
> > > PostGIS outputs something like:
> > > `POLYGON((1 2, 2 3, 3 4, 1 2))`
> > > Yet the WKT standard requires a space after `POLYGON`, like
> > > `POLYGON ((1 2, 2 3, 3 4, 1 2))`
> > >
> > > Am I missing something here?
> > > Thanks folks.
> > > Remi
> > > _______________________________________________
> > > postgis-users mailing list
> > > postgis-users@lists.osgeo.org
> > > https://lists.osgeo.org/mailman/listinfo/postgis-users
> >
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/postgis-users
> > _______________________________________________
> > postgis-users mailing list
> > postgis-users@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/postgis-users
>
> _______________________________________________
> postgis-users mailing list
> postgis-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
>

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_default" \
style="font-family:monospace,monospace">Thanks <a class="gmail_plusreply" \
id="plusReplyChip-3" href="mailto:pramsey@cleverelephant.ca" tabindex="-1">@Paul \
Ramsey</a> !<br></div><div class="gmail_default" \
style="font-family:monospace,monospace">Remi<br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">Le  ven. 23 avr. 2021 Ã   \
16:24, Paul Ramsey &lt;<a \
href="mailto:pramsey@cleverelephant.ca">pramsey@cleverelephant.ca</a>&gt; a écrit  \
:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Since hopefully most \
parsers will consume either version (and kind of have to) just go with emitting \
whatever makes you feel good, no?<br> <br>
&gt; On Apr 23, 2021, at 1:21 PM, Rémi c &lt;<a href="mailto:remi.cura@gmail.com" \
target="_blank">remi.cura@gmail.com</a>&gt; wrote:<br> &gt; <br>
&gt; Hey Paul, great to hear from you!<br>
&gt; Yeah I agree this is a bit confusing :-/<br>
&gt; <br>
&gt; The standards are here, page 54.<br>
&gt; The interesting line is ```&lt;polygon tagged text&gt; ::= polygon &lt;polygon \
text&gt;```<br> &gt; Where `&lt;polygon text&gt;` is then refined into EMPTY or a \
list of linestrings between parenthesis.<br> &gt; <br>
&gt; It looks like the python lib Shapely enforces the space.<br>
&gt; Not sure what to do here, I&#39;d like to follow the standard, <br>
&gt; but the PostGIS is kind of the standard way to follow the standard.<br>
&gt; <br>
&gt; Remi<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; Le ven. 23 avr. 2021 Ã  15:50, Paul Ramsey &lt;<a \
href="mailto:pramsey@cleverelephant.ca" \
target="_blank">pramsey@cleverelephant.ca</a>&gt; a écrit :<br> &gt; Reference \
please? In general the OGC standards have a lot of room for interpretation in \
them.<br> &gt; Certainly we&#39;ve done it this way for 20 years, so :)<br>
&gt; P.<br>
&gt; <br>
&gt; &gt; On Apr 23, 2021, at 12:44 PM, Rémi c &lt;<a \
href="mailto:remi.cura@gmail.com" target="_blank">remi.cura@gmail.com</a>&gt; \
wrote:<br> &gt; &gt; <br>
&gt; &gt; Hey dear list,<br>
&gt; &gt; I&#39;m looking at ST_asWKT() function.<br>
&gt; &gt; I noticed an issue here:<br>
&gt; &gt; PostGIS outputs something like:<br>
&gt; &gt; `POLYGON((1 2, 2 3, 3 4, 1 2))`<br>
&gt; &gt; Yet the WKT standard requires a space after `POLYGON`, like<br>
&gt; &gt; `POLYGON ((1 2, 2 3, 3 4, 1 2))`<br>
&gt; &gt; <br>
&gt; &gt; Am I missing something here?<br>
&gt; &gt; Thanks folks.<br>
&gt; &gt; Remi<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; postgis-users mailing list<br>
&gt; &gt; <a href="mailto:postgis-users@lists.osgeo.org" \
target="_blank">postgis-users@lists.osgeo.org</a><br> &gt; &gt; <a \
href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" \
target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br> &gt; \
<br> &gt; _______________________________________________<br>
&gt; postgis-users mailing list<br>
&gt; <a href="mailto:postgis-users@lists.osgeo.org" \
target="_blank">postgis-users@lists.osgeo.org</a><br> &gt; <a \
href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" \
target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br> &gt; \
_______________________________________________<br> &gt; postgis-users mailing \
list<br> &gt; <a href="mailto:postgis-users@lists.osgeo.org" \
target="_blank">postgis-users@lists.osgeo.org</a><br> &gt; <a \
href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" \
target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br> <br>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" \
target="_blank">postgis-users@lists.osgeo.org</a><br> <a \
href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" \
target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-users</a><br> \
</blockquote></div>



_______________________________________________
postgis-users mailing list
postgis-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic