search

wmgeolab / geoContrast

Data to support the comparison tool for geoBoundaries
2 stars 1 forks source link

GADM Years #12

Closed DanRunfola closed 3 years ago

DanRunfola commented 3 years ago

Let's change to "Unknown" for GADM

karimbahgat commented 3 years ago

I put 2018 because that's when the current v3.4 appears to have been released. The license file states: "These data were extracted from the GADM database (www.gadm.org), version 3.4, April 2018. " I agree that there won't be any way of knowing if all the boundaries were properly up to date at the time of the release, which is the case for most global datasets like this, but we do know it does not go any further than 2018. What would be a good text for indicating so, e.g. "Last updated 2018" or "2018 (Last updated)"?

DanRunfola commented 3 years ago

We record update date and the year the boundary represents separately. So for the represents year, it needs to be unknown. For the update date, 2018.

On Fri, May 28, 2021, 5:06 PM Karim Bahgat @.***> wrote:

I put 2018 because that's when the current v3.4 appears to have been released. The license file states: "These data were extracted from the GADM database (www.gadm.org), version 3.4, April 2018. " I agree that there won't be any way of knowing if all the boundaries were properly up to date at the time of the release, which is the case for most global datasets like this, but we do know it does not go any further than 2018. What would be a good text for indicating so, e.g. "Last updated 2018" or "2018 (Last updated)"?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wmgeolab/geoContrast/issues/12#issuecomment-850669587, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4EPFMSJGETVVNJ6Z7VMB3TQAAUXANCNFSM45JHT3MQ .