Are there applications about GIS based on 3D Slicer?

iwangwangwang · September 15, 2023, 9:28am

Are there applications about GIS based on 3D SLICER?

Can 3D SLICER be used to develop GIS applications?

muratmaga · September 15, 2023, 5:53pm

I am not aware of any.

I also don’t think Slicer is the right choice for GIS. Most GIS data is inherently 2D (lat/long). Even if you did manage to do something, you would have to code all the functionality yourself (e.g., different types of map projections).

There is already a very mature open-source GIS platform called GRASS. is there a reason you are not exploring that?

lassoan · September 16, 2023, 7:32pm

There are some geo/mining applications, but mostly analysis of drilling cores and not geography mapping.

VTK - the library that Slicer is based on - contains lots of GIS features, including lots of projections, dynamic forward/inverse computations, texture mapping, etc. that would be all readily usable in Slicer. Still, due to the lack of experience of the Slicer community in this field and most of the funding focusing on clinical and biomedical applications you might find you need to develop some essential features on your own (or get funding for it).

You might want to ask @Davide_Punzo, who developed SlicerAstro - an edition of 3D Slicer for astronomy applications - about his experiences in using Slicer outside its main application area.

Davide_Punzo · September 16, 2023, 11:02pm

The view factory can be used to fully customize the 2D slice view (e.g having lat-long coordinate axis, etc…) and the controller widgets (the buttons).

You can have a look at the code available in the astrovolume module in SlicerAstro extension (see below for links).

In my astronomical use case (HI 3D data cubes), each dataset was covering little portion of the sky. So I have applied coordinate transformation (in my case celestial wcs transformations) only for the calculation of 2d axis and for the data prode (i.e getting the lat-long at the ijk coordinate)

However, if the data extend on large range of lat and long you would need to apply the transforms also to the data (you could create a vtkTrasformSomething, if your non-linear transformation is not implemented in vtk/Slicer).

This is all doable, but you need to implement this in C++ and having some knowledge of Slicer infrastructure which is not super documented.

See

github.com

Punzo/SlicerAstro/blob/master/AstroVolume/qSlicerAstroVolumeLayoutSliceViewFactory.cxx

/*==============================================================================

  Copyright (c) Kapteyn Astronomical Institute
  University of Groningen, Groningen, Netherlands. All Rights Reserved.

  See COPYRIGHT.txt
  or http://www.slicer.org/copyright/copyright.txt for details.

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.

  This file was originally developed by Davide Punzo, Kapteyn Astronomical Institute,
  and was supported through the European Research Council grant nr. 291531.

==============================================================================*/

// SlicerQt includes

This file has been truncated. show original

github.com

Punzo/SlicerAstro/blob/master/AstroVolume/qSlicerAstroVolumeModule.cxx#L402


      
          /*qMRMLLayoutSliceViewFactory* mrmlSliceViewFactory =
            qobject_cast<qMRMLLayoutSliceViewFactory*>(
            d->app->layoutManager()->mrmlViewFactory("vtkMRMLSliceNode"));*/
          
          qSlicerAstroVolumeLayoutSliceViewFactory* astroSliceViewFactory =
            new qSlicerAstroVolumeLayoutSliceViewFactory(d->app->layoutManager());
          
          //d->app->layoutManager()->unregisterViewFactory(mrmlSliceViewFactory);
          // TO DO: this should be disabled, but SlicerAstro with the last Slicer version (16/02/2021)
          // crash if the default slice view factory is disabled
          d->app->layoutManager()->registerViewFactory(astroSliceViewFactory);
          
          // Modify orietation in default Layouts
          vtkMRMLLayoutNode* layoutNode =  vtkMRMLLayoutNode::SafeDownCast(
            this->mrmlScene()->GetSingletonNode("vtkMRMLLayoutNode","vtkMRMLLayoutNode"));
          if(!layoutNode)
            {
            qCritical() << "qSlicerAstroVolumeModule::setup() : layoutNode not found!";
            return;
            }

There were actually some issues with the factory with recent Slicer version (not sure if they are still an issue), but unfortunately I never had the time to investigate/fix it.

Cheers,
Davide.

iwangwangwang · September 17, 2023, 6:48am

I see, thank you very much

Topic		Replies	Views
Are there any non medical development and application cases here? Development	3	192	September 12, 2023
Using 3D Slicer as library/ Framework in Paraview based application Development	1	424	October 4, 2021
Using `vtkStructuredGrid` in Slicer Development	5	512	December 2, 2021
Question on 3D rendering in Slicer Support	6	99	September 27, 2024
Guidance on Creating a Simplified Python-Based Version of 3D Slicer with Custom Modules Development	2	42	October 25, 2024

Are there applications about GIS based on 3D Slicer?

Related topics