Unique Identifier for Alerts?

  • 3
  • Question
  • Updated 1 year ago
Hi everyone,

Its my first day working with the Wunderground API and so far, so good. I do have a question though...

I noticed that the Alert result object does not contain a unique identifier and that is making it difficult for me to determine if the data I am pulling down is a brand new Alert, or an update to an Alert that I have seen already. What I would like to avoid is duplicating the same alert over and over in my local database, and normally I would use a unique identifier in the returned JSON/XML to determine if the alert was one I had seen before.

Is there a unique ID that I am missing? If not, does anyone have a suggestion for how I can determine if a downloaded Alert object is one I have already seen?
Photo of marcbertone

marcbertone

  • 2 Posts
  • 1 Reply Like

Posted 5 years ago

  • 3
Photo of WunderWilliam

WunderWilliam

  • 7 Posts
  • 1 Reply Like
The alert system doesn't currently have a unique ID for each one, but I will let the API team know that such a feature would be appreciated.
Photo of marcbertone

marcbertone

  • 2 Posts
  • 1 Reply Like
That would be great - thank you. In the meantime I will work on creating my own unique key based on the properties returned in the alert. Its not perfect, but hopefully I can get close enough to avoid generating lots of duplicate entries in my local DB.
Photo of Chip Cox

Chip Cox

  • 2 Posts
  • 1 Reply Like
I noticed this was 3 years ago.  I still don't see a unique identifier that I recognize as such in the alert API.  Was another method developed?
Photo of Brandon

Brandon

  • 29 Posts
  • 7 Reply Likes
Could the <date_epoch>1475319300</date_epoch> be used as a unique identifier? That should be different every time.