This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 45%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EUV%3C/text%3E%3C/svg%3E)
I am trying to create a sample Indoor Maps. I have used the file provided in the documentation of the Microsoft. https://github.com/Azure-Samples/am-creator-indoor-data-examples/tree/master/Drawing%20Package%202.0
I am able to upload the file and generate the operationId. After that I am trying to convert the file. Then it was throwing the error as below. Please provide a solution or working file to try the indoor maps. Please let me know if any configuration needs to be updated.
{
"operationId": "",
"created": "",
"status": "Failed",
"error": {
"code": "dwgConversionProblem",
"details": [
{
"code": "failed",
"details": [
{
"code": "manifestError",
"message": "The manifest provided in the DWG zip package has an invalid version."
}
]
}
]
},
"properties": {}
}
An Azure service that provides geospatial APIs to add maps, spatial analytics, and mobility solutions to apps.
Hi @Uppalapati Vinay Kumar Thank you for posting the question here. Just wanted to check if you have used the correct uuid for the conversion request and used the dwgPackageVersion=2.0 in the POST request. The documentation Convert a drawing package provides the steps needed for the POST request to achieve the conversion. Here is the request for your reference.
https://us.atlas.microsoft.com/conversions?subscription-key={Your-Azure-Maps-Subscription-key}&api-version=2023-03-01-preview&udid={udid}&inputType=DWG&dwgPackageVersion=2.0
Kindly go through the documentation and validate if you are missing any steps along the way and let us know if you still encounter any issues.
Hi @LeelaRajeshSayana-MSFT , Yes, I have added the version as well. It shows the manfest.json error in the conversion status
{
"operationId": "",
"created": "",
"status": "Failed",
"error": {
"code": "dwgConversionProblem",
"details": [
{
"code": "failed",
"details": [
{
"code": "manifestError",
"message": "manifest.json has an invalid 'version'."
}
]
}
]
},
"properties": {}
}
In manifest.json also version 2.0 is mentioned
{ "version": "2.0", "buildingLevels": { "dwgLayers": [ "GROS$" ]}}
According to this doc: https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/azure-maps/drawing-requirements.md#manifest-file-requirements-1 you need to also include featureClasses in your mainifest. I suspect that the error is meant to be something like "file content is not aligned with version requirements".
Yes, feature classes also mentioned in manifest. The Zip file contains Ground.dwg, Level_2.dwg and manifest.json.
"version": "2.0",
"buildingLevels": {
"dwgLayers": [
"GROS$"
],
"levels": [
{
"filename": "Ground.dwg",
"levelName": "level 1",
"ordinal": 0
},
{
"filename": "Level_2.dwg",
"levelName": "level 2",
"ordinal": 1
}
]
},
"georeference": {
"lat": 47.63529901,
"lon": -122.13355885,
"angle": 0
},
"featureClasses": [
{
"featureClassName": "room",
"dwgLayers": [
"RM$"
],
"featureClassProperties": [
{
"featureClassPropertyName": "name",
"dwgLayers": [
"A-IDEN-NUMR-EXST"
]
},
{
"featureClassPropertyName": "roomType",
"dwgLayers": [
"A-IDEN-NAME-EXST"
]
}
]
},
{
"featureClassName": "wall",
"dwgLayers": [
"A-WALL-EXST",
"A-WALL-CORE-EXST",
"A-GLAZ-SILL-EXST",
"A-GLAZ-SHEL-SILL-EXST",
"A-GLAZ-SHEL-EXST",
"A-GLAZ-EXST"
]
},
{
"featureClassName": "workspace",
"dwgLayers": [
"A-BOMA"
]
},
{
"featureClassName": "workspaceFurniture",
"dwgLayers": [
"A-FURN-SYTM-EXST"
]
},
{
"featureClassName": "buildingFurniture",
"dwgLayers": [
"A-FURN-FREE-EXST"
]
}
],
"facilityName": "Contoso Building"
}
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Hi @Uppalapati Vinay Kumar I am just following up to see if this is still an ongoing issue. If you find a resolution to this, kindly share it here so that other community members running into this issue can find a solution. Thank you.
Hi @LeelaRajeshSayana-MSFT @rbrundritt Still the issue is same. Not resolved. Please let me know if anyone has working file or solution to develop an indoor map with the DWG file. Please let me know.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 77%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYZ%3C/text%3E%3C/svg%3E)
Hey @Uppalapati Vinay Kumar , Could you share your request URL that you were using to create this conversion request? I was able to successfully create conversion on the package you referred to in the GitHub repo.
https://us.atlas.microsoft.com/conversions?api-version=1.0&udid=&outputOntology=facility-2.0. I have used this URL. But the New Updates of azure maps documentation provided the tool for conversion https://azure.github.io/azure-maps-creator-onboarding-tool/ Using this tool I am able to convert the file and use on the maps.
For DWG CAD File conversion, we can use the tool https://azure.github.io/azure-maps-creator-onboarding-tool/ provided in the updated Azure Maps documentation. It will be uploaded, converted and creates the dataset. Provides the MapConfigurationId with that we can add in the map.