Changes between Version 5 and Version 6 of GDAL20Changes

Timestamp:

Nov 3, 2010, 11:06:22 AM (13 years ago)

Author:

Mateusz Łoskot

Comment:

List of tickets related to the issues raised here

GDAL20Changes

@@ -35 +35 @@
 There are some things that can be hard when starting on gdal and are frequently on the mailing list.  Here is a starter list, if those types of changes are being considered.
 
-* Standardize command names.  Some are gdal_command others are gdalcommand
-
-* Running gdalinfo --formats should list the formats is some meaningful order.  On linux I can | grep 'format name' or sort or various other things to make it useful.  On Windows, I copy the result into notepad and then search (although more recently I installed gnuwin32).  Sort of nice that a report on supported formats is so numerous as to be a problem.
-
-* Coordinate order of [-projwin ulx uly lrx lry] makes sense if you think of it as a picture with 0,0 starting in the upper left.  Many geospatial people have been trained to think of the 'proper' coordinate order differently.  There is unlikely to be much agreement on this item so it may be best left alone.
+ * Standardize command names.  Some are gdal_command others are gdalcommand
+ * Running gdalinfo --formats should list the formats is some meaningful order.  On linux I can | grep 'format name' or sort or various other things to make it useful.  On Windows, I copy the result into notepad and then search (although more recently I installed gnuwin32).  Sort of nice that a report on supported formats is so numerous as to be a problem.
+ * Coordinate order of [-projwin ulx uly lrx lry] makes sense if you think of it as a picture with 0,0 starting in the upper left.  Many geospatial people have been trained to think of the 'proper' coordinate order differently.  There is unlikely to be much agreement on this item so it may be best left alone.
 
 
 == Considerations ==
-* These aren't that hard to learn
 
-* This will inconvenience long time user who will chronically do it the original way on their first try
+ * These aren't that hard to learn
+ * This will inconvenience long time user who will chronically do it the original way on their first try
+ * This will break a lot of written and running scripts that will need to be changed
 
-* This will break a lot of written and running scripts that will need to be changed
+== Related Tickets ==
+
+Tickets related to other similar issues raised in the past:
+
+ * #289 - OGRPoint::get*() members should be const
+ * #1629 - Replace all occurrences of std::string with CPLString
+ * #1743 - Const correctness in cpl_http module
+ * #1752 - Make new method in OGREnvelope following const-correctness
+ * #3127 - Use char const** instead of char** for input strings with pointer reset
+ * #3153 - Define OGRErr as enumerated type