Missing field 'propertyName' in ICP connection data API

  • 76 Views
  • Last post 17 May 2019
erichislop posted this 17 May 2019

SOAP call to xml electricityregistry

ICP connection data response

I'm currently doing some searches using the EMI APIs but have found that it doesn't return propertyName field like the SOAP request to the electricity registry.
I've converted the SOAP request to JSON for readability.

There are quite a few example of this where the address is the same but the only differentiator is 'propertyName'
With this issue there is no way to know which ICP is correct.

 

  • Liked by
  • msouness
Matthew Keir posted this 17 May 2019

Hi Eric

That’s correct, it’s not there. But that is not because it is missing - more a deliberate exclusion at the design stage. The fields released via the ICP connection data API on EMI were originally consulted on back in 2015.

https://www.ea.govt.nz/development/work-programme/consumer-choice-competition/retail-data/consultations/#c15378

The information in your example clearly shows it's useful to separate the two ICPs. There may be other ICPs where this field has been used to include other details where it is less obvious they should be released. In this case, the field is not really being used as a property name in an addressing sense. Poor labelling of fields can lead to the poor or inconsistent population of data within the registry. Perhaps this field would be better called the ICP ‘description’? 

The good news is that the Authority is currently consulting on releasing additional fields via the ICP connection data API.

https://www.emi.ea.govt.nz/Forum/thread/consultation-on-releasing-additional-registry-fields-through-the-icp-connection-data-api/.

It would be great if you can assist your organisation in their response to this consultation, including providing examples to make your case.

Cheers,

Matthew

Close