Paths, surfaces, crossings, access, etc.

Paths, surfaces, crossings, access, etc.

Paths, surfaces, access, etc.

Bike lanes and paths.

Path access tags for consistency and routing

The Lancaster Station node had been moced away deim the building itself anf snapped onto the Lititz Pike roadway. So I moved it back.

17th's protected bike lanes are under construction. They will probably need to be remapped as separate geometry later once aerial imagery updates.

Added missing City bike route relation members. Some blocks are missing signs you kind of have to read between the signs, so to speak. Wayfinding is poor. St Paul has the new type of wayfinding signs and used to have green Bike Route signs, so I added it.

New roundabouts, and some missing City bike route relation members.

I added Providence, alleys, Edgewood, and Lake to the City's bike route network. They lack traditional bike route signage but have new wayfinding signs with destinations and distance.

Added a missing block of the City's local signed bike route.

Path types based on width, surface, and general use.

These paths are not designated for particular access and are not named. Only the path near White Barn Lane is wide enough to implicitly allow bikes. Also, disconnected the neighborhood Maple Shade Estates from transportation features.

Created a bike route relations for the Forks Township Trail System which is meant to connect the Two Rivers Trailway-Forks paths with the Forks Township Rec Trail. All three should exist as separate bike route relations for accurate and nuanced tagging.

Retagged the new escarpment trail (it is def not a boardwalk), disconnected/unsnapped Lafayette College grounds from roadways (please don't do this), and made the KSAT paths' tags consistent and accurate.

Created the A. Jerome Walnut Nature Trail route relation.

Since the Two Rivers Trailway connects several municipalities, I think it's better suited as a regional cycle network but the documentation about this is sparse. RCN allows it to render on bike maps at higher zoom levels/altitude, which is helpful.

The paths known collectively as Forks Township Trails are not designated for any particular use and so are better tagged as highway=path without access tags. lcn=yes is better used for local route relations and not individual pathways.

Ditto previous changeset: 22nd had incorrect oneway:bicycle tags. I added =yes to the entire bikeable stretch, updated bike lane types, and corrected some left/right errors. Also removed old bike lanes from S 21st.

Spruce between 22nd and 15th was tagged oneway:bicycle=no, which was incorrectly showing that bikes could go eastbound on Spruce. I added oneway:bicycle=yes to both Spruce and Pine.