[Imports] Proposed Import Process for Import of GTFS Data for STL Operator

[Arthur Dolmajian]

You are right, it is route relations with only nodes, I will update the
wiki so it is more clear. I figured it would be too risky to try and
automate adding the ways as well, especially around junctions. Plus. there
is the issue of certain ways not being split at every possible intersection
which would've also caused problems. Myself, and a couple of other
volunteers will add them in manually once I do this import. The script also
generates all the routes as LineString GeoJSON that can be used as
background/reference layer in JOSM for adding the ways.

Knowing the network, I'm fairly certain there are no telescopic
itineraries, just 2 different directions for each route that might have
variations with 1 or 2 stop differences, but I will double check.

The stops are placed on either side of the road as they appear in the GTFS
dataset. I've attached a screenshot of what tags they get. Later, while
adding the ways, I plan to add stop_position nodes directly on the road, at
the start and end of each route.

[image: image.png]
[image: image.png]

On Sat, 9 Feb 2019 at 22:59, Jo <winfixit at gmail.com> wrote:

> Hi Arthur,
>
> Looks good to me. Let me know when you imported a few, then I'll make a
> screencast video how to add the ways for those itineraries. I presume this
> import results in route relations with only nodes in them? What I'm not
> sure of, is whether it' s enough to only add the routes with the most stops
> in them.
>
> What I would do is add the longest variations of 'telescopic' itineraries,
> but also the ones that deviate in other ways. But that can be done at a
> later stage as well.
>
> It' s not clear to me what tags the stops get and whether you place them
> next to the roads, one on each side, or on the highways themselves.
>
>
> Polyglot
>
> On Sat, Feb 9, 2019 at 7:26 PM Arthur Dolmajian <
> arthur.dolmajian at gmail.com> wrote:
>
>> Dear OSM community,
>>
>> I would like to propose an import of GTFS data for STL
>> <https://www.stl.laval.qc.ca/> operator. All necessary steps have been
>> followed. I have documented the process at this wiki page
>> <https://wiki.openstreetmap.org/wiki/Proposed_Import_of_STL_GTFS>. I
>> have also created a separate import account.
>> Please review and advise.
>>
>> Link to wiki:
>> https://wiki.openstreetmap.org/wiki/Proposed_Import_of_STL_GTFS
>>
>> Best regards,
>> Arthur
>>
>> --
>> *Arthur Dolmajian, M.Eng.*
>> Email: arthur.dolmajian at gmail.com <http://arthur.dolmajiangmail.com>
>> Website: arthurdolmajian.com
>> _______________________________________________
>> Imports mailing list
>> Imports at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/imports
>>
>

-- 
*Arthur Dolmajian, M.Eng.*
Email: arthur.dolmajian at gmail.com <http://arthur.dolmajiangmail.com>
Mobile: +374 94 544493
Website: arthurdolmajian.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20190210/716be035/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 22915 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20190210/716be035/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 23547 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20190210/716be035/attachment-0003.png>