Bug between VisualArq template and coordinate system Heron

Hi everyone

I use a lot the Heron plugin to export GIS data and recently I started using Visual Arq. When trying to use the script to export to GIS all of a “sudden” the Heron plugin wasn’t understanding the swiss coordinate system anymore (so it was exporting in the world coordinate system), so I was always getting the data in GIS somewhere very far away where it should be.

After exploring a bit, I’ve found out that, if I open a Rhino file with the “Architectural meters” template and copy the whole data that and export things again, then the plugin all work fine with the custom (swiss) coordinate system.

Have any of you experienced something like this? Any idea why the template would influence it?

PS: I had the issue once with Rhino without using the Visual Arq template when a colleague changed the cplane (if I’m not mistaken). And then even when changing the cplane back to “world” the Heron plugin wouldn’t work with the custom coordinate system anymore. Maybe it has something to do with that?

Hi @natasha.catunda ,
Is the EarthAnchorPoint set in the VisualArq template? If the EAP is set in the Rhino file, Heron will attempt to export the geometery relative to this location, even if it’s 0 Lat 0 Lon. If the EAP is not set (likely the case in the Architectural Meters template), Heron will not attempt to transform the geometry on export.

If you are modeling your geometry assuming the Rhino origin is the Swiss coordinate system origin (LV95), before exporting, you could use the SetEAP component to the LV95 origin to get the results I think you are expecting.

My preferred approach is to model closer to the Rhino origin and use SetEAP to set the Earth Anchor Point to a known reference Lat/Lon near the site, but either way should work.

If neither approach works, can you post a problematic file?

-Brian

1 Like

Hi Brian

I’m not sure what exactly the template does… but it must do something in that direction. That does sounds like the issue and your answer like the solution.

In terms of your preferred solution, that would solve another issue we have also, which would always be to keep sending things close to rhino origin and then back to their "place to export with reference to the Swiss coordinate system origin.

So thank you! I’ll have a look and come back here to let you know if it worked :slight_smile:

And since I’m here I just wanted to say: thank you very much for the plugin :blush:

1 Like

So, I’m trying things a little slow cause I need to align with the projects. But here is my test:

Using the VA template and using the set Earth Anchor Point with Rhino origin worked to put things on the right location! Just for some reason the rhino origin has a random height of around 27m? This is making the buildings come on the right spot but with wrong Z value (which right now is easily to solve but annoying that this was there).

I did right now a little test by opening clean states Rhinos with and without the VA template and both should have the z value = 0. So that must be an issue with my file. I do not know where that came from, but maybe good for other people to know to check that as well before exporting. :slight_smile:

Again, thank you, @Brian_Washburn for you help! That solved the issue!