In the early phase of development on OQT custom regions where defined for which indicators should be computed. The definitions of regions are quite arbitrary as are the boundaries of regions (In many cases a rectangular bbox).
Today those are the regions for which OQT provides pre-computed indicator results through the website to end-users. In fact those are the only regions for which indicator results can be accessed through the website.
In the future available regions should extent to admin boundaries and/or hexagonal cells covering the globe. But for now OQT restricts it to above mentioned custom regions.
For which regions should OQT provide pre-computed results?
Regions should be heterogeneous:
Urban and rural regions
Regions known for good and bad OSM data quality or coverage
Different size in area
Geometry should make sense (e.g. Administrative boundary)
Related to the main issue: I would really like to have a list (maybe as tabular like in the description) of all regions. Maybe we could integrate this into the webpage.
Region origin
In the early phase of development on OQT custom regions where defined for which indicators should be computed. The definitions of regions are quite arbitrary as are the boundaries of regions (In many cases a rectangular bbox).
Today those are the regions for which OQT provides pre-computed indicator results through the website to end-users. In fact those are the only regions for which indicator results can be accessed through the website.
In the future available regions should extent to admin boundaries and/or hexagonal cells covering the globe. But for now OQT restricts it to above mentioned custom regions.
For which regions should OQT provide pre-computed results?
Regions should be heterogeneous:
Regions should have following attributes:
Current regions
Proposed changes to regions
Remove
Update (Before)
Update (After)
Add