Latest Contributions by RDCOGIS

https://developers.arcgis.com/python/latest/api-reference/arcgis.features.toc.html#arcgis.features.FeatureLayer.query return_all_records Optional boolean. When True, the query operation will call the service until all records that satisfy the where_clause are returned. Note: result_offset and result_record_count will be ignored if return_all_records is True. Also, if return_count_only, return_ids_only, or return_extent_only are True, this parameter will be ignored. If this parameter is set to False but no other limit is specified, the default is True.   sounds like a hierarchy of booleans, but the last line is confusing too,... so if no other limits are set it sets it back to True?..... I've used the .query and not set any of these and it return all records, even past the REST's MaxRecordCount another great advantage is the .save on the returned Feature Set to go right to Shapefile (not using the 'as_df=True') fl = FeatureLayer(_itemUrl) features = fl.query(where='Shape is not NULL') features.save(save_location=_pathShps, out_name=_friendlyName + '.shp') ... View more

curious,....now that you are filtering out the bad geometry, can you go back to the .save method, without pandas .sdf fl = FeatureLayer(_itemUrl) features = fl.query(where='Shape is not NULL', out_sr=26911) # save to disk print('saving the Feature Layer to Shapefile') features.save(save_location=_pathShps, out_name=_friendlyName + '.shp')   ... View more

nothing like being 6 years late to the conversation, but I just discovered the easiest way to grab data from a REST end-point, with query option, and save as Shapefile from arcgis.features import FeatureLayer # query the FeatureLayer to produce a FeatureSet print('querying the Feature Layer') fl = FeatureLayer(_itemUrl) features = fl.query(where='Shape is not NULL', out_sr=26911) # save to disk print('saving the Feature Layer to Shapefile') features.save(save_location=_pathShps, out_name=_friendlyName + '.shp')     ... View more

Is there an actual solution for this, not just Sure do! ? ... View more

Thanks for the response, I completely agree with your workflow, but something else is going on here. I have some gremlins in the system, figure this out...... I have an old cached service running for years, originally created from an mxd with the 'Layers' map frame. I completely delete the service. I recreate the service, in Pro (map name is not 'Layers'), I can make the service any random name I want and everything works as expected (after caching a few scale levels). If I name the service the same as the original name, the new cache is completely unusable until I rename the subfolder back to 'Layers'. I first thought that maybe the import into Pro and rename from Layers to a proper name didn't take, but I tried again with a new map and same thing. There's something about the original service name that insists that the cache folder be named 'Layers'. Tough for anyone to recreate so I'm not holding out for an answer, but maybe someone ran into this too.....   ... View more

Hi,  I went though support for this and they've logged some bugs BUG-000158005 - The default print service in ArcGIS Online stretches the color values of the image service in the print output. BUG-000158006 - The default printing tools in ArcGIS Server stretch the color values of the image service in the print output. ... View more

Some further notes.... Setting the Custom Rendering Options in ArcPro resolved the issue for my local testing, but then I applied the same Option to my Server, using the arcgis user, but to no joy. Are there environment settings that can be set within the script to change the behavior?       ... View more

Hi Blake and others, I'm in the same boat. I recreated my ExportWebMap tasks using ArcPro and pagx files (NOT 3.x, server 10.8.1 won't be able to read them, learned that the hard way but that's another story) and the new tasks are returning Image Services with a Stretch Type.  I can see its applying the standard Percent Clip but not sure why its not just leaving it alone as I have it published, as the old task does. I tried setting the Image Service with Allow Raster Functions: false, but it did not help. btw - my reason for upgrading the tasks was so the new ExportWebMaps can print the new Vector Basemaps. Was really pleased until I tried my own imagery....   ... View more

Hi James, sure thing.  Here is what I modified. The call from main to build_email will look like this. The build_email will return all three address (recipient) types: for row in rows: address, address_cc, address_bcc, subject, body = build_email(row, lyr.properties.fields, message)   In build_email I retrieve the three address types from the config file and call a new _get_email_values function. recipients = _get_email_values(row, fields, settings['recipient']) recipients_cc = _get_email_values(row, fields, settings['recipient_cc']) recipients_bcc = _get_email_values(row, fields, settings['recipient_bcc']) .. .. .. return recipients, recipients_cc, recipients_bcc, email_subject, email_body I attached the _get_email_values as a txt. It is quite convoluted and can be simplified just to the top two lines if you wanted to (after .split(;)). The full function (aside from that it could be written better....) will either.... 1. return the address directly as in the config if it detects an '@' 2. get the address from the data if it detects that you used a field name 3. get the address from the data's domain if it detects that you used a field name and the field is a Domain Hope this makes sense, I found the _get_email_values a bit tough to read after leaving it for a few months.   Dave ... View more