thinkwise-software-factory-maps-component

Create a calculated column producing CoordSets JSON, then add a map row pointing latitude_longitude_col_id at it, at least one map_base_layer with a tile URL template, and one map_data_mapping row per element of the data-mapping domain. Confirm scope, tile provider, and center/zoom with the user first.

CoordSets is a JSON envelope with a CoordSets array of coordinate rings, each point having Lon and Lat keys, for example { "CoordSets": [ [ { "Lon": "5.979388", "Lat": "52.208479" } ] ] }. Circles add a Radius key in meters. The map reads this from the column set in latitude_longitude_col_id.

Transposed Lon and Lat values in the CoordSets expression produce valid JSON with silently wrong positions, plotting points thousands of kilometers away. Verify the expression against a row whose real-world location you know, not just that the map renders a pin.

Verified testing showed map_data_mapping could not be created or edited through a metadata-driven staging API because its compound key spans two parents. Treat it as a manual step in the Software Factory UI unless your connector's domain metadata confirms otherwise.

No, tile layers only support long-lived tokens embedded in the URL such as query-string API keys. For bearer or OAuth2 tile sources, front them with a proxy web service. Outbound API calls via web_connection do support oauth and bearer_token authentication types.

You cannot — for marker geometric types the platform nulls and hides border_color, fill_color, width, and opacity fields. Style markers through the domain element's icon field instead. Color fields only apply to line, polygon, rectangle, and circle types using signed 32-bit ARGB values.