Latest Contributions by MPC_KineticGIS_Department

‎09-03-2019

Still can't if you have a custom basemap. Waiting for this fix since the new collector was in Beta.

‎09-03-2019

There is this nice sharing feature in ArcGIS Online for Sharing with your entire organisation, pretty stock standard feature very useful. Collector for reasons unknown ignores this feature, you must share your maps to a group that your users must also be a member of. This is just getting crazy with the amount of hoops you need to go through to share content with collector. Can someone please explain to me why this is intended behaviour? Collector for ArcGIS "Note: In addition to the data requirements, a map appears in Collector if you created it or if you are a member of a group with which the map is shared in ArcGIS Online or ArcGIS Enterprise. The map must also be enabled for use in Collector." If you don't want content in collector just untick the use in collector box on the map.... Isn't your organisation the first group you are a member of?

‎08-01-2019

Struggling to see why vertical text alignment to the object with the text in it STILL isn't in 2.4!!! Horizontal alignment is there but vertical still isn't.

‎08-01-2019

Still a bug in 2.4

‎06-05-2019

So with complete frustration with the processes available I have managed to scrape together info from multiple sources to build this simple script that outputs the main info you need about your replicas. Runs infinitely faster than the embedded arcpy.da.ListReplicas module and gives you better more useful information. Just need to filter the list based on your criteria and feed into the API backend of ArcServer to remove the ones you need. import pyodbc import datetime print datetime.datetime.now() conn_str = ( r'Driver={SQL Server};' r'Server=SERVER\INSTANCE;' r'Database=DATABASENAME;' r'Trusted_Connection=yes;' ) cnxn = pyodbc.connect(conn_str) cursor = cnxn.cursor() query = """WITH cteReplicaLog(ReplicaID, MaxLogDate) AS ( SELECT ReplicaID, MAX(LogDate) FROM sde.GDB_REPLICALOG GROUP BY ReplicaID ) SELECT ITEMS.UUID, ITEMS.Definition .value( '(/GPReplica/ID)[1]', 'nvarchar(max)') AS "ID" , ITEMS.Definition .value( '(/GPReplica/Name)[1]', 'nvarchar(max)') AS "Replica Name" , ITEMS.Definition .value( '(/GPReplica/ReplicaVersion)[1]', 'nvarchar(max)') AS "Replica Version" , ITEMS.Definition .value( '(/GPReplica/CreationDate)[1]', 'smalldatetime') AS "Creation Date", ISNULL(CAST(replicalog.MaxLogDate AS smalldatetime), NULL) AS 'Sync Time' FROM sde.GDB_ITEMS AS items INNER JOIN sde.GDB_ITEMTYPES AS itemtypes ON items.Type = itemtypes.UUID LEFT JOIN cteReplicaLog AS replicalog ON items.ObjectID = replicalog.ReplicaID WHERE itemtypes.Name = 'Replica' ORDER BY 'Replica Name', 'Sync Time' ; """ cursor.execute(query) replicas_data = [] while 1: row = cursor.fetchone() if not row: print replicas_data break replicas_data.append(row) cnxn.close() ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

‎05-23-2019

Is there an ETA yet? its been almost 2 years now?

‎05-21-2019

Good to see the in the product plan means one day maybe. Tested this this morning with 2.3.3 and guess what still a BUG.

‎02-26-2019

I have been using the ArcGIS Pro Scale based symbology options and it great however I think a few key effects are missing from the options. I can see huge benefits for having say a building polygon layer that can then be symbolised based on points, and then say clustered points... a global effect for collapsing to the polygon centroid a global affect for clustered points with an option to display number of points

‎01-09-2019

Reading through this one is similar to https://community.esri.com/ideas/15983 , the issue is more the interface to deal with all of this needs a lot more work. Personally I avoid the REST API and do everything in python and geoprocessing tools as these are the out of the box toolset provided with package.

‎01-08-2019

Having now been running collector within our organisation for the last 4 years I have come across several issues with managing the ever increasing replicas generated from substantial use. One of our databases has over 400 replicas due to the volume of users and number of maps downloaded. There are several scenarios in which orphaned replicas can be created in the offline workflows: Device Lost, Damaged Device Hard Reset App Uninstalled Network dropout during initial download Recently I had a scenario in which a database had blown out substantially in size, after detailed investigation there were several replicas which had been orphaned for some time and were storing a large amount of changes. Currently the tools are problematic to identify which replicas we can safely remove and which need to be kept. doing this manually is very time consuming and has dangers due to the interface in which you can remove a replica is not able to have a filter applied, and crashes when you sort the table more than once. You can access using python the last sent and last received dates for a replica but you can't access when a replica was created? Neither can you un-register a replica using python, although I suspect this is a good thing as this has large disaster potential. We do need a better way to mange this potential mine field of performance and storage liability better. Personally I would like a means to use the properties you can get from arcpy.da.ListReplicas to include the created date and be able to use the Replica Class properties in other tools or as a means to filter the replicas in a more stable dialog window. Potentially an ability to "TAG" a replica with the results of a python script would be incredibly helpful. This BUG with the Replica Manager button has been consistent since 10.3 when I first found it. Still waiting for a fix other than don;t click on the column title more than once.

