Hi, I can give you an advise: try to use (ISO) official code for the geometries and put it as characters. Sylvain Envoyé depuis Yahoo Mail pour Android Le sam., mai 25, 2019 à 0:41, Emmanuel Blondel (GMAIL)<emmanuel.blond...@gmail.com> a écrit : Dear all, I write here as i'm in process to submit a revision of /geometa/ package to CRAN in which i've enabled some coercing methods between main metadata object ISOMetadata from geometa, and foreign metadata objects (from emld / ncdf4 packages)
I've received a "pre-test archived" notification, because of the folllowing warnings dealing with the coercing: Warning: in method for 'coerce' with signature '"ISOMetadata","emld"': no definition for classes "ISOMetadata", "emld" Warning: in method for 'coerce' with signature '"emld","ISOMetadata"': no definition for classes "emld", "ISOMetadata" Warning: in method for 'coerce' with signature '"ncdf4","ISOMetadata"': no definition for classes "ncdf4", "ISOMetadata" Detail at: https://win-builder.r-project.org/incoming_pretest/geometa_0.5-0_20190524_153346/Windows/00check.log I've found this thread that seems to discuss the same matter: https://github.com/r-spatial/sf/issues/129 . I'm facing the same situation where there is no good reason enough to add emld, ncdf4 as Imports, but rather to keep them as Suggests, as they are only used in these specific converters. In the doubt, i prefer asking here if there is some good practice to deal with these warnings, eventually to avoid it, or if this is considered by CRAN team as false positive. Thanks a lot for your advice, Best, Emmanuel [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Dear all, I write here as i'm in process to submit a revision of /geometa/ package to CRAN in which i've enabled some coercing methods between main metadata object ISOMetadata from geometa, and foreign metadata objects (from emld / ncdf4 packages) I've received a "pre-test archived" notification, because of the folllowing warnings dealing with the coercing: Warning: in method for 'coerce' with signature '"ISOMetadata","emld"': no definition for classes "ISOMetadata", "emld" Warning: in method for 'coerce' with signature '"emld","ISOMetadata"': no definition for classes "emld", "ISOMetadata" Warning: in method for 'coerce' with signature '"ncdf4","ISOMetadata"': no definition for classes "ncdf4", "ISOMetadata" Detail at: https://win-builder.r-project.org/incoming_pretest/geometa_0.5-0_20190524_153346/Windows/00check.log I've found this thread that seems to discuss the same matter: https://github.com/r-spatial/sf/issues/129 . I'm facing the same situation where there is no good reason enough to add emld, ncdf4 as Imports, but rather to keep them as Suggests, as they are only used in these specific converters. In the doubt, i prefer asking here if there is some good practice to deal with these warnings, eventually to avoid it, or if this is considered by CRAN team as false positive. Thanks a lot for your advice, Best, Emmanuel [[alternative HTML version deleted]] ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
