|
|
|
Landon Blake
|
Some javascript/style in this post has been disabled (why?)
I have attached a revised version of the CSV file. Thank you
for the fine comments. This is the value of working with a group. :] Here are a list of the column name abbreviations that I used: tn = test name scrsa = source CRS authority scrsc = source CRS code dcrsa = destination CRS authority dcrsc = destination CRS code so1 = source ordinate 1 so2 – source ordinate 2 so3 = source ordinate 3 edo1 = expected destination ordinate 1 edo2 = expected destination ordinate 2 edo3 = expected destination ordinate 3 o1t = suggested ordinate 1 tolerance o2t = suggested ordinate 2 tolerance o3t = suggested ordinate 3 tolerance er = environment requirements eos = expected ordinate source com = comments Hopefully we are getting closer. Landon Warning: _______________________________________________ MetaCRS mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/metacrs |
||||||||||||||||
|
Martin Davis
|
Landon,
Sorry to be a pain on this, but I think these abbreviations might be going a bit too far in the other direction. The style in the CSMap CSV files seems like a good compromise between concision and clarity to me. Example: SeqNbr,EpsgNbr,EsriNbr,OracleNbr,MapInfoNbr,OemNbr,Oracle9Nbr,CsMapNbr,CsMapName,CtmxName,AdskName,EpsgName,EsriName,OracleName,MapInfoName,OemName,GeoToolsName,OcrName,OgcName,GeoTiffName,Oracle9Name,LegacyName,CnvrsnName,CnvrsnComment,MaintenanceComment,Quality,UserFlag,RfcnQualifier (Avoiding spaces in the field names seems like a good idea, too. Not all systems can handle that). I'll take a crack at suggesting a list of field names sometime today. Martin Landon Blake wrote: > > I have attached a revised version of the CSV file. Thank you for the > fine comments. > > This is the value of working with a group. :] > > Here are a list of the column name abbreviations that I used: > > tn = test name > > scrsa = source CRS authority > > scrsc = source CRS code > > dcrsa = destination CRS authority > > dcrsc = destination CRS code > > so1 = source ordinate 1 > > so2 – source ordinate 2 > > so3 = source ordinate 3 > > edo1 = expected destination ordinate 1 > > edo2 = expected destination ordinate 2 > > edo3 = expected destination ordinate 3 > > o1t = suggested ordinate 1 tolerance > > o2t = suggested ordinate 2 tolerance > > o3t = suggested ordinate 3 tolerance > > er = environment requirements > > eos = expected ordinate source > > com = comments > > Hopefully we are getting closer. > > 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 > -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 _______________________________________________ MetaCRS mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/metacrs |
||||||||||||||||
|
Norm Olsen
|
In reply to this post
by Landon Blake
Some javascript/style in this post has been disabled (why?)
Hello All . . . To furthering the discussion with my suggestions: Name = test name Type = Test Type SrcCrsTyp = source CRS authority ScrCRS = source CRS code ExpCrsTyp = expected CRS authority ExpCrs = expected CRS code SrcOrd1 = source ordinate 1 SrcOrd2 source ordinate 2 SrcOrd3= source ordinate 3 ExpOrd1 = expected destination ordinate 1 ExpOrd2= expected destination ordinate 2 ExpOrd3 = expected destination ordinate 3 TolOrd1 = suggested ordinate 1 tolerance TolOrd2 = suggested ordinate 2 tolerance TolOrd3= suggested ordinate 3 tolerance Using = name of specific data source that was used to
generate the expected results. DataSource = expected ordinate source DataComments = comments concerning the data and/or data source,
especially the tolerance values. MaintenanceCmnt= comments concerning who did what and when to
the test. Original comment indicates who entered the test and when. Currently acceptable values for SrcCrsTyp and TrgCrsTyp: EPSG -> implies a numeric designation CSMAP -> implies a key name PROJ4 -> ??? ??? -> ??? ??? -> ??? Currently acceptable values for Type: CRS2D ->
two dimensional coordinate conversion CRS3D ->
three dimensional coordinate conversion SCALEM ->
meridional grid scale SCALEP ->
parallel grid scale CNVRG ->
convergence angle (ExpOrd1 is convergence angle in degrees) GEOID ->
geoid height (ExpOrd1 is geoid height always in meters) VDTM ->
vertical datum shift DATUM ->
geodetic datum shift GEOCTR ->
geocentric coordinate test MGRS-F ->
Military Grid Reference System Forward (ExpOrd1 is a string) MGRS-I ->
Military Grid Reference System Inverse (SrcOrd1 is a string) I have changed my suggestion concerning Environment to what may
be more useful: Using. That is, indicate the name(s) of the data source(s) which was/were
used to generate the expected results whenever there may be some controversy.
BY controversy, I mean there are two Spanish .gsb files, indicate which one the
test requires. The NTv2-0.gsb file name could be given to indicate that
access to that file is necessary for the test to succeed. It could also
be used to distringush between Canada’s version 1 and version 2 (although
version 1 is a pretty dead duck now). Anyway, I suggesting a Using field
as a replacement for an Environment field. Entries in the Using field
would be separated by space characters(???). Examples: NTv2-0.gsb PE7783V2.gsb G1999???.bin What do you think? Norm From:
[hidden email] [mailto:[hidden email]] On
Behalf Of Landon Blake I
have attached a revised version of the CSV file. Thank you for the fine
comments. This
is the value of working with a group. :] Here
are a list of the column name abbreviations that I used: tn
= test name scrsa
= source CRS authority scrsc
= source CRS code dcrsa
= destination CRS authority dcrsc
= destination CRS code so1
= source ordinate 1 so2
– source ordinate 2 so3
= source ordinate 3 edo1
= expected destination ordinate 1 edo2
= expected destination ordinate 2 edo3
= expected destination ordinate 3 o1t
= suggested ordinate 1 tolerance o2t
= suggested ordinate 2 tolerance o3t
= suggested ordinate 3 tolerance er
= environment requirements eos
= expected ordinate source com
= comments Hopefully
we are getting closer. Landon Warning: _______________________________________________ MetaCRS mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/metacrs |
||||||||||||||||
|
Martin Davis
|
Looks good, Norm. I bow to the master of CSV field names... 8^)
One suggestion - change Type to say TestMethod or TestOp. Type is so overloaded... And maybe Name -> TestName, for clarity. Martin Norm Olsen wrote: > > Hello All . . . > > To furthering the discussion with my suggestions: > > Name = test name > > Type = Test Type > > SrcCrsTyp = source CRS authority > > ScrCRS = source CRS code > > ExpCrsTyp = expected CRS authority > > ExpCrs = expected CRS code > > SrcOrd1 = source ordinate 1 > > SrcOrd2 source ordinate 2 > > SrcOrd3= source ordinate 3 > > ExpOrd1 = expected destination ordinate 1 > > ExpOrd2= expected destination ordinate 2 > > ExpOrd3 = expected destination ordinate 3 > > TolOrd1 = suggested ordinate 1 tolerance > > TolOrd2 = suggested ordinate 2 tolerance > > TolOrd3= suggested ordinate 3 tolerance > > Using = name of specific data source that was used to generate the > expected results. > > DataSource = expected ordinate source > > DataComments = comments concerning the data and/or data source, > especially the tolerance values. > > MaintenanceCmnt= comments concerning who did what and when to the > test. Original comment indicates who entered the test and when. > > Currently acceptable values for SrcCrsTyp and TrgCrsTyp: > > EPSG -> implies a numeric designation > > CSMAP -> implies a key name > > PROJ4 -> ??? > > ??? -> ??? > > ??? -> ??? > > Currently acceptable values for Type: > > CRS2D -> two dimensional coordinate conversion > > CRS3D -> three dimensional coordinate conversion > > SCALEM -> meridional grid scale > > SCALEP -> parallel grid scale > > CNVRG -> convergence angle (ExpOrd1 is convergence angle in degrees) > > GEOID -> geoid height (ExpOrd1 is geoid height always in meters) > > VDTM -> vertical datum shift > > DATUM -> geodetic datum shift > > GEOCTR -> geocentric coordinate test > > MGRS-F -> Military Grid Reference System Forward (ExpOrd1 is a string) > > MGRS-I -> Military Grid Reference System Inverse (SrcOrd1 is a string) > > I have changed my suggestion concerning Environment to what may be > more useful: Using. > > That is, indicate the name(s) of the data source(s) which was/were > used to generate the expected results whenever there may be some > controversy. BY controversy, I mean there are two Spanish .gsb files, > indicate which one the test requires. The NTv2-0.gsb file name could > be given to indicate that access to that file is necessary for the > test to succeed. It could also be used to distringush between Canada’s > version 1 and version 2 (although version 1 is a pretty dead duck > now). Anyway, I suggesting a Using field as a replacement for an > Environment field. Entries in the Using field would be separated by > space characters(???). > > Examples: > > NTv2-0.gsb > > PE7783V2.gsb > > G1999???.bin > > What do you think? > > Norm > > *From:* [hidden email] > [mailto:[hidden email]] *On Behalf Of *Landon Blake > *Sent:* Thursday, November 05, 2009 11:43 AM > *To:* [hidden email] > *Subject:* [MetaCRS] Quick and Dirty CSV File Version 00.10.10 > > I have attached a revised version of the CSV file. Thank you for the > fine comments. > > This is the value of working with a group. :] > > Here are a list of the column name abbreviations that I used: > > tn = test name > > scrsa = source CRS authority > > scrsc = source CRS code > > dcrsa = destination CRS authority > > dcrsc = destination CRS code > > so1 = source ordinate 1 > > so2 – source ordinate 2 > > so3 = source ordinate 3 > > edo1 = expected destination ordinate 1 > > edo2 = expected destination ordinate 2 > > edo3 = expected destination ordinate 3 > > o1t = suggested ordinate 1 tolerance > > o2t = suggested ordinate 2 tolerance > > o3t = suggested ordinate 3 tolerance > > er = environment requirements > > eos = expected ordinate source > > com = comments > > Hopefully we are getting closer. > > 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 > -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 _______________________________________________ MetaCRS mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/metacrs |
||||||||||||||||
|
Landon Blake
|
In reply to this post
by Landon Blake
Will revise the file with the new column names an repost tomorrow.
Any decisions on format for DMS values? Landon Office Phone Number: (209) 946-0268 Cell Phone Number: (209) 992-0658 -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Martin Davis Sent: Thursday, November 05, 2009 1:57 PM Cc: [hidden email] Subject: Re: [MetaCRS] RE: Quick and Dirty CSV File Version 00.10.10 Looks good, Norm. I bow to the master of CSV field names... 8^) One suggestion - change Type to say TestMethod or TestOp. Type is so overloaded... And maybe Name -> TestName, for clarity. Martin Norm Olsen wrote: > > Hello All . . . > > To furthering the discussion with my suggestions: > > Name = test name > > Type = Test Type > > SrcCrsTyp = source CRS authority > > ScrCRS = source CRS code > > ExpCrsTyp = expected CRS authority > > ExpCrs = expected CRS code > > SrcOrd1 = source ordinate 1 > > SrcOrd2 source ordinate 2 > > SrcOrd3= source ordinate 3 > > ExpOrd1 = expected destination ordinate 1 > > ExpOrd2= expected destination ordinate 2 > > ExpOrd3 = expected destination ordinate 3 > > TolOrd1 = suggested ordinate 1 tolerance > > TolOrd2 = suggested ordinate 2 tolerance > > TolOrd3= suggested ordinate 3 tolerance > > Using = name of specific data source that was used to generate the > expected results. > > DataSource = expected ordinate source > > DataComments = comments concerning the data and/or data source, > especially the tolerance values. > > MaintenanceCmnt= comments concerning who did what and when to the > test. Original comment indicates who entered the test and when. > > Currently acceptable values for SrcCrsTyp and TrgCrsTyp: > > EPSG -> implies a numeric designation > > CSMAP -> implies a key name > > PROJ4 -> ??? > > ??? -> ??? > > ??? -> ??? > > Currently acceptable values for Type: > > CRS2D -> two dimensional coordinate conversion > > CRS3D -> three dimensional coordinate conversion > > SCALEM -> meridional grid scale > > SCALEP -> parallel grid scale > > CNVRG -> convergence angle (ExpOrd1 is convergence angle in degrees) > > GEOID -> geoid height (ExpOrd1 is geoid height always in meters) > > VDTM -> vertical datum shift > > DATUM -> geodetic datum shift > > GEOCTR -> geocentric coordinate test > > MGRS-F -> Military Grid Reference System Forward (ExpOrd1 is a string) > > MGRS-I -> Military Grid Reference System Inverse (SrcOrd1 is a string) > > I have changed my suggestion concerning Environment to what may be > more useful: Using. > > That is, indicate the name(s) of the data source(s) which was/were > used to generate the expected results whenever there may be some > controversy. BY controversy, I mean there are two Spanish .gsb files, > indicate which one the test requires. The NTv2-0.gsb file name could > be given to indicate that access to that file is necessary for the > test to succeed. It could also be used to distringush between Canada's > version 1 and version 2 (although version 1 is a pretty dead duck > now). Anyway, I suggesting a Using field as a replacement for an > Environment field. Entries in the Using field would be separated by > space characters(???). > > Examples: > > NTv2-0.gsb > > PE7783V2.gsb > > G1999???.bin > > What do you think? > > Norm > > *From:* [hidden email] > [mailto:[hidden email]] *On Behalf Of *Landon Blake > *Sent:* Thursday, November 05, 2009 11:43 AM > *To:* [hidden email] > *Subject:* [MetaCRS] Quick and Dirty CSV File Version 00.10.10 > > I have attached a revised version of the CSV file. Thank you for the > fine comments. > > This is the value of working with a group. :] > > Here are a list of the column name abbreviations that I used: > > tn = test name > > scrsa = source CRS authority > > scrsc = source CRS code > > dcrsa = destination CRS authority > > dcrsc = destination CRS code > > so1 = source ordinate 1 > > so2 - source ordinate 2 > > so3 = source ordinate 3 > > edo1 = expected destination ordinate 1 > > edo2 = expected destination ordinate 2 > > edo3 = expected destination ordinate 3 > > o1t = suggested ordinate 1 tolerance > > o2t = suggested ordinate 2 tolerance > > o3t = suggested ordinate 3 tolerance > > er = environment requirements > > eos = expected ordinate source > > com = comments > > Hopefully we are getting closer. > > 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 > -- Martin Davis Senior Technical Architect Refractions Research, Inc. (250) 383-3022 _______________________________________________ MetaCRS mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/metacrs 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 |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |