Modified verses create in revision table

Dec 1, 2011 at 8:45 PM

We have a somewhat unique work flow where we are doing a "download and symbolize data" and then copying some of our local point data into this dataset. It works. We are getting some "modified" attributes as opposed to "create" attributes in the revision table. What makes some points modified rather than created when we're copying and pasting? Is it something based on proximity or perhaps an attribute?

I don't believe this is creating a problem for us, we just need to understand what's happening so we can figure out our work flow. 

Thank you - Greg Matthews

Coordinator
Dec 1, 2011 at 11:56 PM

Hello Greg, good to hear from you!

I will ping the dev team and find out; would be good for us to add this to our documentation.

Christine

Coordinator
Dec 2, 2011 at 10:59 PM

Hello Greg,

I received a response from the dev team, but sounds like we'd need to do some testing here to confirm. We believe the behavior is related to the proximity of the copied points. There is a small tolerance for where points are copied into the dataset where they are considered as 'modified' rather than created; this is so we don't generate points that are on top of one another. There can only be one point, but it can participate in multiple geometries (points, lines, and polygons).  So what may be happening in your case is that the location of the copied-in points are considered coincident with the existing points already there, and so they are added as 'modified'.

We will try copying in some points here and verify... but this is our hypothesis.

Have a great weekend,

Christine

Dec 5, 2011 at 2:08 PM

Thanks Christine. This makes sense and is good insurance to prevent copy over. If this is the mechanism, it will probably help us to not create duplicates as we try to load our VGI points into OSM.


Greg Matthews, GISP
Transportation Partner Support
National Geospatial Technical Operations Center
Box 25046, MS 510
Denver, CO 80225-0046
Office: 303-202-4446
Cell: 303-345-8353
GDMatthews@usgs.gov



From: "eggwhites" <notifications@codeplex.com>
To: gdmatthews@usgs.gov
Date: 12/02/2011 05:00 PM
Subject: Re: Modified verses create in revision table [esriosmeditor:281534]





From: eggwhites

Hello Greg,

I received a response from the dev team, but sounds like we'd need to do some testing here to confirm. We believe the behavior is related to the proximity of the copied points. There is a small tolerance for where points are copied into the dataset where they are considered as 'modified' rather than created; this is so we don't generate points that are on top of one another. There can only be one point, but it can participate in multiple geometries (points, lines, and polygons). So what may be happening in your case is that the location of the copied-in points are considered coincident with the existing points already there, and so they are added as 'modified'.

We will try copying in some points here and verify... but this is our hypothesis.

Have a great weekend,

Christine

Read the full discussion online.

To add a post to this discussion, reply to this email (esriosmeditor@discussions.codeplex.com)

To start a new discussion for this project, email esriosmeditor@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com