SQL Spatial Data Rendered to Map Chart

[Tony Borelli 2]

I have ARCGIS spatial data in a SQL Server database view. It contains columns:

OBJECTID (int),

SHAPE (varbinary(max)),

XMin (float),

YMin (float),

XMax (float),

YMax (float),

XCenter (float),

YCenter (float)

After creating the Information Link, I noticed that the SHAPE column is not rendering. Spotfire is reading it as a Blob Data Type andthe Properties are blank in the Data Folder before adding the columns to the Information Link. Is there a way to get Spotfire to recognize this spatial data, so that I do not have to add the Property Name =ContentType and Value = application/x-wkb as well as Propert Name = Mapchart.ColumnTypeId and Value =Geometry to the Properties in the Column Element within the DATA folder before adding it to the Information Link

Also, I have to add Property Name = Mapchart.ColumnTypeId for all the X and Y fields with their corresponding values (XMin,YMin,XMax,YMax,XCenter,YCenter).

[Kirsten Smith (she/her)]

Here is the Community article on setting up an Information Link to bring in SQL map data:

 

https://community.spotfire.com/wiki/using-sql-server-spatial-data-spotfire

[Tony Borelli 2]

Arnaud Varin answered in the comments at the link provided. Thank you KirstenS for the quick response. I had been looking for that solution for over a week and noticed he posted his answer last Wednesday.

[Tony Borelli 2]

An additional problem remains after implementing the solution previously discussed. I can not show the labels on the feature map, and have to manually fill in the values below for each column Name.

Data >> Column Properties >> Mapchart.ColumnTypeId

I have to do this for XMin, YMin, XMax, YMax, XCenter, and YCenter.

[Kirsten Smith (she/her)]

Correct, you must have all six values in place in order to have labels displayed.

[Tony Borelli 2]

Is there a quicker way to accomplish this

[Kirsten Smith (she/her)]

In your Information Link under 'Column Properties' you can set the necessary Property values and link it to the data coming from SQL so that the fields are populated when you bring in your data.

[Tony Borelli 2]

The comment on the previous page recommends bringing the data in via

 

Connect to >> microsoft SQL Server >> New Connection

 

This works better as it requires less administrative maintenance on my side. To my knowledge, I do not have an option as you discssed above.