Missing optional fields on Place

[oliverbarnes]

The OSDM spec has the following fields which we haven't implemented yet.

They're optional, but we want to be as thorough as possible as these might be useful for different API consumers.

(I'm going ahead and linking to the 3.5 version that's been undrafted but with no official announcement yet - regarding these fields at least, there doesn't seem to be any changes)

code	
string or null
id of the address

countryName	
string or null
Country of the address.

countryCode	
string (CountryCode)
ISO country code (2 alpha), relative URNs with base urn:iso:std:iso:3166 are recommended

postCode	
string or null
Postal code of the address.

city	
string or null
City name

topographicPlaceName	
string or null
TopographicPlace name of the address. If set it should at least contain the city name.

street	
string or null
Street name of the address. Can also contain the house number.

houseNumber	
string or null
House number of the address. House number can either be in this separate field, or can be contained in the street field.

[marcoow]

I can't really see how having any of this in an OSDM API makes sense tbh… I think if we need this indeed, we'd have to integrate Google places API or so to get all the additional metadata when the basic station data is imported. Also of course we'd need to return localized responses. It's possible of course – I'm just surprised all of this is part of OSDM?

[oliverbarnes]

I don't know yet (why) :) But Andrea did say things are only added to the spec if there's a clear agreed-upon business case for them.

I agree some or most of the fields aren't supported by the current data set, we've been discussing them piecemeal. Nothing decided on our end yet.