Changes between Version 25 and Version 26 of FDORfc16

Timestamp:

Apr 20, 2008, 9:55:56 PM (16 years ago)

Author:

jbirch

Comment:

Less explicit about not filling in auth_name, auth_srid

FDORfc16

@@ -72 +72 @@
 == spatial_ref_sys ==
 
-SQLite databases require the following fields in their spatial_ref_sys table.  The SRID and SRTEXT columns must be populated with a unique identifier and a valid WKT spatial reference string respectively.  AUTH_NAME and AUTH_SRID may be populated where known, but are not critical to functionality and may be left null when unknown.
+SQLite databases require the following fields in their spatial_ref_sys table.
 
 || Column Name || Type || Notes ||
 || srid || INTEGER || an integer value that uniquely identifies each Spatial Reference System within a database ||
-|| auth_name || TEXT || the name of the standard or standards body that is being cited for this reference system. EPSG would be an example of a valid AUTH_NAME.  If unknown, leave as null. ||
-|| auth_srid || INTEGER || the ID of the Spatial Reference System as defined by the Authority cited in AUTH_NAME. {http://spatialreference.org/ref/epsg/26910 26910] would be an example of a valid EPSG srid (UTM Zone 10 NAD830).  If unknown, leave as null. ||
-|| srtext || TEXT || The Well-known Text Representation of the Spatial Reference System ||
+|| auth_name || TEXT || the name of the standard or standards body that is being cited for this reference system. EPSG would be an example of a valid AUTH_NAME. ||
+|| auth_srid || INTEGER || the ID of the Spatial Reference System as defined by the Authority cited in AUTH_NAME. {http://spatialreference.org/ref/epsg/26910 26910] would be an example of a valid EPSG srid (UTM Zone 10 NAD830). ||
+|| srtext || TEXT || The Well-known Text Representation of the Spatial Reference System. ||
 
 The suggested definition is: