Revised Test Data CSV File: New Column Names

[Landon Blake]

Some javascript/style in this post has been disabled (why?)

Gentleman,

 

I have attached a revised CSV file with new column names. Hopefully this will scratch Martin’s abbreviation itch. :]

 

If we can get some consensus on the current format, I can start on a simple draft file format spec next week.

 

Landon

 

 

Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.

_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Hugues Wisniewski]

Some javascript/style in this post has been disabled (why?)

Hi,

 

Whatever names are chosen for the columns I think it would be nice to have the full name displayed at the beginning of the csv file in the comment section

Something like this:

 

# Each line represents a coordinate conversion  test. The format is as follows:

#

# Name = test name

# Type = Test Type

# SrcCrsTyp = source CRS authority

# ScrCRS = source CRS code

# ExpCrsTyp = expected CRS authority

# …

 

The idea is to avoid having to go to a different location like the wiki to be sure about the actual meaning of a given column

While having column names sounds great, for instance, the test.dat file in CsMap

http://svn.osgeo.org/metacrs/csmap/trunk/CsMapDev/Test/TEST.DAT

doesn’t have column names but has a detailed comment about each field. When I started working on CsMap I found this comment to be very useful, especially when moving the files around from one server to another over the years. The info was all in one place.

So abbreviated column names and a legend in the comment section would be nice

 

Hugues

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Landon Blake
Sent: Friday, November 06, 2009 9:35 AM
To: [hidden email]
Subject: [MetaCRS] Revised Test Data CSV File: New Column Names

 

Gentleman,

 

I have attached a revised CSV file with new column names. Hopefully this will scratch Martin’s abbreviation itch. :]

 

If we can get some consensus on the current format, I can start on a simple draft file format spec next week.

 

Landon

 

 

 

Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.

_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Frank Warmerdam]

Landon Blake wrote:

> Gentleman,
>
>  
>
> I have attached a revised CSV file with new column names. Hopefully this
> will scratch Martin’s abbreviation itch. :]
>
>  
>
> If we can get some consensus on the current format, I can start on a
> simple draft file format spec next week.

Landon,

I have done a preliminary implementation of a GDAL/OGR (+PROJ.4) test
script for your file and the one test passes.

   http://svn.osgeo.org/gdal/trunk/autotest/osr/osr_metacrs.py

I had to do a bit of work to properly expose EPSG Axis orientation logic
to Python to get it going.

Anyways, thanks for the work so far.  I don't mind some changes in column
names and interpretation - the script is easily modified.  When things
settle down, I'll try and add some tests.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, [hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Martin Desruisseaux]

Landon Blake a écrit :
> I have attached a revised CSV file with new column names. Hopefully this
> will scratch Martin’s abbreviation itch. :]

I'm fine with the proposed format. I have a few minor comments about the column
names, but I don't mind if peoples prefer to keep the current names.

1) I suggest to rename "srcCrsType" as "srcCrsAuthority" (or "srcCrsAuth" if
"Authority" is too long) since "Authority" is the term used by OGC 01-009. To
me, "crsType" sound like the class ("Geographic", "Projected", "Derived", etc.)

2) I suggest to rename "expCrs[Type]" as "tgtCrs[Authority]" ("tgt" is for
"target", but I'm fine with "dest" as well) since that CRS is part of the test
specification rather than a result expected to be calculated by the library.
This is different than "expOrd" which are the expected calculation results, so
the "exp" prefix is fine for them.

        Regards,

                Martin
_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Martin Davis]

+1 for both suggestions.

So we would have:

srcCrsType -> srcCrsAuth
expCrsType -> tgtCrsAuth
expCrs -> tgtCrs

Would it be worth changing "expOrd1" (et al) to "expTgtOrd1" (et al) for
symmetry and clarity?

Martin Desruisseaux wrote:

