docs: update README structure and document Places Insights samples#31
Merged
henrikvalv3 merged 1 commit intomainfrom Feb 25, 2026
Merged
docs: update README structure and document Places Insights samples#31henrikvalv3 merged 1 commit intomainfrom
henrikvalv3 merged 1 commit intomainfrom
Conversation
…tebook descriptions
n0531m
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the
README.mdto improve repository navigation, standardize link formatting, and help developers discover the new Places Insights samples.Changes included:
imagery_insightslink tostreet_view_insightsto reflect recent repository changes.places_insightsfolder to the "Available Recipe Collections" list, alphabetizing the top-level directories.places_insightssub-folders (notebooks,places-insights-demo, andsample_queries), explicitly noting that developers will be querying a BigQuery dataset using SQL.custom_location_scores,nevada_site_selection,sample_data_demo, andspot_check_results) so developers can quickly identify the right spatial analysis workflow for their needs.