this data set contains 
	Q:\GIS\Department_Lands_and_Facilities\Property_Points\R3CDFW_property-points_epsg6318.gpkg
	and the companion file ;
	Q:\GIS\Department_Lands_and_Facilities\Property_Points\vector-collected_from-lands-folder\R3CDFW_collected_lands_property_points_epsg6318.gpkg

A BETTER VECTOR COLLECTOR WOULD WORK DIRECTLY OFF OF R3CDFW_PROPERTY-POINTS_EPSG6318
ELIMINATEING THE MIDDLE MAN AND FACILITTATEING DELETEING RECORDS FROM THE MANANAGEMENT POINT BACK TO THE SOURCES


python foldernote files 
-------.PullUpdates-------
pulls new records from the vector collected in R3CDFW_property-points_epsg6318

-------.pushUpdatesTo-------
pushes changes from R3CDFW_property-points_epsg6318 back to the vector collector layer (6318)

-------.PushUpdates-------
pushes changes from R3CDFW_property-points_epsg6318 back to the source layers


A BETTER VECTOR COLLECTOR WOULD ELIMINATE THE USSAGE OF THE FIRST TWO BUT STILL NEED .PushUpdates


-------.downloadFromAGOL--------
backups/downloads go to ...
	download_archive_to : Q:\_agol_backups\R3GIS\Department_Lands_and_Facilities
	download_archive_format : gdb

currently exports (downloaded) now appear to contain the contingency values/ field groups
which is good but even if they are lost, R3GIS_AGOL_contingency-update.py can rebuild them
once your layer is back online

-------.contingencies ---------------- 
after editing the contingency table https://experience.arcgis.com/experience/3276c09b396c417cac5ff01ed2b43163
run R3GIS_AGOL_contingency-update.py

-------.publishToAGOL.dont-use------------
the export also comes with the attachment photos
which if you refactor in qgis you will loose AFAIK...but further testing may yield a method
so refactoring can only happen in ARC

-------.editstoagol----------------
as such, this layer uses R3GIS_AGOL_Edit.py (AKA: R3GIS_AGOL_synch-edits.py)
instead of R3GIS_AGOL_Make-PublishingFile.py and R3GIS_AGOL_UploadOrOverwrite.py

-----.create-ITRF----------
a ITRF version is generated mainly for ussage in qfield


---------------------ATTRIBUTES--------------------------------------------
the remote version contains a subset of R3CDFW_property-points_epsg6318
R3CDFW_property-points_epsg6318 may be a subset of teh vector collection : R3CDFW_collected_lands_property_points_epsg6318.gpkg

--- in remote and local
category : Q:\GIS\Department_Lands_and_Facilities\Property_Points\field_values\category.xlsx
type : Q:\GIS\Department_Lands_and_Facilities\Property_Points\field_values\types_by_category.xlsx
name : name, nickname, id, 
label : used for labeling the object, will be a copy of name or type by default
public_info :  yes/no
notes : large free text area used conceptually for any overflow from cat/type/name/label
request : see Q:\GIS\Department_Lands_and_Facilities\Property_Points\field_values\requests.csv
quality : FIX (could be PPK, RTK, or PPP), PPK FLOAT, GPS in FieldMaps, Fixed RTK, AGOL entry, PPK FIX
method : description of the method used to achive the quality, includes the reciver used and the nature of the control

gnss_id : a simple date time ID used to track a feature (filled in automatically if missing)
last_edit : filled in automatically
last_edit_by : filled in automatically
agol_status : filled in automatically by E:\DAIV\tasks_scheduled\ARC\R3GIS_AGOL_Edit.py

--- vector collector based
source_record_id : if the data originates from another source 
source_id : if the data originates from another source 
src_epsg : if the data originates from another source
src_file : if the data originates from another source

--- these are only filled in for records coming from the Reach/OPUS RTK/PPK system
about_gis : 
ppk_conf : 
ssg_used : 
num_wild : 
relquality
ppk_cnt_p
ppk_sd
ppk_sd_all
spreadFact
ppk_cnt
duration
elev_m
elev_ft
elev_src
hgt_4326
hgt_6318
elev_12b_m
elev_18_m
ant_hgt
orig_qual
origsample
conf_rank
float_sd
ppk_shift
date
time



---------------------OLDER--------------------------------------------


more geenral material about PUSH / PULL
AS A MEANS OF A EXAMPLE...

properties of public interest
is a PULL as it gets its parcels from many counties

but you could have many projects that have created selections of parcels (consumers)
if you wanted to update all of those that used napa county parcels
then you would do a PUSH from napa to all

or if you just wanted to update one of the selection sets
then do a PULL from it againts all authories (each countie says its an authority on "APN")

if you have many consumers and many authorities then you have a bit of a mess
one way to overcome it is to vector collect the authorities and then you can PULL 
againts that vector colllection

thats whats kinda going on here. the data set in this folder recieves attribute updates from local edits and from agol
and it get geometery updates and new records from the ITRF version of the vector collection by doing a PULL. 
if you want these attributes to go back to the lands folder then you have to do a PUSH.