IndoorManager tilesetId configuration
I’ve asked this question direct to a team member but thought I’d ask here too as it might benefit the community.
I am using azure-maps-indoor v0.2.3 and azure-maps-control v3.2.1 to attempt to render a tileset using manifest 2.0. The IndoorManagerOptions has a tilesetId and this is how I have traditionally applied a tileset to the IndoorManager (v0.1.x). The Azure map samples I am seeing now do not use this at all, and instead use mapConfiguration, domain and styleAPIVersion properties of the Map object instead.
Does this mean my original setup will not work and therefore requires me to add a pipeline step to create a MapConfiguration for my tileset?
Additional Info:
I should note that my pipeline is created using a global maps account and I still ingest data using the deprecated (but still available) data upload api, and then the conversion, dataset, tileset and routeset make use of Creator openapi spec 2023-03-01-preview (as this is a manifest 2.0 package).
I am still using a global maps account as my infrastructure uses Crossplane over Terraform providers and the azurerm provider does not support setting the required maps account properties for a data registry appropriate setup. Of course there is an issue with Terraform for this and living in hope that it is resolved prior to the maps account data plane data api deletion deadline.
I’ve asked this question direct to a team member but thought I’d ask here too as it might benefit the community. I am using azure-maps-indoor v0.2.3 and azure-maps-control v3.2.1 to attempt to render a tileset using manifest 2.0. The IndoorManagerOptions has a tilesetId and this is how I have traditionally applied a tileset to the IndoorManager (v0.1.x). The Azure map samples I am seeing now do not use this at all, and instead use mapConfiguration, domain and styleAPIVersion properties of the Map object instead. Does this mean my original setup will not work and therefore requires me to add a pipeline step to create a MapConfiguration for my tileset? Additional Info:I should note that my pipeline is created using a global maps account and I still ingest data using the deprecated (but still available) data upload api, and then the conversion, dataset, tileset and routeset make use of Creator openapi spec 2023-03-01-preview (as this is a manifest 2.0 package). I am still using a global maps account as my infrastructure uses Crossplane over Terraform providers and the azurerm provider does not support setting the required maps account properties for a data registry appropriate setup. Of course there is an issue with Terraform for this and living in hope that it is resolved prior to the maps account data plane data api deletion deadline. Read More