Search results

Explicitly allow more flexibility in how geometries are stored

Status: Open.

#162 In zephyr-data-specs/GMNS;

· ssmith55 opened on Mar 17, 2026

PR for GMNS 0.97

Status: Open.

#157 In zephyr-data-specs/GMNS;

· ssmith55 opened on Jan 20, 2026

Notes from adding Lima signal data to example network

Status: Open.

#124 In zephyr-data-specs/GMNS;

· ianberg-volpe opened on Feb 19, 2025

Clarify bike path specification

Status: Open.

#115 In zephyr-data-specs/GMNS;

· gregmacfarlane opened on Oct 16, 2024

Specification Clarification for node_id and zone_id in node.csv

Status: Open.

#83 In zephyr-data-specs/GMNS;

· ghost opened on Jul 9, 2024

[EPIC] Resolve differences in terminology/terms w/ other relevant standards

Status: Open.

#71 In zephyr-data-specs/GMNS;

· e-lo opened on Jan 19, 2024

🐛 Need to clarify if required means a required column OR also required valid data within column

Status: Open.

#70 In zephyr-data-specs/GMNS;

· e-lo opened on Jun 13, 2023

Implement continuous integration/testing to make sure spec isn't malformed

Status: Open.

#66 In zephyr-data-specs/GMNS;

· e-lo opened on Jun 12, 2023

Replace x_coord, y_coord, z_coord in the Node and Location tables with the well-known-text (wkt) representation of a point

Status: Open.

#43 In zephyr-data-specs/GMNS;

· ssmith55 opened on Aug 24, 2020

Create issue templates, pull-requests and issue tags

Status: Open.

#41 In zephyr-data-specs/GMNS;

· e-lo opened on Aug 17, 2020

Create a tagged version (geojson) of selected GMNS tables

Status: Open.

#38 In zephyr-data-specs/GMNS;

· ssmith55 opened on Jul 16, 2020

Integration with A/B Street?

Status: Open.

#36 In zephyr-data-specs/GMNS;

· dabreegster opened on Jul 4, 2020