Stay organized with collections
Save and categorize content based on your preferences.
As part of the ['Roads Management Insights'] onboarding process, a representative from
Google works with you to obtain additional details about your project. This page
outlines the categories of information you are required to share during
onboarding.
Provide jurisdiction details
Share information about your managed regions. See Define
jurisdictions
for more details.
Choose a cloud region
Choose a Google Cloud region from the list of BigQuery supported regions that is
geographically closest to where you'll access route data.
Since BigQuery does not support inter-regional data access, make sure your route
data resides within the same region from which it is accessed. This is also
where your historical data is stored. Ensure data storage in this region
complies with data-sovereignty rules.
If you already are a BigQuery user, consider your current region of choice to
make it easier to combine data to derive enhanced insights.
If your contract includes a Real-Time Operations package, you must also choose
Google Cloud region or regions for Pub/Sub. The list the Google Cloud regions
for Pub/Sub message storage is limited to certain regions. See Configure
message storage
policies
for more details.
Provide project number
Share your Google Cloud Project with your Google representative. The Google
Cloud Project number is used by Roads Management Insights for several purposes,
including:
Enabling project access to the Roads Roads Selection API, facilitating the
creation and management of designated routes. Keep in mind this project can
be separate from the project Number used to enable Google Cloud services.
Creating a private data exchange in Analytics Hub to host the historical
table listing, following the naming convention: Roads Management -
PROJECT_NUMBER.
Creating a BigQuery dataset of historical designated routes for the project.
See Accumulated road
data for
more information.
Creating a Pub/Sub topic for you to receive real-time data. See Real-time
road data for
more information.
Provide Google Cloud Account emails
Provide the Google Cloud account email(s) of everyone that needs to access
Analytics Hub and BigQuery for road data analysis. Google representatives will
grant Analytics Hub's Subscriber role to the accounts you provide.
Google Account email address(es) for BigQuery access: Provide the Google
Accounts (can be Gmail or Google Workspace) that will be granted access to
the data through BigQuery Sharing, also known as Analytics Hub. You can list
multiple email addresses, separated by comma
Google Account email address(es) for Pub/Sub Subscriber role: Provide
the Google Accounts that will have Pub/Sub subscriber permission assigned.
The provided accounts must also have required IAM
roles
in your project to be able to access the data.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[],[],null,["# Provide project information\n\nAs part of the \\['Roads Management Insights'\\] onboarding process, a representative from\nGoogle works with you to obtain additional details about your project. This page\noutlines the categories of information you are required to share during\nonboarding.\n\nProvide jurisdiction details\n----------------------------\n\nShare information about your managed regions. See [Define\njurisdictions](/maps/documentation/roads-management-insights/jurisdiction)\nfor more details.\n\nChoose a cloud region\n---------------------\n\nChoose a Google Cloud region from the list of BigQuery supported regions that is\ngeographically closest to where you'll access route data.\n\nSince BigQuery does not support inter-regional data access, make sure your route\ndata resides within the same region from which it is accessed. This is also\nwhere your historical data is stored. Ensure data storage in this region\ncomplies with data-sovereignty rules.\n\nIf you already are a BigQuery user, consider your current region of choice to\nmake it easier to combine data to derive enhanced insights.\n\nIf your contract includes a Real-Time Operations package, you must also choose\nGoogle Cloud region or regions for Pub/Sub. The list the Google Cloud regions\nfor Pub/Sub message storage is limited to certain regions. See [Configure\nmessage storage\npolicies](https://cloud.google.com/pubsub/docs/resource-location-restriction)\nfor more details.\n\nProvide project number\n----------------------\n\nShare your Google Cloud Project with your Google representative. The Google\nCloud Project number is used by Roads Management Insights for several purposes,\nincluding:\n\n1. Enabling project access to the Roads Roads Selection API, facilitating the creation and management of designated routes. Keep in mind this project can be separate from the project Number used to enable Google Cloud services.\n2. Creating a private data exchange in Analytics Hub to host the historical table listing, following the naming convention: Roads Management - \u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e.\n3. Creating a BigQuery dataset of historical designated routes for the project. See [Accumulated road\n data](/maps/documentation/roads-management-insights/accumulated-data) for more information.\n4. Creating a Pub/Sub topic for you to receive real-time data. See [Real-time\n road data](/maps/documentation/roads-management-insights/real-time-data) for more information.\n\nProvide Google Cloud Account emails\n-----------------------------------\n\nProvide the Google Cloud account email(s) of everyone that needs to access\nAnalytics Hub and BigQuery for road data analysis. Google representatives will\ngrant Analytics Hub's Subscriber role to the accounts you provide.\n\n- **Google Account email address(es) for BigQuery access:** Provide the Google Accounts (can be Gmail or Google Workspace) that will be granted access to the data through BigQuery Sharing, also known as Analytics Hub. You can list multiple email addresses, separated by comma\n- **Google Account email address(es) for Pub/Sub Subscriber role**: Provide the Google Accounts that will have Pub/Sub subscriber permission assigned.\n\nThe provided accounts must also have [required IAM\nroles](https://cloud.google.com/bigquery/docs/analytics-hub-view-subscribe-listings#required_roles)\nin your project to be able to access the data."]]
