1. There is no Unique Identifier between your English and French Data. You need to add a Unique ID column that represents the specific border. 2. You have double semi-colons in your data. CSV readers read this as an extra empty column after every column with data. There should only be 1 semi-colon. It would be better if you created a proper standards CSV file with Quoted Text and comma separated. 3. There should be no semi-colon on the last column. A Semi-colon is only used to denote a new column. It is not used to denote the end of a column. 4. Your dates use non-standard timezone abbreviations which are not used in the global community: "2017-11-14 08:10 PST”, where PST is not globally known and therefore time parsers that convert this into a system data/time do not typically support timezone abbreviations. You should be using ISO8601 timezone formats. 5. You need to provide a data dictionary for how you will display delay information. Will it always be in minutes? What if the delay is 2.5 hours? Will this be displayed as “2.5 hours”, “2 hours 30 minutes”, “150 minutes”, etc. Systems need to parse your data and need to know how you present your data. 6. Why do you show data as “--“ for columns that you do not support data for? Example: All the US bound columns have the double hyphen. Do you never support data for these directions? If not, why are they included in the data? If you do support them, when, please provide examples. 7. In the location column you have locations without context. What do all of the abbreviations mean? NB, ME, NB, ND, WA, etc. Yes we can figure it out based on human context. But for a system you should be providing more information such as the full name or at least the country. Otherwise we have to parse and edit the data to make it readable by others. 8. What is the Rate of Updates to the wait times? How are wait times collected? Automatic? Automated? Human input? Are wait times always updated at the same times? We need to know this type of information so that when a system is polling the data to collect the updates, it is not looking every minute, when the times are only updated every 30 minutes.
Temps d'attente à la frontière
Temps d'attente approximatif (débit commerciale et voyageurs) à la frontière aux postes frontaliers terrestres de l'Agence des services frontalier du Canada les plus occupés.
Note : Le jeu de données de l’ASFC contient des données pour les voyageurs qui entrent au Canada. On retrouve sur le site Web du « U.S. Customs and Border Protection » le jeu de données pour les temps d’attentes en direction des É.U. Pour accéder leur jeu de données, veuillez consulter le site Web de temps d’attente à la frontière du « C.B.P. » (anglais) et leur document d’aide (anglais).
- Éditeur - Nom actuel de l’organisation: Agence des services frontaliers du Canada
- Licence: Licence du gouvernement ouvert - Canada
Hello, Thank you for the detailed feedback, I have forwarded your comment to the data owner. I will post their response here once I receive it. Regards, Momin Open Government team
the structure of the data is full of errors that make it useless for consumption by other systems
Hello, Thank you for your feedback, it has been forwarded to the data owner. Regards, Momin Open Government team
Can you please return dates in a proper ISO8601 format. Using the Timezone abbreviations are incorrect usage and ambiguous
Why does the csv file have empty columns? There are what looks like double semi-colons, but they parse to empty columns.. WHY?!
It seems these sets do not include actual data fro the US bound times but your website has this data. Would be really nice to have those columns populated. Do you plan on doing this? If so, do you have an expected time?
Hi, thank you for your comment. I have forwarded your inquiry to the data owner for response. Stay tuned! Momin, the Open Government team.
Response from data owner: Thank you for your question regarding US bound wait times. The CBSA is not the owner of the US border wait times data. Please visit the U.S. Customs and Border Protection to access their dataset. Here is a link to their wait times application (https://bwt.cbp.gov/index.html) and the help file on accessing their dataset (https://bwt.cbp.gov/Content/bwt_help.pdf). Hope this helps! Momin, the Open Government team.
Please document units. The Border Wait Times page on CBSA that was linked at some point shows either None or ## minutes. The file here simply gives a number, but nowhere is it stated that the number is in minutes, hours, travellers, vehicles, or any other random unit.
I find this file tremendously useful. However the way it currently handles closed border crossings is not quite what I'd expect. Why do closed border crossings simply not appear on the list? Edmundston crossing is closed today (Aug 15, 2014) according to this page here [ http://www.cbsa-asfc.gc.ca/bwt-taf/menu-eng.html#_s2 ]. Is there a separate file available that documents the open/closed status of a crossing? I realize that border wait times are not the same as closures -- a wait time for a closed border crossing is indefinite. If I have a program parsing this data, how does one expect that when searching for specifically named border crossing is truly closed (temporarily or otherwise) or has had a name change? Please, either provide a machine processable file that indicates temporary closure status on affected border crossings or simply include a "closed" status to be input for the existing border wait times CSV file. Thank you.
Thank you for your comment. We have sent it off to the data owners at Canada Border Services Agency and they have informed us that they are currently looking into your request. Thank you for your patience.
Il serait intéressant, afin de rendre le tout synchronisé avec le gouvernement américain, de publier le temps d'attente dans les voies Nexus pour entrer au Canada. Merci
Merci pour votre commentaire. Malheureusement, à l’heure actuelle l’ASFC ne possède et ne conserve pas de données sur le temps d’attente à la frontière pour les participants au programme NEXUS distinctes des données globales déjà publiées. N’hésitez pas à communiquer avec nous si vous avez d’autres questions.
Why data in this dataset incomplete/different (not current and does not include a number of lanes open) from the data available http://travel.gc.ca/travelling/border-times-us
Thank you for your feedback. We have forwarded your comment to the dataset provider for their response.
I'd like GPS coordinates (latitude and longitude) of each border crossing location added to this file.
Thank you for your comment. The following response has been posted on behalf of the data owner : "Hello, we currently do not have the requested data set available. Your request has been logged and we hope to add this data set to our Open Data collection in the future". Thanks, Data.gc.ca.
This file is stupid. Have you actually opened it? Useless.
What would make this file NOT stupid? What information would you like in it? I would like GPS coordinates for each border crossing location. I would also like ALL US/Canada crossings included.
The following comment has been posted on behalf of Canada Border Services Agency : Thank you for your comment. This data set displays wait times for reaching the CBSA primary inspection booth when crossing the Canada/U.S. land border. More information on Border Wait Times data can be found at http://www.cbsa-asfc.gc.ca/bwt-taf/menu-eng.html#_s1. At this time, we are unsure as to what specifically you are having issues with. Please contact email@example.com so we can address your concerns directly. Thank you.