全域を対象とする場合の例外: 運用エリアが市、州、国全体などの公式な境界と一致する場合、お客様は独自のファイルを提供する代わりに、デフォルトの Google マップの地政学的な境界を使用するようリクエストできます。送信の際には、地域の説明、裏付けとなるドキュメント（公式の道路網地図へのリンクなど）、境界の場所 ID を添付する必要があります。プレイス ID は、Google の境界の範囲から取得できます。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-05 UTC。"],[],[],null,["# Define jurisdictions\n\nThis document describes Google's policy and process around defining your\noperational jurisdiction for Roads Management Insights. A jurisdiction is a series of\none or more disjoint polygons that defines a region.\n\nTo ensure data is provided appropriately, Google ensures that users can only\ncreate and track routes only within their approved jurisdiction.\n\nAll customers must define their jurisdiction according to the following policy.\n\nPolygon submission requirements\n-------------------------------\n\nAny custom or extended jurisdiction polygon that you submit must adhere to the\nfollowing technical specifications:\n\n- **File Format:** GeoJSON RFC7949 (.geojson)\n- **File Size:** 1 File of Maximum 10MB\n- **Multiple polygons:** If a jurisdiction is composed of several distinct polygons, they must be combined and submitted as a single GeoJSON file.\n\nThe next sections provide details on the submission requirements for the\nfollowing scenarios:\n\n- [Public sector customers (e.g., Cities, National and State DoTs)](#public)\n- [Private customers (e.g., Highway and Utility Providers)](#private)\n- [Extended jurisdiction requests (applies to all customers)](#all)\n\n### Public sector customers (e.g., Cities, National and State DoTs)\n\nThe following list describes the types of jurisdiction polygons public sectors\ncan submit and their requirements:\n\n- **Default boundary:** By default, a customer's jurisdiction is defined by the corresponding Google Maps Geopolitical Feature (e.g., the official city, county, state, country boundary).\n - Customers can refer to [Google boundaries\n coverage](/maps/documentation/javascript/dds-boundaries/coverage) to view boundary shape and retrieve Place ID required for onboarding. Google won't provide the polygon file to the customer.\n- **Custom polygon:** If a customer finds the default Google Maps boundary to be insufficient or inaccurate, they may submit their own polygon file for our team to verify.\n - Max 1 GB GeoJSON file with polygon of your jurisdiction. If there are several polygons, upload one single file for all.\n\n### Private customers (e.g., Highway and Utility Providers)\n\nThe following list describes the requirements for private customers to define\ntheir jurisdiction polygon:\n\n- **Required submission:** Private customers are required to provide a polygon file that defines their specific area of operational jurisdiction and a supporting document.\n - Max 1 GB GeoJSON file with polygon of your jurisdiction. If there are several polygons, upload one single file for all.\n- **Verification:** The submission must be accompanied by a description of the area and supporting documentation (e.g., a link to an official road network map).\n- **Exception for full-area coverage:** If a customer's operational area matches an official boundary, such as an entire city, state, or country, they may request to use the default Google Maps Geopolitical Feature boundary instead of providing their own file. The submission must be accompanied by a description of the area, supporting documentation, for example, a link to an official road network map, and Place ID(s) for the boundary. Place IDs can be retrieved from [Google boundaries\n coverage](/maps/documentation/javascript/dds-boundaries/coverage).\n\n### Extended jurisdiction requests (applies to all customers)\n\nCustomers may request data for areas larger than their primary jurisdiction by\nproviding a polygon file and a clear business justification. All such requests\nare subject to a manual review by our Operations Team.\n\nThe Operations Team will evaluate requests based on the following guidelines:\n\n- **Standard review:** Requests will be reviewed for approval if the area:\n - Extends no more than 20km from the customer's primary boundary; AND\n - Remains within the customer's national boundaries.\n- **Case-by-case review:** Requests for areas that exceed the 20km buffer but have a strong, demonstrable impact on the customer's primary jurisdiction will be considered for approval on a case-by-case basis (e.g., a county transportation authority needing visibility into a neighboring region).\n- **Requires special approval:** Any request for a jurisdiction that crosses national boundaries must be flagged for special review.\n\nJurisdiction onboarding process\n-------------------------------\n\nDuring your onboarding process, a representative from Google reaches out to you\nfor your jurisdiction details.\n\nAfter sharing your jurisdiction details, the process is as follows:\n\n1. **Review jurisdiction details**. The Google representative validates the jurisdiction information to ensure that the jurisdiction boundaries you provide match the region you manage.\n2. **Validation**. Once approved, Google uploads the jurisdiction into the system.\n3. **Jurisdiction upload**. The representative confirms the upload.\n4. **Create selected routes**. You can start creating selected-routes under given jurisdiction.\n\nTalk to your Google Representative if you need to make modifications to your\njurisdiction after the validation process."]]
