Add Data API Tile Preview Demo

[strixcuriosus]

Add Demo Notebook for Rendering Data API Search Results as Preview Tile Layers

This PR adds a demo notebook that showcases how to visualize Planet’s Data API search results as preview tile layers, similar to the preview experience in Planet Explorer, but directly in Python.

📋 Key Features:

• Search & Filter: Query the Data API using filters like date range, cloud cover, and AOI.
• Interactive Map: Use folium to display and toggle Planet satellite imagery preview tiles.
• GeoJSON AOI: Automatically centers the map on a user-defined GeoJSON AOI.
• Fast Preview: render imagery preview tiles without waiting for full order activation, streamlining decision-making.

🛠 What’s Included:

• API setup, AOI definition using GeoJSON, and creating Data API search with filters.
• Building Tile Service preview URLs for Data API results.
• Rendering search results as tile layers on a map.

🌟 Value:

• Offers a quick visualization experience, similar to Planet Explorer, but with the flexibility of Python.
• Enables fast, synchronous previews, speeding up decision-making
• Provides early insights before ordering, downloading, or delivering data

See #349

[olepinard]

Hi Ash, this looks really great and will be a helpful add to this repository. Looks good to me!

[matthew-ballard]

this looks great, just a few comments:

• could the shell command installs be removed and we add those packages to the requirements.txt file?
• suggest changing the search dates from 2016 to 2024, images look nicer

[nik-bladey]

It's great to see this.

One interesting thing about this demo is that it leverages two different APIs (Data API and Tile Service API), both of which are now maintained by the same team, which is tasked with the "Gather" phase of the platform experience. It might be worth (if not now, then at some point) renaming the directory to reflect that customer journey stage rather than being specific to Data API. @matthew-ballard, do you have thoughts on this?

[nik-bladey]

Also best to keep the README up-to-date.

[strixcuriosus]

• could the shell command installs be removed and we add those packages to the requirements.txt file?

@matthew-ballard thanks for the suggestion. This seems like a topic for bigger conversation outside of this specific notebook.

Including the special notebook-specific dependencies inline ensures that they don't get lost if someone shares or runs just the isolated notebook (without the full repo context). For example, some users will run individual notebooks directly in colab. IMO we should strive to make each notebook fully runnable (or documented) in a standalone environment.

It is also a common pattern in the data science community, for example see:

• hugging face notebook: https://github.com/huggingface/notebooks/blob/main/transformers_doc/en/quicktour.ipynb
• segment anything geospatial notebook: https://github.com/opengeos/segment-geospatial/blob/main/docs/examples/satellite.ipynb
• earth engine tutorial: https://github.com/giswqs/earthengine-py-notebooks/blob/master/Tutorials/GlobalSurfaceWater/1_water_occurrence.ipynb

Are you recommending updating the requirements.txt in planet-notebook-docker/requirements.txt ?
This requirements.txt has not been updated in 4 years, is buried under the docker section, and seems to be global for the entire repo.
I am happy to update this for now to include folium, but I know other notebook authors will prefer different mapping libraries, and I don't think we should have global dependencies as we grow out more of an ecosystem of notebook demos.

I would also like to keep the install command for those who wish to use this notebook without dealing with the global docker env setup so that it can work in colab or other environments with ease.