You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :-)
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:
@harry-gibson What behaviour would you expect here?
The text was updated successfully, but these errors were encountered: