nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Level features aren't updating

Lwkrynock

I'm having an issue where the feature geometry for levels isn't updating when I use the Import Floorplans to Indoors Database GP tool to update floorplans in our Indoors model. If I run the tool and import the CAD floorplans to a new Indoors gdb, it works as expected. However, if I run the tool on our existing gdb, it only updates the units and details, but doesn't update the level features. The GP tool history reports that level features were updated, but the geometry doesn't change and editor tracking doesn't show any edits. Below are example screenshots - first is the one with the issue; second has correct geometry (new gdb).

I'm running ArcGIS Pro 3.4. Has anyone else experienced this or have any suggestions on what might be going wrong here?

Find more posts tagged with

Accepted answers

All comments

Lwkrynock

Thanks for this tip! Yes, I do recall getting out of sync with versions at one point and running that tool fixed things. I forget that it's there so this is a good reminder to try it when issues come up.

Lwkrynock

That's great news that the plans are importing correctly! Yes, hopefully Esri fixed that bug.

Oddly enough, I'm having the same problem with the new tool Import CAD to Indoors. Arcs are coming in as straight lines and the unit polygons aren't being built correctly. It's odd because it's only happening on some floors I've tested, not all. These are the same plans that imported fine using the deprecated tool.

As I mentioned, still in Pro 3.4 and am hesitant to update due to compatibility issues with some of the data we maintain and our current version of ArcGIS Enterprise. If I have time, I may do what you did and load 3.6 on my laptop and test there. Or, I may just wait a couple of months since we're planning a bigger upgrade this Spring.

Re. your initial reply, I'm happy to share experiences and maintenance processes with you. The process of getting our floorplans into Indoors went pretty smoothly for us and the main reason is that our CAD group has very solid standards in place and the floorplans are very clean and well maintained. Also, our groups work very closely which is always a good thing! I see you are in the higher ed Indoors group. Are you with a University? I'm at NC State.

Thanks for the help and insights!

Laurel

AaronKoelker

I find that anytime I run into an issue like this with Indoors data/tools, the most common solution is to run the Upgrade Indoors Database GP tool on the FGDB to validate it (domains, attribute rules, etc.) and ensure it matches whatever latest version of Pro/Indoors Information Model you are using.

It sounds like you got what you needed with the workaround of just deleting the existing Levels and letting it recreate them. But for others who come across this with the same issue, maybe try the Upgrade tool first.

JDenham

In a very odd turn of events, I ran an import on my laptop (v3.6.1) using the deprecated "Import Floorplans..." tool, and the arcs imported properly this time. This was with the same settings that I've been using all along. Over the last year I have been asking ESRI to please fix this arc problem, and I've tested & re-tested this with each new version since v3.4 was released, each time finding that arcs were still not importing right. Before today I had not tested v3.6.1 because ESRI had given the impression that a fix of this old tool was not planned.

After today's discovery, I even uninstalled v3.6.1 and downloaded/installed v3.6.0 (the latest version I had confirmed the bug existed in) and was surprised to see that arcs are importing there as well. I don't know if it's fair to suggest that ESRI quietly decided to find and fix this bug without documenting it anywhere, then roll it into the back versions for download, but I don't know how else to explain this. This was a customer support-confirmed bug that has been plaguing me for over a year.

Ultimately this allows me to finally update my office PC to the current version of Pro and keep using the deprecated tool until the new one matures a bit. Hopefully they will add the ability to assign custom ID fields. I think once that happens, I'll start transitioning to the new one. I suspect that it might handle updates better than the old tool. For now, I'm thrilled to run the newest version of Pro on my main PC again. 🙂

-Jeremy

JDenham

Hi Laurel,

I'm sorry to hear that this new tool will be negatively impacting you as well. We don't have as many CAD drawings as you do, but it also sounds like my workflow isn't as polished as yours either. I think I've said elsewhere on this forum that I wish I could see others' Indoors CAD maintenance processes to take notes. 🤔

-Jeremy

Lwkrynock

Thanks for the insight, Jeremy! I also ended up deleting the level features from the example I shared and re-running the GP tool.

However, with that tool being deprecated (which I'd heard about, but was trying to ignore!! 😂), you're right that we need to go ahead and start moving to using it. I did some testing with it today and it is quite different. It did update the level polygon feature - there is a a long description about how it handles updates on the tool reference page. As you mentioned it auto-assigns globalID-like values in the ID fields.

It's definitely going to take a lot of work and rethinking to switch tools. We have spent the past 1-2 years getting our CAD floorplans imported to Indoors (~1700) and we have developed several FME models to help with this process, updating floorplans, QAQC, etc. At least one of them will need to be rebuilt or done a different way because of switching tools. So, yeah...one step forward, two steps back I guess.

Laurel

JDenham

This is how it behaves for me as well. On the rare occasion that I need to update the Level features, I simply delete it before running the GP tool and allow the tool to re-create a new one. We don't store user data in the level features, so removing them and re-importing them is easy enough. I've never known why they don't get updated like the others. Sometimes it's hard to know if this was 'as designed' or simply an oversight.

As it happens, I'm still running ArcGIS Pro v3.3.7 because my CAD arcs (door swings and other details) have been importing as straight lines from v3.4-v3.6. ESRI support tells me that the "Import Floorplans to Indoors Geodatabase" tool is being deprecated, and the new tool is the "Import CAD to Indoors Dataset" tool. It uses an entirely new 'config' structure that now exists in a JSON file instead of an excel file. It also doesn't allow you to pre-populate custom Facility ID, Detail ID, Unit ID like the previous tool did, AND only allows one floor to be imported at a time. 😞

If the new tool is able to do what you need it to, it might be a good time to move over to it. We have lots of buildings to maintain, so we're currently trying to work through some of these issues (and a newly discovered bug) before we can start using the new tool. *I'm not sure how the new tool handles Level polygons though. If it also fails to update them during import, it will be evidence that perhaps it is by design.*

-Jeremy

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.