Conversation
🚀 Overture Maps docs branch preview deployed!You can review your changes at https://staging.overturemaps.org/docs/pr/281/index.html ♻️ Last refreshed: 2026-03-03T22:18:52Z |
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter MARKDOWNNATURAL_LANGUAGE |
Super-linter summary
Super-linter detected linting errors For more information, see the GitHub Actions workflow run Powered by Super-linter MARKDOWNNATURAL_LANGUAGE |
Adam Lastowka (Rachmanin0xFF)
left a comment
There was a problem hiding this comment.
Not the requested reviewer (hi Brad Richardson (@brad-richardson) 👀), but this is AWESOME. Didn't look at everything, but definitely a stellar rewrite. Easier on the eyes + more human.
| | theme | string | Name of the Overture theme being queried. | | ||
| | type | string | Name of the Overture feature type being queried. | | ||
| - The **segment** type has a LineString geometry that represents the center-line of a path repeatedly traversed by people or objects. Segment properties describe both the physical properties (e.g. road surface and width) and non-physical properties (e.g. access restriction rules) of that path. | ||
| - The **connector** type has a Point geometry that defines the topology of the transportation network by representing the physical connection between two or more segments. Connectors do not have properties beyond geometry and the common properties required for all Overture features. |
There was a problem hiding this comment.
Nit: the connector type doesn't really "[define] the topology" of the network; that information lives within the connectors field within the segment type. The connector type is just a convenient list of "the positions of all links between segments", but this is redundant information that can be reconstructed from the segments alone.
What's in this PR?
To do