Qlik Community

Qlik Associative Big Data Index Discussions

Ask a question or participate in a discussion about Qlik Associative Big Data Index here.

New Contributor III

etl macth value

Hi everyone, I'm trying to load latitude and long-term points from a geojson file, by calling rest, loads the values in a single field / column, one under the other, so they don't match and don't identify the geographic point on the map , it would be possible with some function to make them match, then create another field that in a table the value one would correspond to the value immediately below




Labels (1)
3 Replies
Honored Contributor III

Re: etl macth value

So you have one column with two rows and those two rows together form a geo point on a map? I don't see how this question has anything to do with Big Data, so maybe I am totally misunderstanding you.

Try these functions:

With peek() you can get the value of a row above the row you are in.


Combine it with the geomakepoint() function to turn it into a geo point to be used on a map.


Hope that helps. If not, please show us an example or try to use some more punctuation in your sentences so it is easier to understand what you are trying to say.

May you live in interesting times!
New Contributor III

Re: etl macth value

Thank you for the answer, you are right i mistaken the theme.

i have a table made like that:















in this i'm now that to every numerical that starts with 9 will be a latitude, and 45 that follows a longitude, wants to make them match for create a point subsequently, how follow:





9.47387289 , 45.389403

9.48939049, 45.8493039

9.48494903, 45.3834930

9.37494040, 45.4849393

thanks for the availability,

if you can tell me the area where it is appropriate to write this post, I am grateful,



Honored Contributor III

Re: etl macth value

I somehow doubt your actual source table looks like that as there seems to be no key relating the values. In other words: I don't see any way to recognize which number should go with which other number (except that a 9 does not go with a 9 and a 45 does not go with a 45).

At this point, I am starting to wonder if you could have solved this problem manually by now by just creating an inline table (or even just copy these values in some XLS file or something) and just use the geomakepoint() function to turn them into a geo point.


May you live in interesting times!