This is for the 'xs-update' branch of the toolbox, as the Project Map Data to Cross Section tool in the master branch doesn't work for me.
I've found an issue that results in incorrect apparent dip calculations for certain OrientationPoint Type values. See the images below, where OrientationPoints with Type value of "bedding, top bed known from local features" are northeast dipping, but the PlotRotation field would have them incorrectly projected as southwest dipping on a WSW-ENE cross section projection. It looks like the issue is that the DipDirection is incorrectly calculated with the same value as the Azimuth, though these are planar measurements and the dip direction should be 90° clockwise from the azimuth. This then propagates to an erroneous ApparentInclination and an incorrect PlotRotation field.
I don't speak Python, but ChatGPT tells me that the planar measurement is being incorrectly classed as linear (thus DipDirection is set to equal Azimuth). It tells me that the filtering function that separates linear from planar measurements catches the "L" of "local" and incorrectly classes this measurement type as linear.
Perhaps a better linear/planar filtering would rely on the symbol code rather than the Type value.
Thank you,
Skyler Mavor
Montana Bureau of Mines and Geology
This is for the 'xs-update' branch of the toolbox, as the Project Map Data to Cross Section tool in the master branch doesn't work for me.
I've found an issue that results in incorrect apparent dip calculations for certain OrientationPoint Type values. See the images below, where OrientationPoints with Type value of "bedding, top bed known from local features" are northeast dipping, but the PlotRotation field would have them incorrectly projected as southwest dipping on a WSW-ENE cross section projection. It looks like the issue is that the DipDirection is incorrectly calculated with the same value as the Azimuth, though these are planar measurements and the dip direction should be 90° clockwise from the azimuth. This then propagates to an erroneous ApparentInclination and an incorrect PlotRotation field.
I don't speak Python, but ChatGPT tells me that the planar measurement is being incorrectly classed as linear (thus DipDirection is set to equal Azimuth). It tells me that the filtering function that separates linear from planar measurements catches the "L" of "local" and incorrectly classes this measurement type as linear.
Perhaps a better linear/planar filtering would rely on the symbol code rather than the Type value.
Thank you,
Skyler Mavor
Montana Bureau of Mines and Geology