Latest Contributions by JamesMudd1

I was able to resolve this issue by adding the Attribute Table Function.  After completing the recommended workflow in the provided link, and re-adding the layer to ArcMap, the Unique Values renderer is available in the layer properties.  I am using ArcGIS Desktop v.10.5.1.   --Jim ... View more

Very large complex features can cause these issues.  Avoid using multipart features, features with 'holes', and very dense/complex features with many vertices.  --Jim ... View more

We have about 20 Juno SB units, in service for about 5 years.  We've picked up 2 additional Juno 3B units to replace faulty units.  They have been workhorses for us, but we do have a lot of the same issues others in this thread have experienced.  We do a lot of wildlife surveys, so the accuracy has been acceptable (able to navigate and find a nest to repeat survey collection).  The camera does not have the quality/zoom required, so we don't use them at all.  We have had several units go bad, but over a 5 year period that is expected to a certain degree.  We've had a couple units where the USB port has failed (motherboard replacement ~the cost of a new replacement unit, hence the 3B units).  We have also had one just mysteriously fail to turn on, dead as a doornail- no tech support solution from vendor.  And a smashed screen here or there, but usually the otterbox does it's job.  As far as performance issues, the most important advice I can give is avoid very large complex polygons!  Do not create multi-part polygons. Land Ownership is a critical layer for us (to avoid trespass issues).  The background matrix of contiguous private lands (this is not individual parcel data, just categorized public/private classes) can create huge, complex polygons that span across large sections of the state with tens of thousands of vertices, data holes, etc.  We use an overlay tool to split the polygons to bite-size units, like PLSS townships.  The other work-around is to clip your data to your project area to reduce the size of large or meandering features.  Google "arcpad perfomance tips" to get other tricks, like turning off extensions, layers, simplify symbology, zoom-in tight as possible to study area for checkout, etc.  Found a lot of damn annoying bugs.  Reported to esri, but they don't seem to get fixed.  I.e. a definition query on a *date* field throws a serious error!  Have to use a query on a dummy field instead.  Minor workaround, but annoying as hell when you are trying to implement a clean, normalized geodatabase schema design across an organization.  <grumble, grumble>  Anyway, ... Hope that helps.  Good luck!  Glad this thread was created.  We're still a few years out from implementing Data Collector on Android, so I'll be browsing this discussion again. --Jim ... View more

Hi Ingrid, After a few calls with ESRI tech, it appears that this is a 'design feature' and not a bug.  The ArcSDE geodatabase does not allow storage of geometry errors.  ArcPad isn't as smart, so allows the errors to be collected.  The limited functionality of arcpad is mainly due to the limited processing power of the mobile device; esri can only do so much.  So, our solution is to use geodatabase replication to create check-out file geodatabases for each project and generate arcpad checkouts from the file geodatabases, which will allow the errors to be checked-in.  The errors can then be resolved in ArcMap desktop, which is much easier.  To give you a little more info on our system design strategy, we will be using the replica file geodatabases as our primary project databases, checking-in and checking back out on a regular basis.  We will use the server geodatabase as a tool to syncronize and aggregate the multiple project replica geodatabases.  One drawback is that we can't have multiple editors on the project file geodatabases, but we can have them edit the server data directly if we're in a crunch.  One benefit is that the project managers can edit the replica databases with ArcView, reducing the need for more expensive ArcEditor licenses.  Please reply to this thread if you come up with any other work-arounds or if you have more questions.  Good luck.  --Jim Hi Jim Did you ever get this resolved?? We have avoided the transition from shapefile checkouts (still available in ArcGIS 9.3.1) to axf checkouts for exactly this kind of issue (among others). But we are finally gearing up to upgrade to ArcGIS 10 and we need to resolve this exact issue. Your input would be VERY much appreciated! Ingrid ... View more

Hi Denise, Thanks for the reply.  I have explored this workflow.  However, the FME extension only allows you to view the .axf data, or export it to a new geodatabase featureclass, but not to edit the data in-place in the .axf.  This means it would require a manual editing session to move the features from the new featureclass into the original geodatabase from which it was checked-out.  This isn't too big an issue when you are collecting new features, but if you are editing existing features, it is a big issue to avoid duplicates.  So, our workflow is going from check-out/check-in to check-out/export/repair geometry/load/(edit).  The goal is to make the process of collecting features in the field and getting them into the organization geodatabase easier and less prone to errors.  We have about 15 project managers collecting data throughout the field season needing to get the data back into the geodatabase on a daily or weekly basis.  An involved manual workflow will be a problem to manage.  Can it really be this problematic to collect polygon GPS data and sync it with a geodatabase?  Are we the only ones trying to do this?  I find that hard to believe.  I'm sorry if my frustration is showing, but this seems like such a basic function I can't believe it's this problematic.  I would hate to have to abandon our ArcGIS Server development and go back to project-level personal geodatabases.  --Jim James, Your post didn't say what versions of ArcPad and ArcGIS Desktop you are using and what I am going to introduce you to is only available with ArcPad 10.0.3, released earlier this month. New at ArcPad 10.0.3 is the ArcPad AXF Extension for FME which allows ArcGIS users with FME 2011 SP3 to browse AXF files in ArcCatalog, drag/drop AXF files into ArcMap, and export AXF files into a Geodatabase. For more information, please review the ArcPad Help on ArcGIS Resource Center. Now you can read your ArcPad AXF files directly in ArcMap or ArcCatalog using the ArcPad AXF Reader for FME. The ArcPad AXF Reader for FME  is available right now in FME 2011 SP4 and FME 2012 beta. If you already have a license for FME, download either of these and  start using the extension now. If you do not have a license for FME, you can obtain a free temporary license right now from www.safe.com/arcpad. The ArcPad AXF Reader will be integrated in the ArcGIS 10.1 Data Interoperability Extension. Cheers, Denise ... View more