In the OpenTransitTools transit loader for Pelias, there are intersections and landmarks (and also another loader that pulls fare vendors from a web service custom to TriMet). In the future, having a generic .csv loader would probably be a better way to load such data. Thinking the official Pelias transit loader is probably best to just load data elements defined by the GTFS spec (i.e., today that is just stops.txt ... in the future, maybe they'll be other transit elements defined in GTFS that should get into Pelias, etc...)
In the OpenTransitTools transit loader for Pelias, there are intersections and landmarks (and also another loader that pulls fare vendors from a web service custom to TriMet). In the future, having a generic .csv loader would probably be a better way to load such data. Thinking the official Pelias transit loader is probably best to just load data elements defined by the GTFS spec (i.e., today that is just stops.txt ... in the future, maybe they'll be other transit elements defined in GTFS that should get into Pelias, etc...)