> Landon Blake a écrit :
>> I have attached a revised CSV file with new column names. Hopefully
>> this will scratch Martin’s abbreviation itch. :]
>
> I'm fine with the proposed format. I have a few minor comments about
> the column names, but I don't mind if peoples prefer to keep the
> current names.
>
> 1) I suggest to rename "srcCrsType" as "srcCrsAuthority" (or
> "srcCrsAuth" if "Authority" is too long) since "Authority" is the term
> used by OGC 01-009. To me, "crsType" sound like the class
> ("Geographic", "Projected", "Derived", etc.)
>
> 2) I suggest to rename "expCrs[Type]" as "tgtCrs[Authority]" ("tgt" is
> for "target", but I'm fine with "dest" as well) since that CRS is part
> of the test specification rather than a result expected to be
> calculated by the library. This is different than "expOrd" which are
> the expected calculation results, so the "exp" prefix is fine for them.
>
>     Regards,
>
>         Martin
> _______________________________________________
> MetaCRS mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/metacrs
>

--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
[phone]

_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Landon Blake]

Martin Davis wrote: " Would it be worth changing "expOrd1" (et al) to "expTgtOrd1" (et al) for symmetry and clarity?"

Any comments on this before I update the test file?

Landon
Office Phone Number: [phone]
Cell Phone Number: [phone]
 
 

-----Original Message-----
From: Martin Davis [mailto:[hidden email]]
Sent: Monday, November 09, 2009 2:42 PM
To: Martin Desruisseaux
Cc: Landon Blake; [hidden email]
Subject: Re: [MetaCRS] Revised Test Data CSV File: New Column Names

+1 for both suggestions.

So we would have:

srcCrsType -> srcCrsAuth
expCrsType -> tgtCrsAuth
expCrs -> tgtCrs

Would it be worth changing "expOrd1" (et al) to "expTgtOrd1" (et al) for
symmetry and clarity?

Martin Desruisseaux wrote:

> Landon Blake a écrit :
>> I have attached a revised CSV file with new column names. Hopefully
>> this will scratch Martin's abbreviation itch. :]
>
> I'm fine with the proposed format. I have a few minor comments about
> the column names, but I don't mind if peoples prefer to keep the
> current names.
>
> 1) I suggest to rename "srcCrsType" as "srcCrsAuthority" (or
> "srcCrsAuth" if "Authority" is too long) since "Authority" is the term
> used by OGC 01-009. To me, "crsType" sound like the class
> ("Geographic", "Projected", "Derived", etc.)
>
> 2) I suggest to rename "expCrs[Type]" as "tgtCrs[Authority]" ("tgt" is
> for "target", but I'm fine with "dest" as well) since that CRS is part
> of the test specification rather than a result expected to be
> calculated by the library. This is different than "expOrd" which are
> the expected calculation results, so the "exp" prefix is fine for them.
>
>     Regards,
>
>         Martin
> _______________________________________________
> MetaCRS mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/metacrs
>

--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
[phone]



Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.
_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Landon Blake]

Version 00.12.00 CSV file is attached with revised column names as requested below.

Landon
Office Phone Number: [phone]
Cell Phone Number: [phone]
 
 

-----Original Message-----
From: Martin Davis [mailto:[hidden email]]
Sent: Monday, November 09, 2009 2:42 PM
To: Martin Desruisseaux
Cc: Landon Blake; [hidden email]
Subject: Re: [MetaCRS] Revised Test Data CSV File: New Column Names

+1 for both suggestions.

So we would have:

srcCrsType -> srcCrsAuth
expCrsType -> tgtCrsAuth
expCrs -> tgtCrs

Would it be worth changing "expOrd1" (et al) to "expTgtOrd1" (et al) for
symmetry and clarity?

Martin Desruisseaux wrote:

> Landon Blake a écrit :
>> I have attached a revised CSV file with new column names. Hopefully
>> this will scratch Martin's abbreviation itch. :]
>
> I'm fine with the proposed format. I have a few minor comments about
> the column names, but I don't mind if peoples prefer to keep the
> current names.
>
> 1) I suggest to rename "srcCrsType" as "srcCrsAuthority" (or
> "srcCrsAuth" if "Authority" is too long) since "Authority" is the term
> used by OGC 01-009. To me, "crsType" sound like the class
> ("Geographic", "Projected", "Derived", etc.)
>
> 2) I suggest to rename "expCrs[Type]" as "tgtCrs[Authority]" ("tgt" is
> for "target", but I'm fine with "dest" as well) since that CRS is part
> of the test specification rather than a result expected to be
> calculated by the library. This is different than "expOrd" which are
> the expected calculation results, so the "exp" prefix is fine for them.
>
>     Regards,
>
>         Martin
> _______________________________________________
> MetaCRS mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/metacrs
>

--
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
[phone]



Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.

_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Frank Warmerdam]

