Latest Contributions by RobertStevens

Thank you Dan Those urls describe what appears to be a very rich python API -- far richer than the ESRI description of ArcPy. There are many, many classes. Is that a third party API on githib (or similar)? Perhaps I have not dug deep enought into ESRI documenatation. ... View more

Hi Neil No, I am using desktop, just on a local machine. The basemap that ships with Business Analyst displays a map of the whole world, so I suppose that is why it uses Web Mercator. But an important, perhaps the most important, feature of BA is that it intended for use by non-GIS professionals (like myself), and hence people who don't know all the subtleties of projections etc. There is some history here. BA 10.0 used to use a special projection named, not surprisingly, "Business Analyst Projection". This projection was described as dynamic. By that was meant that the details of the projection changed according to the latitude and longitude of the area of interest, and the bounding rectangle. (Perhaps some guru from ESRI could comment). It seems that what you are telling me is this. That Web Mercator is essentially never used as a projection of small areas, distant from the equator. And that, regardless of the projection used in the basemap as shipped, that it implied that the user would choose a different projection, better adapted to his geographic area of interest. Im my case I suppose that would likely be "NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601", and that to use Web Mercator Auxiliary Sphere would give a terribly distorted map. But why doesn't a product like BA make this more explicit for the business user? Another thing I have never understood about ArcMap is that, if the frame and the dataset use coordinated base of different geographic datums, it asks the user for the appropriate transformation to use. Why?? Surely the software itself is best equipped to answer that question. How am I, the ignorant business user, supposed to know what the answer to that question is? Thx for your continuing help. Rob Stevens ... View more

And another thing about this blessed Online World Geocode service is that one of the fields it returns is named city. This causes one of my fields, also named city, to be renamed as city_1. I DONT WANT THIS. Why the hell does it mess with my field names instead of changing its own? Or using a name less likely to cause a conflict like that? ... View more

Hi Dan Yes. Not the specific error about the Willamette River, but the original error for which I posted a workaround. ESRI inform me that they are aware of a number of problems concerning the 2015 data update, although they did not get  info specifics. Rob ... View more

Please see my solution to this problem at https://community.esri.com/thread/174980 Sorry. I should have posted it here, but I lost track of my original post. However, there is yet more bad news. In using the data at a scale of 1:10K I also find that there is no feature for the Willamette River in the basemap data. I doubt that many of you care about that specifically; but where there is one error, there are likely several, so my conclusion about this 2015 basemap, both raw data and layers, is that they are likely rife with errors. Rob Stevens ... View more

Ty Dan Yes. I think the problem has been that I have been running geocoding and with the geocoder set to save results in a geographic coordinate system (WGS 84). Whenever I use data created that way, any tool I use which honors the application environment setting is going to create data items based on geographic coordinates. I still do not understand the results I get. If, in my example case, you divide the Shape_Area by the Shape_length  you get a value for r/2, the radius of the feature divided by two. Doing that, I get r=0.016863 in some units. I am using a radius of 1 mile, so there appear to be about 59.3 miles in one of these mystery units. That does not correspond to anything I know, even approximately. Anyway, thx for help. Rob Stevens ... View more

You say: "I really hope this helps". I'll say it does! Matthew, you are the man. That is exactly what is happening. I am getting some number which is in degrees squared, or something very like. What an absurd unit, even if the map does have a geographic coordinate system. Not even steradians based on the earth's radius. Oh well. Good. Now I just have to figure out how to change this default in the workspace environment. I guess something like this will always happen if one draws a geometric figure about a point that was geocoded into a latitude and longitude using the default value in the environment which says for output coordinate system, which says: "same as input". Ty Matthew. Rob ... View more

Ty for responses Neil and Dan. Dan, are you saying that if I created new features (I am not BTW), that those new features would change the coordinate system of the underlying dataset? Ie: I have features with GCS WGS 84 coordinates. I have a map with world mercator projection. I create a new feature, and the coordinates are stored in meters in the original dataset? So I have umpteen features stored as a pair of angles, and one feature stored with a pair of huge numbers? Or is it rather that the new feature will cause all the values in the original dataset to be converted to meters, and the coordinate system description will become Web Mercator (which I wouldn't want since I had a reason for having the original dataset in CGS WGS 84) ... View more

I will answer my own question. In Arcmap the list of geocoding services comes from, potentially, 3 places: The map itself (stored internal to the .mxd) The system configuration file: C:/Program Files/ArcGIS/version/Locators/DefaultLocator.xml The per-user config file: C:/Users/user/AppData/Roaming/ESRI/version/Locators/DefaultLocator.xml All three are consulted by Arcmap, but, obviously, the first is not available to ArcCatalog. Hence the difference. There should still be an API to query and change the list of geolocators stored in the map. ... View more