[Talk-us] Importing CobbLinc Public Transit Routes from Government Data
stevea
steveaOSM at softworkers.com
Thu Feb 9 22:39:18 UTC 2023
On Feb 9, 2023, at 7:15 AM, Sam wrote:
> Thanks, I don't really understand the lingo there or what any of this
> means, so I'll go ahead and retire this idea for now.
Try this: build from scratch the transport route you use every day. From scratch. As a start. Build out the rest of the transit network from there. Go at your own pace. There are nodes, ways, relations, route relations (for transit and others) made out of relations, the routers, renderers and use-cases that "consume" these data downstream....
Sounds like you are building up to transit relations (could be bus routes as v1 or v2?) but are not there yet, especially as it might feed into your app. There's a way to get there, I'm sure. You are in early to intermediate stages.
> There are more of them to review to make sure there are no duplicates
> and what not, so I wasn't going to do the bus stops, but would that make
> more sense to do instead? It would just take longer for me to go through
> them all by hand and there are still only a few of them on the map. I
> just really want my mapping app to be able to do my morning commute
> properly instead of telling me there are no buses in Cobb :( (though I'm
> not sure that bus stops are enough for this, but it's worth a shot).
Build things up manually from scratch as objects, one at a time, try them on for size, connect them, etc.
Learning about bus stops and adding them to bus routes is an awesome task. When you make or improve bus routes just right, they light up like neon flares on certain transportation renderers, for example. If they make your app work, hey, nice job, Sam. Your app / our map can bounce off of one another with you building things, cool. It doesn't always work like that, as we share this fabric. If you want to make a local project of however you see things, do so, it's your map, too. It should be a fairly short path between how you might tag a bus route relation in OSM and how it does or doesn't light up on your app. Something to watch.
Import scripts are like being handed a big machine gun and you pull the trigger. I say: shoot a few bullseyes, first.
Looks like Brian might have paved some road ahead for a license waiver into OSM. That does happen and is nice when it does (nothing like "explicit permission," I've got a few of those in OSM). I wouldn't say green lights ahead (yet) but it might be in your back pocket if / when you might be ready to enter these data in the future.
It's a great big plastic map, Sam. You and your app can build it yourself, one object (node, way, relation) at a time.
Have fun. Ask. Read wiki. There is community here. You are allowed to build very cool, detailed, exact, community-shared things here, like bus routes, cycle routes, train routes (they have to be "real"). Do yours, locally, light-it-up in your app, hey, that's an E-ticket ride. It's a win when the map improves!
More information about the Talk-us
mailing list