topic Re: Geo-Operations in SaaS environment in GeoAnalytics

Geo-Operations in SaaS environment

Wizards — Wed, 29 Jan 2025 15:35:54 GMT

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

Re: Geo-Operations in SaaS environment

Wizards — Wed, 21 Oct 2020 13:07:09 GMT

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.

Re: Geo-Operations in SaaS environment

Patric_Nordstrom — Thu, 22 Oct 2020 11:40:10 GMT

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-loaded-tables/m-p/1741009/highlight/true#M3295

Thanks,

Patric

Re: Geo-Operations in SaaS environment

Wizards — Fri, 23 Oct 2020 09:11:35 GMT

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

Re: Geo-Operations in SaaS environment

Patric_Nordstrom — Fri, 23 Oct 2020 09:18:21 GMT

The dropbox link needs to be direct file access

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

Re: Geo-Operations in SaaS environment

Wizards — Fri, 23 Oct 2020 11:07:53 GMT

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);

Re: Geo-Operations in SaaS environment

Jonas_Karlsson — Fri, 23 Oct 2020 11:15:08 GMT

Hi,

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

Cheers

/Jonas

Re: Geo-Operations in SaaS environment

Wizards — Fri, 23 Oct 2020 11:23:04 GMT

Hi @Jonas_Karlsson

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

same error

Re: Geo-Operations in SaaS environment

Jonas_Karlsson — Fri, 23 Oct 2020 13:20:21 GMT

Maybe

~~fieldSeparator="COMMA",~~

Use TAB

Re: Geo-Operations in SaaS environment

Wizards — Fri, 23 Oct 2020 12:10:52 GMT

hi @Jonas_Karlsson

That too was done but I return this error

Re: Geo-Operations in SaaS environment

Jonas_Karlsson — Fri, 23 Oct 2020 13:53:00 GMT

Add

stringQuotes="DOUBLEQUOTE"

Re: Geo-Operations in SaaS environment

Jonas_Karlsson — Fri, 23 Oct 2020 13:54:46 GMT

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"');

Re: Geo-Operations in SaaS environment

Jonas_Karlsson — Fri, 23 Oct 2020 14:03:49 GMT

// 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);

Re: Geo-Operations in SaaS environment

Wizards — Fri, 23 Oct 2020 14:47:27 GMT

Hi @Jonas_Karlsson

I start to see a green light, apparently the order in which the Dataset parameter are arranged plays a big role in the script run.

After arranging the parameters my script runs successfully.

I will check the results, then after If results are as expected, I will accept as solution.