Create a Common Questions doc page

[twelch]

That guides user through different decisions

• I have a unique planning boundary, which template should I start with and how do I add my boundary datasource and geography?
• I have a more authoritative EEZ boundary for a project, how should I use it?
• I want to use more than one EEZ polygon in my planning boundary, how do I do that?

May want to include an informal decision tree that helps guide decisions and points at resources and examples

[twelch]

Another example is choosing which global datasource to use so that preprocessing and geoprocessing work together.

Comments from the subregional PR

OSM land polygons have been traditionally used by SeaSketch as a baseline (coastline) because it matches basemaps that use OSM (like Mapbox used by SeaSketch). Its accuracy wasn't questioned until it was seen that for small island nations it can be missing small landmasses. This matters when defining for example a nearshore boundary for planning, if you are missing small islands, the nearshore area around them will not be included in the planning area or in drawn sketches. The % of area relative to the whole EEZ is small, but it could have localized impacts particularly regarding enforcement.

EEZ project template: preprocessors will default to using global-eez-with-land-mr-v3 and then clip to global-land-osm. Simple project template: default geography for basic projects will be the world.json polygon Template eez projects will have a default geography that uses global-eez-mr-v11 (eez with mr land baseline cut out), because it's available right now in global form. This will create a small misalignment with the osm land baseline used by the preprocessor. After creating a new report project, developers can then decide which baseline is best:

if the Marine Regions baseline is more accurate and should be used, then switch to a preprocessor that clips to global-eez-mr-v11. Keep the geography using global-eez-mr-v11. if the OSM baseline is accurate enough and fit of clipped shapes to the map is more important, then preprocessor can stay with global-eez-with-land-mr-v3 and a local geography can be created that takes the MR EEZ boundary and subtracts out OSM land, as we have traditionally done for all projects.