Closed btitaro closed 6 months ago
This can be safely ignored. It's because the timelapse_time
column is a special hms
(hours-minutes-second) data type, which mapview doesn't know what to do with, so it drops it. In practice it means that the mapview map won't have the column in it.
We have three options:
Ignore it, and/or drop that column yourself when you call mapview on it:
library(dplyr)
library(mapview)
mapview(select(deployments, -timelapse_time), zcol = "sample_station_label")
Import the timelapse_time
column as a regular character type (more flexible but perhaps less useful), or you can convert it to character when you don't want it in hms format:
deployments$timelapse_time <- as.character(deployments$timelapse_time)
Open an issue upstream in the sf
package, where the warning is being thrown...
Thanks Andy - Seems like option 1 might be easiest? We can discuss with others tomorrow as well though. Thanks again for the help yesterday!
Brian
From: Andy Teucher @.> Sent: Wednesday, May 8, 2024 5:24 PM To: bcgov/bccamtrap @.> Cc: Titaro, Brian WLRS:EX @.>; Author @.> Subject: Re: [bcgov/bccamtrap] mapview warning message (Issue #27)
[EXTERNAL] This email came from an external source. Only open attachments or links that you are expecting from a known sender.
This can be safely ignored. It's because the timelapse_time column is a special hms (hours-minutes-second) data type, which mapview doesn't know what to do with, so it drops it. We have three options:
library(dplyr) library(mapview)
mapview(select(deployments, -timelapse_time), zcol = "sample_station_label")
Import the timelapse_time column as a regular character type (more flexible but perhaps less useful)
Open an issue upstream in the sf package, where the warning is being thrown...
— Reply to this email directly, view it on GitHubhttps://github.com/bcgov/bccamtrap/issues/27#issuecomment-2101707848, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BHTXVTMH6C7CXQE2PIB23FDZBK62DAVCNFSM6AAAAABHNW4IISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBRG4YDOOBUHA. You are receiving this because you authored the thread.Message ID: @.***>
Agreed, option 3 would be the best, I might pursue it later down the road...