A tool to help with this kind of integration is being developed as a Google
Summer of Code project. It's in early stages and focused on GTFS feeds, but
we can look into doing this for lists of stops with approximate coordinates
as well.
Polyglot
Op di 5 jun. 2018 om 08:59 schreef Stefan de Konink
Hi, Stefan, two steps required. The second is a lot easier than the first.
1) curate a database of exiting nodes. Choosing a unique key usually isn't
difficult, especially if you are using GTFS data (stop_id is a good
choice). Cross-check against routes already mapped.
2) write a proposal. You mig
Have you taken a look at this project?
https://github.com/CUTR-at-USF/gtfs-osm-sync
On Tue, Jun 5, 2018, 6:36 AM Johnparis, wrote:
> Hi, Stefan, two steps required. The second is a lot easier than the first.
>
> 1) curate a database of exiting nodes. Choosing a unique key usually isn't
> difficu
Yes. It has some useful ideas that can be adapted for the GSOC project
mentioned by Jo. It doesn't really have any application to this edit,
however.
On Tue, Jun 5, 2018 at 1:00 PM, James wrote:
> Have you taken a look at this project? https://github.com/
> CUTR-at-USF/gtfs-osm-sync
>
> On Tue,
I wasn't familiar with IFOPT, but one of its fellow travelers, Reflex, is
associated with the "ref:FR:STIF" code in my proposal.
Thanks for this.
On Tue, Jun 5, 2018 at 12:41 PM, Stefan de Konink wrote:
> On dinsdag 5 juni 2018 12:33:12 CEST, Johnparis wrote:
>
>> Hi, Stefan, two steps required
Hello,
Some people have already said to use Osmand+ but I would like to point out
a not-so-evident feature that may be of your interest: you can configure
the maps as to display Overlay POIs, which means that they will appear
highlighted and can be clicked on them to get all their tags. Usually, y
6 matches
Mail list logo
