Timeline for Difference between notations of WKT format: 'POINT()' and 'Point ()'
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 26, 2021 at 12:06 | vote | accept | Taras♦ | ||
| Nov 11, 2021 at 12:09 | comment | added | Vince |
Okay, so the original standard and examples were all uppercase and the current specification, copyrighted 10+ years after I wrote my first case-insensitive parser, is now explicitly case-insensitive. So the real difference between POINT and Point is when the export function that generated the WKT was written.
|
|
| Nov 11, 2021 at 9:44 | comment | added | user30184 |
@vince, I wrote only a link to the original OGC-SF standard to my answer but I was reading the current version of the standard myself. I added now also this link portal.ogc.org/files/?artifact_id=25355. Table 6 in the current version has examples like MultiLineString ((10 10, 20 20), (15 15, 30 15)).
|
|
| Nov 11, 2021 at 9:39 | history | edited | user30184 | CC BY-SA 4.0 |
added 125 characters in body
|
| Nov 11, 2021 at 5:14 | comment | added | Vince | The examples in the linked document are all UPPERCASE in that section (6.2.3); it would have been nice if the case insensitivity of WKT was mentioned in 6.2, where WKT was defined, and included in the examples, as well. | |
| Nov 10, 2021 at 20:05 | history | edited | user30184 | CC BY-SA 4.0 |
added 441 characters in body
|
| Nov 10, 2021 at 20:01 | comment | added | user30184 |
Any help with interpreting BNF is welcome, but I think that "point" within Point Text refers to 0-dimensional geometrin object and not to any character string. But this sentence in 7.2.1 is rather easy to interpret: The text representation of the instantiable Geometry Types implemented shall conform to this grammar. Well known text is case insensitive. Where human readability is important (as in the examples in this standard), an “upper camel-case” where each embedded word is capitalized, should be used
|
|
| Nov 10, 2021 at 16:11 | comment | added | Vince |
The <name> definition doesn't seem applicable to WKT, since while 'qweRtyAsdF' is a valid name, it isn't a valid geometry type. In 6.2.2 (p. 28) it states that <Point Tagged Text> := POINT <Point Text>, where <Point Text> := EMPTY | ( <Point> ), <Point> is <x> <y>, and <x> and <y> are " double precision literal" values. It doesn't state that "POINT" is (P|p)(O|o)(I|i)(N|n)(T|t), so there's room for trouble. But I wouldn't reject poinT either.
|
|
| Nov 10, 2021 at 15:21 | history | answered | user30184 | CC BY-SA 4.0 |