The check for comparing the spatial references is failing (alias was always an empty string) so no geometry projection


(see discussion @ http://esriosmeditor.codeplex.com/discussions/432089) - A user should be able to set the output projection in the download tool itself instead of workflows where users must reproject the OSM dataset after loading.

How-to: If you change the GP environment of the tool or the model in which the tool is executing then the tool should respect that. The environment parameter is called “output coordinates”. It will save you the reprojection later on and all the tools downstream will just automagically pick up the spatial reference.

This was broken at version 2.1 and should be fixed in the next release.