Talk:Lansing, Michigan
There is extensive GIS data available from Eaton County's website (including address points for the entire county): http://data-ecgis.opendata.arcgis.com/datasets/address-points?geometry=-84.657%2C42.688%2C-84.596%2C42.699
Based on my reading of the license, I'm not sure if we can use this data in OSM. Mostly it's free to use, but on the condition that "Any Derivative Work created by the Licensee shall bear the following notice:'Reproduced with permission granted by the County of Eaton, Michigan'. Some information has been provided subject to a non-exclusive, limited, and revocable license granted by the County of Eaton, Michigan." Davenport651 (talk)
CATA Route Relations and Overall Organization (Copy from Talk:Michigan)
Looking over the CATA route relations, I see some inconsistencies and improvements that I plan to work on. I plan to go through the route relations and match their names with the ones provided at the CATA master system map (eff. Aug. 2024) to provide a source of consistency. Current inconsistencies primarily include variations in style of name, (compare "Bus 1 - Downtown Lansing - Meridian Mall - Westbound", "CAMPUS CRUISR SOUTH & WEST CIRCLE-SOUTHBOUND"). I suggest the use of the name included on the master map, matching as closely as possible to the name on the map (not including reference/route number or direction, as that information should be encoded with separate tags) (e.g. "Downtown Lansing - Meridian Mall", "North & South Neighborhoods"). Other names (such as those listed on the schedules page, if different) can be added with alt_name=* on the relation, once again, without route number or direction in the name. (e.g. ref=33, name=North & South Neighborhoods, alt_name=Campus Cruiser South & West Circle;Union - S. Neighborhood). See here for reasoning behind proposed naming convention. If descriptive names are desired, I would suggest using description=*. Discussion about naming is highly encouraged.
More importantly than the aesthetic changes are the functional changes that should be made. I propose that we begin migrating the CATA network (including stops, routes, super relations) to current Public Transportation standards as described at Public transport and Buses. This should involve including bus stop nodes in the route relations in the order described at Buses and giving them the role of platform. It should also involve cleaning up the bus stop nodes already present by putting the stop number in the ref tag (rather than the name tag) and the route number(s) in the route_ref tag (optional if included in route relations). Stops can then be given names according to the name shown when entering the stop number on the [and departures] page with stop number in the ref tag (e.g. ref=1720, name=WBD Gr. River past Maplewood D, route_ref=1).
This isn't really complete, but I will leave it here for now so it can be discussed. --Aenet (talk) 09:26, 3 December 2024 (UTC)
I'm planning to begin working on the bus stops to start adding them to the route relations shortly. For any stops that have their stop number as a name=*, I will be moving the stop number to ref=*. I may start setting the stop names to those shown on CATA's Stops & Departures/Schedules pages for the stops. I will wait to change the name for the route relations until I have at least some agreement/discussion from fellow mappers, as my suggest does not match the value format shown on Tag:route=bus or Public transport. --Aenet (talk) 16:30, 3 December 2024 (UTC)
For routes that are not loops (have sections labeled as outbound and inbound by CATA) that currently have only one relation, I am going to create separate relations for the inbound and outbound section. I will reuse the old relation as the outbound section (assuming that to=* and from=* match that of the outbound section), creating new relations for the inbound section and a super relation for the entire route. I will keep the names for these as they are with a suffix of either " - Inbound" or " - Outbound" and the same name will be used on the super relation. --Aenet (talk) 16:46, 3 December 2024 (UTC)
See here for continued updates
https://wiki.openstreetmap.org/wiki/Talk:Michigan#CATA_Route_Relations_and_Overall_Organization --Aenet (talk) 15:51, 4 December 2024 (UTC)