Website shows SPDX-identifier, but I can't find it in the spreadsheet.

[jbruechert]

I noticed the website now shows the spdx-identifier for some feeds, which is great progress!
However I could not figure out how to consume this information from the spreadsheet. Is there any column I have missed?

Slightly related, it would be interesting to know where this information is sourced from, as I could not find a corresponding field in the JSON schema either.

[davidgamez]

Hi @jbruechert,
The SPDX ID is not currently available in the CSV. As for the source of the information, there are two methods:

• Inferring the license ID(SPDX ID) from the URL. Core implementation here
• Manual assigned license(WIP). Our team reviews the license URLs, connects with the producer(if necessary), and sets the license.
  As this information is set up and generated in the API project, there is no current plan to add it to the JSON schema.

You can follow the progress of this work here
An important note is that we design the licenses so that we can have licenses not on the SPDX list. For good or for bad, there are many feeds with customs licenses, and we would like to model those licenses in the future as well. This is the main reason that we kept the license id outside the CSV. We are providing a license endpoint that returns the license information. This is in PROD but there is still a lot of work to be done.

Related to license information. I also noticed in transitous that you have matched some feeds with their corresponding license. At some point, we can also sync the feeds that you already identified into our system.

[jbruechert]

Thank you for the quick reply.

The background why I'm asking about this, is that downstream projects of Transitous rely on the SPDX-identifiers, and we currently have to set them manually for feeds from the Mobility Database, which is a bit of a disadvantage over Transitland Atlas.
For me it would be perfectly fine if not every feed has an SPDX-identifier, as we can easily fall back to passing through the url directly, but if would be helpful to at least get it from the CSV where it is known.

Of course I can try to replicate your fuzzy matching on the url in Transitous as well, but it seems like unnecessary duplication and a source of incorrect license information.