Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

'Project Map Data to Cross Section' tool fails #19

Open
sekbennett opened this issue Apr 7, 2022 · 7 comments
Open

'Project Map Data to Cross Section' tool fails #19

sekbennett opened this issue Apr 7, 2022 · 7 comments

Comments

@sekbennett
Copy link

Long time listener, first time caller.

I'm making my first ever attempt at creating 3 geologic cross sections using the GeMS toolbox. I'm running Pro v2.9.2 and GeMS toolbox v2.7.0. I'm trying to run the 'Project Map Data to Cross Section' tool and cannot get it to run without failing. The line for each of my 3 cross sections are in their own, independent line feature class (e.g. 'CrossSection_A', 'CrossSection_B', CrossSection_C') and I'm attempting to use only 1 at a time in the 'Section line' parameter. See below for screen grabs of my input parameters and the resultant error message.

I first tried project 3 Feature Classes (ContactsAndFaults, Geologic Lines, and OrientationPoints) and received the error message several times. I tried again, only projecting ContactsAndFaults, but received the same error message.

One thing worth noting: my GeMS-style gdb does NOT have empty Feature Datasets for each of my 3 cross sections. I assume this is not an issue, since the info pop-out for the 'Output name token' parameter says that if the cross section Feature Dataset does not exist, it will be created.

Any help getting the tool to work to create 3 cross section Feature Datasets would be very much appreciated. I'd hate to have to revert my gdb to ArcMap and use the ArcMap GeMS tools....or even worse, revert to constructing my cross sections in Illustrator.

Cheers,
Scott

Bennett x section input parameters

Bennett x section error message
@rhaugerud
Copy link
Contributor

rhaugerud commented Apr 7, 2022 via email

@ethoms-usgs
Copy link
Collaborator

ethoms-usgs commented Apr 7, 2022 via email •
edited
Loading

@sekbennett
Copy link
Author

Thanks, guys. I just shared a link to a copy of the gdb, which I put up on OneDrive. Let me know if you have any issue accessing it.

@sekbennett
Copy link
Author

Hi guys....I was hoping to construct 3 cross section in ArcGIS Pro this week using this nifty tool. Do you think it's best to hang tight and wait for a solution in the next day or so from you and your team, or do you suggest I revert to the ArcMap version of the GeMS toolbox and use an older version of the tool? I guess it depends on whether you suspect the problem I'm having is due to an issue with my gdb or if it's an issue with the tool itself (and how long it might take to debug the tool). I appreciate your time with this and value any time estimate you might be able to provide.

Cheers,
Scott

@ethoms-usgs
Copy link
Collaborator

Hard to say, it is my top priority right now and I can devote most of the next few days to it, but it probably won't be ready this week. Might be best to try the ArcMap version or my standalone cross section toolbox (https://github.com/ethoms-usgs/Cross-Section).

I was able to fix the initial problem you described but the tool then failed further along. It would run to completion with no errors but the output feature classes were empty. I am also re-writing a few sections to hopefully be more efficient.

@sekbennett
Copy link
Author

Ok...thanks for the update, Evan. And thanks for your hard work on fixing this!

@ethoms-usgs
Copy link
Collaborator

I posted a version of the tool to a branch at the repo recently:
https://github.com/usgs/gems-tools-pro/tree/xs-update
Download the toolbox from there and try it out. I am gathering documentation suggestions (and bugs) before merging it with the main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ethoms-usgs @sekbennett @rhaugerud