Clarify AOI | Export | Share language

[LanesGood]

It is confusing to have multiple terms referring to predictions and exports. We have:

• AOI
  • On Explore page/main app, can refer to the selected area before prediction is run
  • On Explore page, also refers to selected area after prediction is run
  • On Projects list page, refers to exported maps
  • Has multiple meanings In frontend/backend codebases, and API
• Export
  • On Project individual page, we have "Exported maps" as a grouping with "AOI" referring to individuals
  • Has multiple meanings In frontend/backend codebases, and API
• Share
  • Explore page's "Export" dropdown states "Create Share URL" and "Copy Share URL"
  • Has multiple meanings In frontend/backend codebases, and API

[vgeorge]

@LanesGood I agree that we can improve the language. I believe the main issue is with 'exported maps.' The API calls them 'Shares.' We could normalize this in the frontend to 'Shared Maps,' avoiding 'Export/Exported'. But what if we just call them 'Maps' for simplicity, and refer to the ones marked as published: true (which are listed on the platform) as 'Public Maps'?

Whichever decision we make, I believe we should avoid any changes in the API.

cc @geohacker @ingalls

[LanesGood]

@vgeorge and I discussed the nature of what these maps are and have landed on the term "Prediction map." We think this is a better representation, as each set of exported prediction tiles from a unique project can represent a different AOI, different checkpoint, and different timeframe, but they all represent predictions.

So, the page in #68 will be "Public prediction maps," and the option in the export menu will be "Create/copy prediction map URL"