Indego Import

The Indego Import is an import of the Indego GBFS data, which contains the names and coordinates of Indego bikeshare stations in Philadelphia, Pennsylvania. The import is currently (as of 2019-08-10) at the planning stage.

As of 2019-09-18, there are 23 bikeshares mapped within Philadelphia, and 133 bikeshares in the GBFS data. This import would add 110 bikeshare stations, and add additional data to the 23 stations already mapped.

Goals

• Add missing Indego bikeshares
• Add tags to existing bikeshares, such as name and ref.
• Identify new, moved, or closed bikeshares and update OSM accordingly.

Schedule

This is a small import. Two weeks?

Import Data

Station coordinates, names, reference numbers (station_id), and addresses.

Background

Data source site: https://gbfs.bcycle.com/bcycle_indego/gbfs.json
Link to permission (if required): https://www.openstreetmap.org/user/jcoscia/diary/390466

OSM Data Files

Nothing yet.

Import Type

One-time import of a large number of stations, followed by periodic edits for new, moved, or closed stations.

There's not that much data, so using JOSM manually should work.

Data Preparation

Data Reduction & Simplification

Add tags to existing Indego bikeshares instead of creating new ones. This is a manual import, so this should be easy.

Tagging Plans

Tags using GBFS data

See: https://gbfs.bcycle.com/bcycle_indego/station_information.json

Key:addr=address

(addresses will be parsed manually and the appropriate addr tags will be used)

Key:name=name

Key:ref=station_id

Note: excluding "bcycle_indego" from station_id may or may not be useful, need feedback

Other tags

Tag:amenity=bicycle_rental

Key:network=Indego

Key:operator=Indego

Key:fee=yes

Changeset Tags

import=yes

Key:comment=Indego Import of bikeshare stations in Philadelphia.

Key:imagery_used=Mapbox Satellite

Note: the account "Indego_GBFS_Import" may be used for the import.

Data Transformation

Manually input each station into JOSM, following the tagging plans above, and the workflow below.

Data Transformation Results

Nothing yet.

Data Merge Workflow

Team Approach

Solo.

Workflow

Steps:

1. Using JOSM, go to coordinates in GBFS file.
2. Check for existing Indego bikeshare; if one exists, don't create a new node.
3. Add/copy data from the GBFS file to the node.
4. Verify that the coordinates are correct, and that all tags are entered properly.
5. Move to next station in GBFS file.

There aren't that many bikeshares, so one changeset may be okay. Need additional feedback on this.

If a revert is needed, I could use JOSM's reverter plugin to do so.

Conflation

If tags do not exist on an existing Indego station, and exist in the GBFS data, add tags. If tags do exist, and they conflict, verify in-person before changing those tags. Tags that are identical in meaning may be overwritten. Ex. overwrite operator=IndegoBikeshare with operator=Indego. If an existing station's location is significantly different than in the GBFS data, verify in-person.

QA

From my personal experience with the Indego application, their data is accurate and up-to-date. If it may be inaccurate, (Ex. can't see bikeshare from aerial imagery) I'm willing to confirm it in-person.

See also

The email to the Imports mailing list was sent on 2019-08-10 and can be found in the archives of the mailing list at [1]

I have reached out to the GeoPhilly group using Meetup on 2019-08-10. There is no response just yet.