Landon Blake wrote:

> Version 00.12.00 CSV file is attached with revised column names as requested below.
>
> Landon
> Office Phone Number: [phone]
> Cell Phone Number: [phone]
>  
>  
>
> -----Original Message-----
> From: Martin Davis [mailto:[hidden email]]
> Sent: Monday, November 09, 2009 2:42 PM
> To: Martin Desruisseaux
> Cc: Landon Blake; [hidden email]
> Subject: Re: [MetaCRS] Revised Test Data CSV File: New Column Names
>
> +1 for both suggestions.
>
> So we would have:
>
> srcCrsType -> srcCrsAuth
> expCrsType -> tgtCrsAuth
> expCrs -> tgtCrs

Landon,

I think you neglected to change tgtCrsType to tgtCrsAuth.

Also, the leading comment lines break my .csv reader.  I'd suggest putting
explanatory text in a Test_Data_File.txt associated with the data file.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, [hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Martin Desruisseaux]

Landon Blake a écrit :
> Version 00.12.00 CSV file is attached with revised column names as requested below.

Seems good to me (with the name change pointed by Frank).

I assume that the next steps are to transfert the test data from various
projects to this format, then eventually split the file according some criterion
to be determined? Or do you prefer to define the criterions first?

        Martin
_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Landon Blake]

I corrected the column name I forgot in the last revision. I also
attached two (2) CSV files. The first one has comments, the second does
not.

At some point, I will need to do some work on a description of our file
format.

Will I be able to commit these files to SVN soon? That way you guys
don't have to monkey around with e-mail attachments every time I need to
correct something I forgot.

Landon
Office Phone Number: [phone]
Cell Phone Number: [phone]
 
 
-----Original Message-----
From: Frank Warmerdam [mailto:[hidden email]]
Sent: Wednesday, November 11, 2009 11:11 AM
To: Landon Blake
Cc: [hidden email]
Subject: Re: [MetaCRS] Revised Test Data CSV File: New Column Names

Landon Blake wrote:
> Version 00.12.00 CSV file is attached with revised column names as
requested below.

>
> Landon
> Office Phone Number: [phone]
> Cell Phone Number: [phone]
>  
>  
>
> -----Original Message-----
> From: Martin Davis [mailto:[hidden email]]
> Sent: Monday, November 09, 2009 2:42 PM
> To: Martin Desruisseaux
> Cc: Landon Blake; [hidden email]
> Subject: Re: [MetaCRS] Revised Test Data CSV File: New Column Names
>
> +1 for both suggestions.
>
> So we would have:
>
> srcCrsType -> srcCrsAuth
> expCrsType -> tgtCrsAuth
> expCrs -> tgtCrs

Landon,

I think you neglected to change tgtCrsType to tgtCrsAuth.

Also, the leading comment lines break my .csv reader.  I'd suggest
putting
explanatory text in a Test_Data_File.txt associated with the data file.

Best regards,
--
---------------------------------------+--------------------------------
------
I set the clouds in motion - turn up   | Frank Warmerdam,
[hidden email]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent



Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.



_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs

[Landon Blake]

Roger that. I'm just glad we are getting something everyone can use. :]

Landon
Office Phone Number: [phone]
Cell Phone Number: [phone]
 
 

-----Original Message-----
From: Martin Desruisseaux [mailto:[hidden email]]
Sent: Thursday, November 12, 2009 9:35 AM
To: Landon Blake
Subject: Re: [MetaCRS] Revised Test Data CSV File: New Column Names

Hello Landon

Landon Blake a écrit :
> I'm not sure if we intend to split the CSV file. If we do, what criterion do you have in mind?

Nothing particular. I though that Norm or Martin Davis or some other wanted to
split the file. On my side, I'm totally neutral on this aspect.

        Martin


Warning:
Information provided via electronic media is not guaranteed against defects including translation and transmission errors. If the reader is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this information in error, please notify the sender immediately.
_______________________________________________
MetaCRS mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/metacrs