# Intersection ID

In some cases the Attribute Rule calculating the nearest Intersection ID will pull an Intersection ID from an intersection point that is not connected to the road segment that feature is placed on. This is because the Intersection ID is pulled from a[ Thiessen polygon](https://pro.arcgis.com/en/pro-app/tool-reference/analysis/create-thiessen-polygons.htm) layer created from the Intersection points. Due to this calculation method, make sure to check the Intersection ID that is calculated when creating new features. This field is editable and a new Intersection ID that makes more sense can be added.

![](https://lh3.googleusercontent.com/KbH1l9VeCcYtbUB5MBYaIHyLF6n17W8gKwcuEBvNVwdGfeI4aDwJl2EEJFBp5BluXgHMc9OZ0UiwHb4fVldO_GodqcHSWZDJ--LFrS-3LnD7ShynqbcbY2hoao3li8-nsWX5VdRfo2i5RpQtzRijwg)

Example showing Intersection Thiessen Polygons

In the example above, if any feature were to be placed along E Stassney Ln along the mid-point between Intersection IDs 5152923 and 5154236, it would have an Intersection ID that is not from either intersection along E Stassney Ln, and will instead be coded to the neighborhood street to the north.<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://atd-dts.gitbook.io/atd-geospatial/signs-markings-banners/markings-gis-maintenance/attribute-rules/intersection-id.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.