add schema for landCover, base theme#118
Conversation
|
This sounds great! I feel like the right place to initially have this discussion is within the
then we should push forward with it... |
thanks Victor Schappert (@vcschapp) - this PR is the result of discussion in that task force last week |
BoZivk
left a comment
There was a problem hiding this comment.
Shouldn't this be referenced within schema/schema.yaml?
|
Victor Schappert (@vcschapp) / Jennings Anderson (@jenningsanderson) / Jacob Wasserman (@jwass) / BoZivk |
The base branch was changed.
Victor Schappert (vcschapp)
left a comment
There was a problem hiding this comment.
Can we add a couple of examples and counter-examples specific to the land_cover feature type?
6514db7 to
3977082
Compare
updating per conversation
add cartography container
add refs
adding to defs
fixing build error?
fix defs
fix defs?
remove propers, use container
add example
add land cover to featureType
|
Jonah Adkins (@jonahadkins) Wasn't there a version of this where min-max zoom level was expressed instead as a scale? |
originally, but we thought it was more confusing |
Jacob Wasserman (jwass)
left a comment
There was a problem hiding this comment.
Looking forward to getting this out there!
sentence case descriptions
|
PR for data license approval: https://github.com/OvertureMaps/tf-data-platform/pull/253 |
|
In schema meeting 2024-05-01, Jacob Wasserman (@jwass) indicated including ESA WorldCover for use as landcover is OK by legal. So this is not a blocker for merging. |
remove links
Proposal
Add multiple resolutions of global land cover data to base theme in Overture (sometime in 2024). Examples below from Meta's production basemaps.
Low Resolution, minZoom=0, maxZoom=4
Medium Resolution, minZoom=4, maxZoom=9
High Resolution, minZoom=9, maxZoom=24
Background
The Display Maps team at Meta recently completed a project to integrate global land cover data into it's basemaps. Landcover data provides an opportunity o display continuous, gapless representation of the Earth's natural surfaces. We derived these products from the 2020 European Space Agency (ESA) raster land cover product. Our process was generally: (1) download the image tiles, (2) process them, (3) vectorize them, and finally (4) post-process them to a usable format for vector tiling. We publicly released these with our Daylight product last year (Blog).
For Discussion
(1) IMO this is a huge opportunity for Overture to provide a massive dataset, critical to every global basemap used in a multitude of mapping applications. This would be a first-of-its kind public dataset, it's hard to develop for day-to-day mappers, and is a huge technical lift at global scale.
Examples of land cover in production across several providers.

(2) Providing multiple resolutions meets the needs of map developers and cartographers who would use this data in their workflows. We could provide only the highest resolution, but users would need to develop complex processes to generalize and simplify the data. Providing only medium or low resolution would fall short of expectations for this type of dataset.
Providing tile zoom recommendations is probably a better way to define resolution than a specific reference scale like 1:1,000,000 or text like 'medium'.
(3) This is typically a "one and done" type dataset. This type of data is generally only needs refreshing every 5 to 10 years, and adding metadata such as
yearandsourcehelps define that.(4) While this type of data can be found in OpenStreetMap, this product provides continuous coverage across the globe.