Azure Map issue with the overall experience of the tutorial

DigitalDots-DevOps commented 1 year ago

Hi Azure maps team, we are using Azure maps for a while and we were very trilled about the new changes you have done as far as DWG flexibility and so on. So, we decided to migrate, but the experience has been negative. First, the conversion step has bunch of issues with the dwg itself. (I am using the provided sample from the repo, the new one). If you ignore the errors and continue the process the tileset eventually does not display on the map. We are using the https://github.com/Azure-Samples/AzureMapsCodeSamples/blob/main/Samples/Creator/Creator%20Custom%20Styling/Creator%20Custom%20Styling.html or https://github.com/Azure-Samples/AzureMapsCodeSamples/blob/main/Samples/Creator/Creator%20Indoor%20Maps/Creator%20Indoor%20Maps.html we would remove the
styleAPIVersion: '2022-09-01-preview', mapConfiguration: '9963aed3-2575-303a-b841-827c16bb09c5', portion that tis specific to the account and then we add the tilesetId. Nothing on the map. Again we are not new to Azure indoor Map. We have been using for 6m. I will challenge you to try to follow the steps and experience the tutorial itself. Working with the previous version was ok (with some hiccups again in the documentation, I had to contact the team to fix those) We need better and cleaner documentation and tutorial. This is not a cheap Azure offering for us to be left with so few samples and buggy onboarding docs. Resposne:

    "operationId": "7d182431-63fb-4d9f-a379-d88449c7626d",
    "created": "2023-07-23T04:52:40.1096208+00:00",
    "status": "Succeeded",
    "warning": {
        "code": "dwgConversionProblem",
        "details": [
            {
                "code": "warning",
                "details": [
                    {
                        "code": "geometryWarning",
                        "message": "Geometry is not valid. LINESTRING (-4.074586808681488 -14.112736344337463, -4.074586808681488 -14.112736344337463)",
                        "innererror": {
                            "levelOrdinal": 1,
                            "layerName": "A-FURN-FREE-EXST",
                            "geometry": "MULTIPOINT ((3.5710108 3.0856987), (3.5710108 3.0856987))",
                            "code": null,
                            "message": "Issue with entity or entities in this layer."
                        }
                    },
                    {
                        "code": "geometryWarning",
                        "message": "Geometry is not valid. LINESTRING (-4.020082890987396 -14.194307684898376, -4.020082890987396 -14.194307684898376)",
                        "innererror": {
                            "levelOrdinal": 1,
                            "layerName": "A-FURN-FREE-EXST",
                            "geometry": "MULTIPOINT ((3.5723728 3.083612), (3.5723728 3.083612))",
                            "code": null,
                            "message": "Issue with entity or entities in this layer."
                        }
                    },

And so on...

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: fa6d4f33-0311-2315-edef-b81c06fb3e0d
Version Independent ID: f7cc6c67-470f-e3f2-1a5c-d71487a85034
Content: Tutorial: Use Microsoft Azure Maps Creator to create indoor maps - Microsoft Azure Maps
Content Source: articles/azure-maps/tutorial-creator-indoor-maps.md
Service: azure-maps
GitHub Login: @brendansco
Microsoft Alias: Brendanc

SaibabaBalapur-MSFT commented 1 year ago

@DigitalDots-DevOps Thanks for your feedback! We will investigate and update as appropriate.

svet-tot commented 1 year ago

Soooo, I was messing around with this and it turns out that the previous approach of having the tilesetId into the html file is not valid anymore. You need to use the configurationId that is at the end of the tutorial. There is not a singe statement explaining that breaking change. So, now this must be done:


  domain: 'us.atlas.microsoft.com',
  styleAPIVersion: '2022-09-01-preview',
  mapConfiguration: 'a34f8478-df30-adeb-b788-dc6766f64e95',

instead of this

"tilesetId": "dfef42ea-fa18-1433-5b60-c604a8b3caad",

AshokPeddakotla-MSFT commented 1 year ago

@svet-tot Thanks for sharing the additional details. I have assigned the issue to the content author to evaluate and update as appropriate.

brendansco commented 1 year ago

Hi @svet-tot

The conversion warnings that are shown there are expected. We wanted to include an actual DWG file with realistic warnings that could show up. This shouldn't prevent any of the actual indoor map from showing up. We will update this to add a note somewhere calling this out so that users aren't thrown off by the warnings.

All of the documentation that is out there with Creator should be referencing MapConfigurationId or MapConfigurationAlias. Previous tilesets or tilesets created from drawing package 1.0 would still work with tilesetid. The assumption was that if a new customer or existing customer starts looking into drawing package 2.0, they would find the documentation that points to the use of MapConfigurationId. In this instance here, you were already familiar with using tilesetid and continued to use the same field. Could you share the document that you looked at to discover the new conversion updates or where it would have been helpful to call out this change?

MicrosoftDocs / azure-docs

Azure Map issue with the overall experience of the tutorial #112628

Document Details