Changes between Initial Version and Version 1 of DevWikiISO19125

Oct 15, 2010, 7:46:28 AM (11 years ago)



  • DevWikiISO19125

    v1 v1  
     1= ISO19125 Draft Comments =
     3This page is a collection of notes/questions based upon readings of the ISO19125 draft standard.
     5= General Questions & Answers =
     71) Confirmation that ST_AsText() and ST_AsBinary() can handle more than 2 dimensions and also parse SRID information. How should the SRID be parsed in both WKT and WKB?
     92) A decision as to where the central authority for allocating/administering ISO-19125 SRIDs should reside. Who would maintain this information?
     10How can we download updates to this information?
     123) A matrix to define the handling of spatial predicates when NULL/EMPTY geometries form one or both of the input geometries.
     13We've already attempted to document this on the wiki here: but there are still many cases that need to resolved.
     154) A matrix to define which spatial functions are valid for which geometry types (e.g. POINT, POLYGON etc.), and if so, what should they return?
     16e.g. if calculating distance between a POINT and a POLYGON, or between 2 surfaces - how should this be done?
     185) If the specification is to allow > 2 dimensions, I'd like to see a table documenting how the spatial predicates such as ST_Union(), ST_Within() etc. should behave in these cases.
     20Should we ignore the 3rd dimension or calculate in 2.5D? A complete set of examples for all predicates should be given in the documentation to allow us to verify the behaviour of existing geometry libraries (e.g. GEOS, Boost).
     226) Clarification of precision models used for all calculations.
     24Do we assume double precision floating point numbers for all inputs? What if users want to specify their own precision? Does there need to be a fixed point alternative representation?
     267) Clarification on the definitions of IsSimple and IsValid. Is IsSimple just for point and linear features and IsValid just for areal features as PostGIS has interpreted the current specs to be?  Or is IsValid for all feature types as SQL Server has interpreted the specs to be?
     288) Documentation for each type detailing the exact criteria which make a geometry valid (e.g. minimum number of points, size)
     30Is a geometry with repeated points considered valid?
     329) Do the spatial predicates require validity to function? How should the database behave if a non-valid geometry is passed into one of these functions? Should the WKT/WKB parser explicitly reject invalid geometries?
     3410) Why has the ST_ function prefix been dropped?
     3611) Definition of TRIANGLE:
     38Unless I'm wrong, this is just a really stupid definition for the TRIANGLE WKB (from the "modularized" ISO draft)
     42  byte byteOrder;
     43  static uint32  wkbType = 17;
     44  uint32  numRings;
     45  LinearRing rings[numRings]
     48I mean, it's a triangle right? How many rings does it have? And how many points are in that ring? At a minimum it should be reduced to:
     52  byte byteOrder;
     53  static uint32  wkbType = 17;
     54  LinearRing ring;
     5712) Clarification of acceptance of data from other sources, e.g. WKB geometries encoded with SQL-MM geometry types such as 1000000001  - how/should these be accepted?
     5913) How are empty geometries encoded in WKB?
     6114) How are SRIDs encoded in both WKT and WKB?