Spectrum Spatial (SSA/LIM)

Scenario:

Users create a large polygon or use an existing polygon from say the Kerbside Waste Collection Service days, then use the 'Map Information' tool to fetch the owners and address info from the underlying properties from a databind and it fails if the selection is too great!

Is there plans to increase the Databind limit, at this stage in our v12.1 SSA it appears very low. While I appreciate you can run a Query using the same polygon it will not obviously return the databind attributes.

The only work around I can see is having a separate 'spatial' layer that has names and address info etc?

Thoughts?

Hi Tony, currently number of records in data bind is combination of number of features SSA application retrieves (default configuration 100) and number of records spectrum platform feature service retrieves (default configuration 1000)

Both properties can be configured, please see the screenshots

• SSA: maxNumberOfFeatures , configurable via shared.properties

• Spectrum Manager: Feature service count

Thanks,

Rahul Mahajan

Thanks for your reply Rahul,

I have increased both of the limits that you have suggested. In the meantime I have also come across mention of the Data bind maximum records that can be fetched on page 8 of the V12.1 Release Notes where it says the limit is 999 records, and I believe this is the exact issue I am having with our data bind selections max'ing out.

Is there plans to increase the 999 limit?

Regards,

Tony Jordan

Hi Tony

It is not possible to configure the maximum data bind results beyond 1000 at the moment

There is a default limit of 1000 applied to feature results in Spectrum itself. Whilst this can be increased in Spatial Manager (choose at the top “Service” – “Feature Service” – “Maximum Features”) SSA is hard coded to limit the result to 1000.

As you know there is also a limit imposed by the map information results, which defaults to 100, but can be increased up to 1000 using the “maxNumberOfFeatures” setting in customerconfigurations\analystcontroller.properties

We typically keep this setting below 1000 as it can affect performance of showing map information if a user zooms out and clicks a map with many layers enabled.

We can consider increasing the limit as a feature request, but it may be a better option to allow data bind results to be launched or exported from a query result.

Below is an alternative suggestion, which is perhaps more elegant, as a feature request for the product.

You would (1) draw a polygon (or pick a region from map and add as annotation) then (2) you would query the base spatial table (such as addresses) to see the tabular results. In the overflow menu of the tabular results we would (3) add the links to see or to export a data bind result for data binds associated with that table. This could support up to 10,000 or more rows potentially. Exporting the data bind may be sufficient (and is easier to implement) rather than showing the results as another table within the SSA UI.

Let me know if this seems a better option and I can write up a user story for the team to take in a future release.

Hey Mustafa,

Thanks for looking further into this, as this selection ability is very important for many of our users.

The ultimate is that we can as you said, 'create a polygon and select databind records within'.?

In the interim, I have implemented adding our Property Rating Information as a nightly refreshed layer/table, then a polygon can query the required Name and Postal Address results from this. In fact, I have just tested selecting all 10,500 properties within our district which took 4 seconds to return the info! Fast!!

Please though, add the ability to return this many records from a databind, as the solution I have come up with I believe is a 'work-around' which requires extra layer/tables to be included in the map setup just to achieve this selection process.

Regards,

Tony

Hi Tony,

If your adding / refreshing a static layer, if you have SQL Server, it may be easier to simply set the layer up as DB layer, then you just need to update the layer using a scheduled SQL job in the database.

And then again another way to do this is to have the Layer actually point at a SQL view looking at the data source via SQL Query. That way the data is always up to date, I am using this for some of the layers in SSA and it works ok. Views give you great flexibility with your data as you can simply show any amount of reduced data sets from original data sources, (views are just queries after all)

There is a gotcha with this though as SSA cannot jump to the object in the map when you click on the results of a query against the layer... There is a fix in the works for this though with PB Engineering.

Hope this helps

cheers