# Missing nodes? **URL:** \ **Category:** Support\ **Created:** [March 3, 2020, 4:01pm UTC](https://community.citystrides.com/t/missing-nodes/19331 "2020-03-03T16:01:12Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)\ **Post date:** [March 3, 2020, 5:36pm UTC](https://community.citystrides.com/t/missing-nodes/19331/2 "2020-03-03T17:36:41Z")
It’s possible that Naarderstraatweg wasn’t tagged properly at the time of the import ( [Overpass Street Query](https://community.citystrides.com/t/overpass-street-query/18631) ). Another possibility, relating to the “part of a street is a bike path” issue, is that if the bike path portion of the street is not named the same as the street, then it will exist in CityStrides as a separate street (assuming that it’s tagged in a way that will allow it to import). Basically, OSM doesn’t have “streets” it only has “segments” - so during my import I have to collect all of the individual segments and group them into a single street record. I do this based on the name tag. (This is also why there are sometimes two streets in one city with the same name, existing in CityStrides as a single street record) --- _[View the full topic](https://community.citystrides.com/t/missing-nodes/19331)._