Latest Contributions by danbecker

same issue here, saw the server task mgn reported 90%+ of memory was being used. Just ordered another 4GB of RAM. ... View more

Yes, geometry is important. The polygons represent fixed survey area "units" that are walk-able in a single day. The client (editors) will simply "drop" the survey area polys where they want us to survey. Field surveyors will load the same webmap in Collector and know exactly where to survey. It's a way of having the client definitively tell us where they want our surveyors to go. The only workarounds I can think of: 1. I did create a point symbol that draws at the correct dimensions and is automatically scaled according to the reference scale set in the data frame properties. While this works in ArcMap I highly doubt it would act the same in AGOL. 2. Create a web app. using the JS API, have the client use the web app to drop the survey polygons. Include the feat. service in an AGOL web map that the surveyors will use with Collector. As long as all the surveyors push/pull sync each morning before heading out they will be continually "updated" as to where surveys should take place. This should work, but quite a bit of hassling around for a very basic task. I'm open to other suggestions. ... View more

I have an existing polygon that has correct x/y dimensions. I would like other editors to simply select the polygon from the feature template and drop it onto the map in a location of their choosing. The catch, I want the editors to do so using ArcGIS Online. This would be simple in ArcGIS Desktop, but since there is not a "copy feature" tool in ArcGIS Online, I was trying to figure out a way to accomplish this using feature templates, which are supported in AGOL after publishing the .mxd to a feature service. ... View more

Here are instructions I wrote for myself a few months ago. A few of the steps regarding new feature class you can omit because you already have a "new feat class" which is your original SDE gdb. Rem. to add field, as specified in step 2. HOW TO MOVE FEATURE ATTACHMENTS FROM 1 GDB TO ANOTHER 1. create new geodatabase 2. create new feat. class in new geodatabase     -geometry has to be the same as the source feature class that has feat. attachments     -for fields, use the import button and specify source feature class     -add additional field name: alias_GID type: text, length: 150 3. enable attachments on new feature class 4. append source feature class to new feature class     -NO TEST     -add field source.GlobalID to target.alias_GID 5. create new field in new feature attachment table named "REL_alias_GID" type: text, length: 150 5. append source feature attachment table to new feature attachment table 7. field calculate new feature attachment table REL_alias_GID to [REL_GLOBALID] 8. join new feature class.alias_GID .. TO .. new feature attachment table.REL_alias_GID left table is new feature attachment table right table is new feature class 9. field calculate new feature attachment table REL_GLOBALID to new feature class.GLOBALID ... View more

see here: related tables and offline editing 1. We have our own on-premise server 10.3.1; not federated to AGOL or portal. 2. In ArcGIS online, when adding the token-secured feature service as an item, I usually select "store credentials with item". This eliminates an additional feature service prompt for credentials 3. Add the same item to a new webmap, save, share it 4. download the webmap for offline use in Collector 5. In offline mode, select a feature and attempt to access it's related records. You will get "no valid location" in the right-hand pane. The workaround is during step #2. DO NOT store credentials with the service item. Proceed with the remaining steps. You will now be able to access the related features. There were earlier bugs in Collector with credentials stored in service items, but they have since been fixed. This bug is related to the previous ones, but different as it only pertains to related records. From my testing it was introduced at version 10.3.4. We were using related records with stored service item credentials at Collector 10.3.3 and did not have this problem. ... View more

Here's the thread related to the storing credentials with AGOL service item: related tables and offline editing From what I've observed the above issue is only when related tables are used. I can't search for bug-000087792; support site appears to be down. We continued to receive "not a database file" error several times last night during attempts to download a webmap. Please PM and I will send logs; nothing looks out of the ordinary. ... View more

iPhone 6s / iOS 9 just reported a similar error, unable to download: map was not a database file. This time it was during an attempted webmap download for offline use. Server log level was set to "FINE", I did not see any errors in server log. I just set server to log level: "DEBUG". After the field crew member attempts another download tonight, I'll post the log if I see anything. Def. something going on with new 6s hardware. These 2 variants of "not a database file" are encountered during almost every sync and map download. This is not the case when working with older apple hardware. In all cases, the same webmap, feature services, AGOL items are used by all hardware; pretty much narrows it down to individual hardware or network/internet connections. Edit 11/10/2015: I stand corrected; I just received the same error when downloading the same webmap using an iPad2. unable to download: map was not a database file. Server 10.3.1, the feature service contains 2 relationship classes; Collector can edit related data. I got the same error 2 times during attempted downloads. 1. open map in online mode, if prompted to sign into the secured feature service do so. This is necessary because you CANNOT store feature service credentials in AGOL item. This causes an error when editing related records; this bug was introduced in version 10.3.4, someone correct me if I'm wrong. 2. Go back to the maps screen 3. attempt to download the webmap. If you get error unable to download: map was not a database file  attempt again. You will likely get the same error 4. Close Collector on the iPad, (double click home button, then swipe from bottom-to-top). 5. Re-launch Collector, you will likely be auto-signed in. Repeat steps 1-3. This time the webmap will successfully download. ... View more

to my knowledge, you Can use the 3D polyline feature service in Collector, but it will only capture 2D data. 3D data collection is not possible with the current release of Collector, which is 10.3.5. ... View more

Hey guys, any update on this from the dev team? will this be addressed in 10.3.6? thanks. ... View more

what you propose would kind of work, here are the problems I see: 1. the tablet in the truck would always have to be ON, and not go into standby mode 2. I assume its in the city, so the tablet would be best to have cellular data plan so you can reduce reliance on GPS signal which might be impacted inside the truck cab. This is all so that Collector can display current location, relative to your base map parcels 3. I assume you would setup a relationship class between parcel polygons and a new recycling table you create 4. There would not be an out-of the box way to simply touch a parcel poly in Collector and populate a related record in your recycle table. 5. You would have to touch [select] parcel poly, scroll down on details screen, choose "new" to add record to your related table, then "submit" to save. So, 3 clicks instead of 1. 6. Having drivers/field crew that are diligent and care about building a good database. I have found that is the toughest challenge. ... View more

I had the same thing happen, Related tables in offline mode show "No Valid Location" just like in the 2nd screenshot above. Online mode the map works fine. Collector 10.3.5 Server 10.3.1 Token secured feature service added as item to AGOL, with credentials stored in item feat. service with archiving, editor tracking, attachments enabled Reproduce problem: New AGOL webmap Add the feature service item from AGOL Both the feature layers AND the related tables are auto. added to the map Configure symbology, popups, ect... Save webmap download webmap to Collector 10.3.5 click on a feature service polygon, under the details/relationship, click "new" to add record to relationship table Rather then displaying the fields for the related table, you get "No Valid Location" Workaround: New AGOL webmap Add Layer From Web Enter the URL to your secured feature service, example: hxxp://mydomain.com/arcgis/rest/folder/servicename/FeatureServer When prompted, enter service credentials Configure symbology, popups, ect... Save webmap download webmap to Collector 10.3.5 click on a feature service polygon, under the details/relationship, click "new", everything will work normally. Problem: There seems to be something incorrect with how AGOL is storing secured proxied service items? I'm not sure if its related to secured services, or services that contain relationship classes and related tables? Perhaps this is related to URL case sensitivity settings in IIS7? But regardless, it seems like offline Collector related records that were added from a AGOL item with stored credentials does not work in offline mode ... View more