Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Make the product's catalog more visible

See original GitHub issue

I’ve just had the case of a user who didn’t know a product type was made available by eodag. The new website (#233) will display the content of product_types.yml in one of the sections of the Getting Started. However, this still won’t be so easy to find or to browse. eodag list or dag.list_product_types() return the content of the YAML file, but this is also not so easy to explore.

I was thinking that we could have a script to generate a nicely formatted HTML page of this catalog. We could generate it during the docs build and link it or embed it in the documentation. We could also generate this HTML the first time EODataAccessGateway is instantiated (like the whoosh index or the default configuration file) and have a method to open that page in a browser (e.g. dag.open_product_catalog()).

This would allow users to:

  • Easily see the products that are made available directly by eodag
  • Find the product’s identifier eodag uses (e.g. S2_MSI_L1C)

For each product, we could add the list of providers that make it available.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

aoyonocommented, Jul 9, 2021

Yes, the guess_product_type was an attempt to achieve that. It would definitely help to gather the EO community thoughts somewhere to enhance it.

sbrunatocommented, Jul 9, 2021

Hi @aoyono , glad to see your message! And also, thanks for the suggestion.

That is true that the product type may be something not so easy to handle : it can be named differently between eodag, one provider, or another one.

There already exist the “guess product type” functionality. Is is documented here (It might need an example to be more clear).

We may also add some more examples in the documentation to show how to use it, like:

eodag search --platform SENTINEL2 --processingLevel L1 --box 1 43 2 44 --start 2021-03-01 --end 2021-03-31

It is also related to #165 to have some keywords to describe product types, and query them

Read more comments on GitHub >

github_iconTop Results From Across the Web

Product Visibility Tools & Tips - Firebear Studio
This article contains the best product visibility tools and tips. You will discover how to increase both product and brand visibility.
Read more >
Catalog Visibility Options - WooCommerce
With Catalog Visibility Options, you have the ability to restrict visibility of products based on user role. To configure visibility on a per...
Read more >
8 Ways to Make Your Catalogs Stand Out | USPS Delivers
A successful catalog will display products in a clear, informative way while still showcasing individuality. Don't let your catalog get bogged down by ......
Read more >
Complete Guide On WooCommerce Product Visibility (Hide ...
WooCommerce product visibility gives you control over who gets access to particular items. Learn how to hide certain products on your store!
Read more >
All About WooCommerce Catalog Visibility Options - Codeable
Before proceeding any further, let's get a little more familiar with what WooCommerce's catalog mode has to offer. In short, the catalog ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found