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.

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

In GeoProcessing tool, must create new output folder for each run #36

Open
andrewphilipsmith opened this issue Nov 17, 2016 · 1 comment

Comments

@andrewphilipsmith
Copy link
Contributor

andrewphilipsmith commented Nov 17, 2016

Steps to reproduce:
In the OSM2MapAction Runner toolbox, specify an output directory that already exists. The selected directory can be empty.

Expected behaviour:
The toolbox should except the output path if it is a valid OS path.

Actual behaviour
The toolbox only excepts the output path if it has been created within the toolbox's UI:
osm2mapaction_runner_tlbx_error

@harry-gibson What behaviour would you expect here?

@harry-gibson
Copy link
Contributor

This parameter is configured as an output parameter, so whether this shows up as an error or just a warning depends on the setting of "Overwrite results of geoprocessing operations" in the overall arcmap Geoprocessing Options dialog. If it's enabled, you just get a warning and can run.

This was deliberate, because the tool generates a substantial number of subdirectories below the selected output location, so the user will probably generally want to pay careful attention to the folder they choose and perhaps use a new empty one each time so that they have some hope of keeping track of the version of the shapefile set they are working with (assuming they re-run the tool after receiving a new .pbf and thus want to create a new set of shapefiles but may also want to keep the previous ones). At the very least this forces the user to be conscious of this when they choose the location.

That was my thinking anyway - open to persuasion :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants