{"push_id":2172676743,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e97076c4dfef4cf2a6111563ac90ebb7c1674b70","before":"685562416ec6d22b9b3927e02ca0ddacf84ca646","commits":[{"sha":"e97076c4dfef4cf2a6111563ac90ebb7c1674b70","author":{"name":"Max-Julian Pogner","email":"2ee33beb87d8241708537d76f63d7ba0215b5c42@pogner.at"},"message":"make WKT.class.php more strict\n\nHi,\n\ntoday i had to debug a surprising problem: WKT linestrings produced by geoPHP where not recognised by the remote server. Further investigation revealed, that their wkt parsing library does not expect a space before left parentheses of LINESTRING.\n\nCrosschecking with http://www.opengeospatial.org/standards/sfa reveals: within the OpenGIS standard examples are written with space before left parenthesis. However, the BNF does not allow for spaces (see Section 7.2.2 the productions `linestring tagged text` and `linestring text` do not make any mention of `<space>`). I was also unable to find any general remarks regarding whitespaces (for example: there is the normative text outside BNF that left and right delimiters need to be balanced).\n\nAll this, of course, is not a problem with geoPHP but with the remote server.\nHowever, I was thinking about: if the BNF in the standard mandates no space before left parenthesis (that is: `LINESTRING(` opposed to `LINESTRING (`), then, in accordance with Jon Postel's \"strict in what you send\"-principal, geoPHP should continue to parse many input strings but only produce output strings without space.\n\nPlease let me know what you think,\n\nregards,\nMax","distinct":true,"url":"https://api.github.com/repos/qyanu-pull-requests/geoPHP/commits/e97076c4dfef4cf2a6111563ac90ebb7c1674b70"}]}
{"actor":{"display_login":"qyanu"}}