‎03-05-2018

Recently had an issue in which a user deleted an entire feature instead of a feature part. Given the Feature class has Archiving and versioning enabled I thought that this would be no problem to restore the row to the Live dataset. This however is deceptively difficult. As the feature class participates in a replica workflow I thought I just had to ensure the globalID was maintained when it was restored but I have as yet been unable to restore the row to the replica workflow whilst maintaining the history in the archive table. What would be great is a tool in which one or more rows could be reinstated back to the main table from the Archive table almost like an undo geoprocessing tool, however one that participates in the Archiving process. Restore these features to this point in time whilst maintaining the rest of the features as current.

‎02-01-2018

I would like to see the ability to have more than one Geoprocessing tool open and switch quickly between the two without having to reenter the information each time. Especially now that there is no independent select by location and attribute windows. I would love to see a toll be able to be docked independent of the toolbox, I can see a window on my second screen with 4-5 tools I am constantly flicking between, dropping results in and queuing up. I know its possible with the little button in the top of the geoprocessing window just would be alot handier if they were dockable windows.

‎08-09-2017

I have but apparently it is working as intended and as such no bug was created, I completely disagree with that statement. Once the analyst understood the issue, he discussed the issue with his team, and has advised that although there were numerous changes with the new update of ArcGIS Online in June 2017, the behaviour you have reported is the expected behaviour of Collector. No bug has been logged for this behaviour.

‎08-08-2017

The basic premise of what we are working on is that we have a large amount of dynamic data and it is filtered to only display design data that is approved for Construction. This design changes regularly and swaps between approved and unapproved based on changes to site conditions and construction requirements. To achieve this is a simple definition query in which a field Status is set to one of three options, Proposed, Current, and Archived. This is the same principle we have been using for years with the ESRI suite of products. To keep the Construction teams isolated from building unapproved or old designs query is set up so that data is only shown on any map they see to Status = Current. In downloaded maps in collector if a feature is changed from current to anything else the features remain in Arc Collector as current until the map is removed and re-downloaded again. During a sync the data is never updated or removed from the originally downloaded data. This behaviour is not the same behaviour that occurs in normal replicas or versions, this only occurs in offline maps in collector. What is the point of the sync functionality if it only does half of the job. I would have expected that any features that are removed from the map from a change in attribution by a layer query would also be removed from any downloaded maps after a synchronisation occurs? Does anyone have a work around solution for this type of replication management in a disconnected environment? We are now looking at other options to solve this as I can see no logical way of solving the issue. We have tried Definition queries in the service layer within ArcGIS Server. Filters within the Published map in ArcOnline. I should also mention that this works perfectly in where a feature is changed to current but not when it is changed from current to something else. At a function level it looks like the adds table is functioning correctly but the delete table is not being referenced in the child replica as the feature is filtered out.

‎06-13-2017

The Region setting within an AGOL organisation is very helpful, but it would be significantly better if services that are published or hosted in the organisation have date fields honour the display settings by default. This is honoured in the desktop applications that publish the services but not in the AGOL system. Or even better would be to add another setting to allow an Organisation to set the default date display format specifically. I know some organisations would want a Julian date format instead of a regional setting. Basically each time I create a service or hosted feature layer I have to go through and change the display settings for every date field to reflect our regional date standard. This is very tedious and time consuming to say the least especially when you have multiple dates in multiple layers.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by MPC_KineticGIS_Department

Re: Can Collector create multiple maps for multiple project areas?

Maps Shared to Organisation Not in Collector

Re: Layout Text Enhancements

Re: How to center align legends in ArcGIS Pro 2.2.2

Re: Collector Replica Management in ArcServer

Re: How do I transfer attributes between features in Pro?

Re: How to center align legends in ArcGIS Pro 2.2.2

ArcGIS Pro Scale Based Symbology Options

Re: Remove Orphaned Versions Created by Collector

Collector Replica Management in ArcServer

Restore Row from Archive Table

Have Multiple Geoprocessing Tools active

Re: Data remaining in Downloaded Collector Maps after changes to attributes that are filtered

Data remaining in Downloaded Collector Maps after changes to attributes that are filtered

Date Field Default Display Setting Across AGOL Organisation

Re: ArcGIS Online Time Zone - Over-ride UTC defaul...

Bulk Change date format for every date field in Po...

Bulk Change date format for every date field in Po...

Have Multiple Geoprocessing Tools active

Re: ArcGIS Pro: 2.4.2: In general, ArcPro has less...