Please don’t feel bad - all feedback is helpful. I can’t fix/improve what I don’t know.
It’s also possible that there are other people with the same frustration, so us having this conversation in the open will help them as well. To that end: my reply here isn’t solely directed at you - it also includes related information that can help others or expand the conversation.
I don’t recall promising any update timeline. It’s still very much a work in progress (as you can see, based on the fact that this thread exists 
), and I still don’t have a good/reliable sense of how quickly cities are updated. It can be difficult to keep my messaging consistent & sometimes I’m a little more ‘conversational’ than I probably should be (which can add to confusion) - sorry about that.
I took some time to review your incomplete streets in Barcelona, and it looks like the main issue is that highway=track records are now included in OSM syncing. That conversation is in Should "highway=track" records exist in CityStrides? … it sounds like you disagree with that change. I encourage you and anyone reading along to add your perspective to that thread.
For reference, About the Node, Street, and City Data holds the info about what data is collected from OSM & it also links to the query I use for that.
There’s technically more going on here than just the code that I wrote to decide which streets to import. That code hasn’t been touched since September (though it is possible that it was updated between the time that Barcelona was originally created and when it was updated - if the update on Jan 18 was its only update).
The part that isn’t coming from CityStrides code is that OSM is constantly changing with user generated (read: sometimes garbage) content. This doesn’t seem to be the main cause of your particular complaint, but it is related - that street which name is someone’s email address. The fact that anyone can edit OSM means that someone can create/update/delete street data in bad ways (either accidentally or as Vandalism), and it’s possible that my update code will blindly accept that change into CityStrides. This is why Facebook puts so much time & effort into moderating their OSM imports.
This is pretty clearly not the case for your particular complaint, but it is important for me to point out because this forum is a source of information for a lot of people. Understanding the complexities & difficulties around using OpenStreetMap data can help others.
I, and I’m sure many others, are thankful that you took the time to make contributions to OSM. Your efforts helped improve CityStrides as well as OSM itself.
Unfortunately, this is a “forever problem” (I don’t know if there’s a word/phrase for this already) because OSM is constantly changing through other people’s contributions. The work to correct bad data will never end.
Besides this one change of allowing highway=track records into CityStrides, have there been other instances of bad data being created in Barcelona (or other cities you run)?
I don’t recall making changes to this code in ways that I thought would cause issues like this - so if you/others have seen other drastic “moving the goal post” changes, please let me know so I can have a better sense of where I need to be more careful/thoughtful.
Addition: The fact that Accés Terminal B exists in CityStrides is very odd to me. It was last edited by you 7 months ago (before the Jan 18 update) to include foot=no, which my code ignores & yet it’s still in CityStrides … I’m looking into this.