Latitude must no be less -90

[Former Member]

Dear community,

due to social media load meanwhile I got error messages for some search terms.

Response from odata service is

Latitude must no be less than -90 or greater than 90

for interaction contacts.

I assume this has something to do with the geocode fields in contact records.

Is there a way to get rid of those exceptions?

Thanks.

Timo

[Former Member]

Dear community,

in my case the problem was somewhere in SAP Data Services pre configured SAP content - as a workaround I just switched the values for longitude and latitude in the python script in the last step of loading data to system.

Cheers

Timo

[former_member183196]

Hi Timo,

Great..incase of issues with pre-delivered content in SAP Data Services(rapid data load package), please open a ticket for the following component.  SV-RDS-EIM.

Thanks

-Bharath

[nicolae_ciumac]

Hi,

is the social media load sending any geocodes at all?

Could you exemplarily paste a request-payload that failed with such a response?

What release are you on?

Regards,

Nico

[Former Member]

Hi Nico,

here you can find a sample request - Hybris Marketing Release ist 1508 SP02; should be same as 1602?!?

    {

      "City" : "Toluca, M\u00e9xico",

      "TwitterId" : "***",

      "Timestamp" : "/Date(1473258888000)/",

      "Facets" : [

        {

          "Id" : "***",

          "IdOrigin" : "TW"

        }

      ],

      "Longitude" : "19.2925000000",

      "ImageURI" : "http://pbs.twimg.com/profile_images/***.jpg",

      "CountryDescription" : "Mexico",

      "Latitude" : "-99.6569000000",

      "FullName" : "***",

      "Id" : "***",

      "GenderDescription" : ""

    },

Thank you.

Timo

[nicolae_ciumac]

Well, Timo - "it's obvious, Watson!" as Sherlock would say

in your payload you have "Latitude" : "-99.6569000000" which is not a valid value and that's exactly the error message you get. either it can be corrected or you can omit both Longitude and Latitude.

btw - we now have SAP Hybris Marketing 1.2 1608 as most actual release - so you're one year behind. I'd strongly recommend to upgrade.

Regards,

Nico

PS: there are major improvements, incl. conceptual differences after 1508 - so "No", 1508 is not the same at all as >=1602. Again, please upgrade.

[Former Member]

Hi Nico,

yes sure it is obvious.

But what's strange, if you check geo data of Toluca, Mexico it is

Latitude: 19.2878600°
Longitude: -99.6532400°

So actually only the values are interchanged. But - we are using rapid deployment solution or better rapid data load delivered by SAP.

So I don't know where this mix comes from. Might be a mapping or pre-delivered content.

Indeed you are right - we recently upgraded to 1508 SP02 and had some trouble with that, therefore we are not that courageous to upgrade again in that short time.

And last question - yes 1508 is not 1602 , but I saw that with SP02 we got some features similar to 1602 , so therefore I thought the SP02 closed a gap?!?

Thanks again.

Timo

[nicolae_ciumac]

We try to close gaps with every new release, so you surely did close some gaps.

In 1602 a major change was introduced for Data Management (and later, some more stuff from following releases got downported too), in the way we treat Contacts & Interactions.

The upgrade process has also improved and should now be much smoother.

Regards,

Nico

[Former Member]

Just to add - I was mistaken

We have 1511 SP02 , but I see your points