Latest Contributions by CharlieFrye

Glad it worked ... View more

I missed that you mentioned Cascade - am double checking before confirming about not being supported. ... View more

It looks like (thanks for the image) you've done this step correctly.  Unfortunately not all types of storymaps can be embedded (and some older storymaps do not support embedding. That said, you should have been given a more useful message. What type of story map are you embedding the map series into?  The newest builder app, or one of the other templates? ... View more

Here is a short geoprocessing workflow (for ArcGIS Pro or ArcMap): 1. Use Identity tool to assign the Block Group IDs to each voter point.  2. Use Summary Statistics tool to summarize voter points by Block Group ID to get the sum of voters - you may want to select a subset of voters by party or another attribute first, e.g., select republicans and do a summary, then select democrats and do a summary, and so on. You may also need to Add a short integer field to the Voters feature class and Calculate it to have a value of 1. The idea is to produce a summary where you get the sum (count of voter points) within each block group by voter category.   3. Use the Join Field tool to join the result of each summary to the block group polygons - now the voter counts in the same attribute table as the total population and other demographic cohorts for each block group. 4. Query for block groups with voter counts (by category) that exceed desired proportions of demographic variables, e.g., (!Democrats_SUM!/!TotalPop_CY!) > 0.5 This can all be saved and automated as a geoprocessing model and run as needed on different elections or different geographic areas.  Depending on how the voter points have been assigned their location in space, i.e., randomly within a voting precinct, or by geocoding the voter's address, it may be moderately to severely unethical to randomly assign demographic characteristics to those points.  These are two independently compiled datasets. From this data there is no way to know how many democrats are actually over the age of 55, are male or female, or earn over 50,000 per year.   Instead, one can say is of 59 block groups, 36 have a majority of democrats, and 23 a majority of republicans.  Of the 36 democratic block groups, 28 have a median household income of greater than $80,000 per year, and 22 have a median age over 55. To quickly come up with relevant statements like that, first find the total percentages of relevant demographics for the entire area.  Then see if the voter categories contain strong deviations from those percentages.  ... View more

We've had sporadic issues with that server, though it is generally up.  We have had intermittent issues with that tool, and frequently need to restart instances of the server to get it to working. That said, there is also a limit on the number of features that can be be downloaded via the ExtractData tool, so use a small extent (something that would download only a few flowline features) to verify. The service should return a useful error message if the extent is too large, meaning too many features have been requested.    The feature counts limits are listed here:  http://www.arcgis.com/home/item.html?id=06f9e2f5f7ee4efcae283ea389bded15 send me an email if the tool seems to be down, and we will have a look.  (Ha! I didn't know I could put my email in a hyperlink here). Thanks ... View more

I don't know if anyone ever followed up, but here is the issue and how to get around it: Issue: If a raster's extent is beyond the extent of the Mosaic Dataset's coordinate system's extent, it will not be added, and produces the 999999 error. Workaround: The offending raster needs to have a coordinate system, and then run the Clip tool (Raster toolbox under Data Management) with the Maintain Clipping Extent option checked (it is not by default).  You will need to define the extent coordinates to be within the extent of the coordinate system.  For example if the raster's right maximum coordinate is 180.000543 and the coordinate system is WGS_1984, which has a limit of 180.0, then you'll need to enter 179.999999 (I tried 180 and it didn't work).  The result was the correct number of columns and rows with all the data. I asked Technical Support to log an enhancement to the Add Raster tool so it gives a useful error message. ... View more

I just verified this with the development team, and they reproduced it, and are logging a bug report.  I'll follow up when I've got more information.  In the meantime, my mind has blanked and it would be good to get back to learning what you originally needed, and let's see if we can get you that data via another means. Charlie ... View more

We spent time, yesterday, doing the same, and deduced that the only difference is in the Post request's header, and the refURL was the difference--the same refURL that was in the request to get the token must be used when supplying the token for another request. We proved it by using Fiddler's Composer tab to send the request using the header information used in the Python script, and that worked. The browser sends a request where the header contains a different refURL. So, effectively, we eliminated the REST API as the cause.  Now we are looking that the FeatureSet.Load() method, which we have found works when using a service that does not require authentication, but does not work when authentication is required (it used to work). ... View more

We verified there is no bug in the URL--though it's a little confusing because the browser uses a different refURL in it's header, and that's why pasting the URL into the browser fails.  I was able to use Fiddler's Composer, where I could specify the header to match the code, and that works. The real problem looks to be in the FeatureSet.load() method, and I'll need to check on that next. ... View more

Hi Greg, I am able to reproduce what you've described. I recalled that when I was originally writing this script, it was important not to set the referer to an actual URL, and than any string, like "arcgis" would instead work. That no longer seems to be the case, I'll need to investigate that.  On your questions: * Could there be a specific issue with the service retruning JSON results? Charlie did you request JSON when it worked?  I've always used JSON for this, though I've tried HTML to see what it looks like (not so parse-able), and so it's rather strange that it allowed the sequence you found.  The reason it works is that once the token is entered in step 3, the browser has cached it. * Do I need to do more to make the request URL safe?  I'm not sure, as I'm not a web programmer ant not familiar with the concept. * Does the same page handle token requests from all *.esri.com domains?  Should I be requesting the token from a different ESRI REST GenerateToken page if there are more than one?  No, each ArcGIS Server can be configured to authenticate, and when so the portal, e.g., www.arcgis.com is entered into the server's configuration. Charlie ... View more

I just double checked, both the USA_Roads and USA Wetlands services are working properly. That can be tested by using a URL like: http://landscape1.arcgis.com/arcgis/rest/services/USA_Wetlands/MapServer/0/5 where the last digit is the ObjectID of a feature, which will return the attributes of that feature. it looks like you may have an issue in your code, where "0/query" is at the end of your service variable, and also in your query variable. ... View more

We got this fixed.  Sorry for the delay and inconvenience. ... View more

Replying to both questions: Actually the dynamic map services can work as feature services do; at least for these services.  Not all dynamic map services serve feature classes, which is why they are not general supported like feature services in the various ArcGIS client interfaces.  The invalid token message can occur if you get a token from one portal and try to use it for another.  This should not be a problem if your credentials are for a .arcgis.com organization account.  But, if your credentials are for a different portal, then the token will not be valid.  One way to test this is just run the code that generates the token, to get a new token, and substitute that into the URL pasted into the browser. That written, since it may be useful, I tried this by getting my own token, and got the same error.  So I went to the REST endpoint, which required that same token, and it worked.  It looks like there is a problem with the USA Roads service, none of the layers are showing in the REST end point.  I'll see what I can do. ... View more