Quick question on Step 1 Reoptimization after marking GCPs and Check Points. After this step, can I switch all the GCPs I had marked previously as GCPs to “Check Points” to see how close my PPK data is on it’s own (with no GCPs) or would the check point results in the Quality Report be skewed because I already did Step 1 and Reoptimized after adding initial GCPs/Check Points? If this is the case, I assume I would have to Rematch and optimize to get a more balanced comparison against check points?
Mark GCPs on images using raycloud and set them as check points. As you mark them, you’ll be able to see the accuracy of each point.
Reoptimize and regenerate quality report.
By using this method, the GCPs will never be used in the model so you can get a true accuracy assessment of your PPK data. If the result doesn’t meet your accuracy needs, then convert one point at a time from checkpoint to GCP and reoptimize. Then you can see how many GCPs you actually need to meet your accuracy requirement with PPK.
Based on my workflow above…marking GCPs and Check Points and Re-optimizing after I run Step 1. It doesn’t sound like I can toggle the GCPs I initially marked before to check points status and re-optimize again without getting results that would be skewed. Meaning because I marked those GCPs initially and classified them as GCPs, they are still somehow held as GCPs even though they’re now considered check points?
Andrew’s method gives you the possibility to check the actual accuracy of your PPK data, which weren’t affected by any other external source of information - GCPs.
Looking at the workflow you applied, marking the GCPs changed initially implemented PPK information.
By changing the label of GCPs to checkpoints you won’t remove that impact the GCPs had already had on your dataset.
Therefore, I would recommend creating a project from scratch and following the workflow Andrew mentioned.
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.