You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no reason to store data as SHP + CSV any longer. CSV output is helpful for inspection outside of R / GIS, however, it is difficult to actually use in ESRI tools.
GeoPKG works well for storing spatial data:
sample locations
polygons with QA/QC metrics already attached
Also, we would not be limited to 10 characters in field names. Be sure to remove reserved characters like "." from field names.
No reason except for the fact that they are very commonly used formats still.
I like GeoPKG... but I am not really convinced we can make them work with ESRI tools consistently. Has there been some improvements on this I am not aware of?
There is no reason to store data as SHP + CSV any longer. CSV output is helpful for inspection outside of R / GIS, however, it is difficult to actually use in ESRI tools.
GeoPKG works well for storing spatial data:
Also, we would not be limited to 10 characters in field names. Be sure to remove reserved characters like "." from field names.
Notes here.
The text was updated successfully, but these errors were encountered: