Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Wizards
Contributor II
Contributor II

Geo-Operations in SaaS environment

I am having problems applying this operation dissolve in the SaaS environment .

To my knowledge the autogenerated script from geoanalytic can be migrated to geo-Operations in SaaS environment.

After several steps followed from script conversion 

I am still unable to migrate my script syntax.

@Patric_Nordstrom 

 

 

2 Solutions

Accepted Solutions
Jonas_Karlsson
Employee
Employee

This will load the data correct:

Load * Extension GeoOperations.ScriptEval ('Load() DATASOURCE NiscodeArea CSV url="https://dl.dropbox.com/s/ehw7aghq8a7k5fm/NiscodeArea.csv?dl=1", fieldSeparator="COMMA", keyField="Niscode", geometryField="RefgemG10.Area",geometryType="POLYGON", stringQuotes="DOUBLEQUOTE"');

View solution in original post

Jonas_Karlsson
Employee
Employee

// Faking BasisRegio since it wasnt included in the dataload *, left(Niscode,1) as BasisRegio;
Basis:
Load * Extension GeoOperations.ScriptEval('
load()
DATASOURCE dis CSV
url="https://dl.dropbox.com/s/ehw7aghq8a7k5fm/NiscodeArea.csv?dl=0",
fieldSeparator="COMMA",
keyField="Niscode",
stringQuotes="DOUBLEQUOTE"
');Load * Extension GeoOperations.ScriptEval('
Dissolve(dissolveField="BasisRegio", resolution="auto", areaDatasetKeyField="Niscode", dissolveDataset="DissolveDef")
DATASOURCE DissolveDef INTABLE keyField="Niscode"
DATASOURCE NiscodeArea CSV
url="https://dl.dropbox.com/s/ehw7aghq8a7k5fm/NiscodeArea.csv?dl=0",
fieldSeparator="COMMA",
keyField="Niscode" ,
geometryField="RefgemG10.Area" ,
geometryType="POLYGON",
stringQuotes="DOUBLEQUOTE"
', Basis);

View solution in original post

13 Replies
Wizards
Contributor II
Contributor II
Author

Just to add and be specific. I uploaded the autogenerated script from Geoanalytics and my trial script to be used for SaaS environment which gives an error. 

 

Patric_Nordstrom
Employee
Employee

The problem here is that GeoOperations can only use one internal table, it's a limitation of SSE.

See here for a workaround for placing one of the tables in a csv file. This is for closest but works in the same way for dissolve.

https://community.qlik.com/t5/Qlik-GeoAnalytics-Discussions/GeoOperations-use-CLOSEST-with-two-loade...

Thanks,

Patric

Wizards
Contributor II
Contributor II
Author

Thank you for the responds @Patric_Nordstrom 

I followed the steps as for the example provided. Using this script

Load * Extension GeoOperations.ScriptEval('
Dissolve(dissolveField="BasisRegio", resolution="auto", areaDatasetKeyField="Niscode", dissolveDataset="DissolveDef")
DATASOURCE DissolveDef INTABLE keyField="Niscode", namedAreaField="BasisRegio"
DATASOURCE NiscodeArea CSV
   url="https://www.dropbox.com/s/l43doha3qziij5j/NiscodeArea.csv?dl=0",
    fieldSeparator="TAB",
    keyField="Niscode" ,
    geometryField="RefgemG10.Area" ,
    geometryType="POLYGON"
', Basis);

I get an error saying unknown geometry field

Patric_Nordstrom
Employee
Employee

The dropbox link needs to be direct file access

 url="https://dl.dropbox.com...

Wizards
Contributor II
Contributor II
Author

Thanks for the heads up. Unfortunately its still giving the same error (Unknown geometry field in CSV, RefgemG10.Area') after giving a direct acces to the Dropbox.

Load * Extension GeoOperations.ScriptEval('
Dissolve(dissolveField="BasisRegio", resolution="auto", areaDatasetKeyField="Niscode", dissolveDataset="DissolveDef")
DATASOURCE DissolveDef INTABLE keyField="Niscode", namedAreaField="BasisRegio"
DATASOURCE NiscodeArea CSV
url="https://dl.dropbox.com/s/ehw7aghq8a7k5fm/NiscodeArea.csv?dl=0",
fieldSeparator="TAB",
keyField="Niscode" ,
geometryField="RefgemG10.Area" ,
geometryType="POLYGON"
', Basis);

 

Jonas_Karlsson
Employee
Employee

Hi,

Try to use ...?dl=1
instead of ...?dl=0
in the Dropbox link.

Cheers

/Jonas

Wizards
Contributor II
Contributor II
Author

Hi @Jonas_Karlsson 

I tried both as well earlier on how to get direct-link to files in Dropbox.

same error 

Jonas_Karlsson
Employee
Employee

Maybe

fieldSeparator="COMMA",

Use TAB

 

/J

Wizards
Contributor II
Contributor II
Author

hi @Jonas_Karlsson 

That too was done but I return this error

Screenshot 2020-10-23 140615.png

 

Sample Table.png