You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, OSM divides a country into smaller regions at certain point in time. To retrieve historical data in such cases, we need to examine two web pages, the national level and, once the country is split up, the regional level.
For example, if we want historical data for Barcelona from now until 2021, we get the daya from this URL. However, for earlier data (e.g., from 2012 to 2021), we need to go to the national-level download page.
With the current feature, when this is the case, to downloading data from previous years to the area split, you have to explicitly specify the desired level (national, i.e. 2). Otherwise, the process doesn't work.
It would be helpful to either explain this issue in the vignette or enhance the feature/function to automatically determine the appropriate level based on the availability of OSM data.
The text was updated successfully, but these errors were encountered:
eugenividal
changed the title
'version' feature for cases where OSM splits a country into regions at certain point in time
Issue with the 'version' feature when OSM split up a country into regions at certain point in time
Jan 24, 2025
A follow-up regarding the
version
feature:Sometimes, OSM divides a country into smaller regions at certain point in time. To retrieve historical data in such cases, we need to examine two web pages, the national level and, once the country is split up, the regional level.
For example, if we want historical data for Barcelona from now until 2021, we get the daya from this URL. However, for earlier data (e.g., from 2012 to 2021), we need to go to the national-level download page.
With the current feature, when this is the case, to downloading data from previous years to the area split, you have to explicitly specify the desired level (national, i.e. 2). Otherwise, the process doesn't work.
It would be helpful to either explain this issue in the vignette or enhance the feature/function to automatically determine the appropriate level based on the availability of OSM data.
The text was updated successfully, but these errors were encountered: