New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why are resolutions are defined in terms of 'minimum' separation? #1154
Comments
The typical usage or 'resolution' for spatial data is related to numerical precision-- what is the smallest distance (in geographic space) between two points that can be asserted to be in different locations. Locations reported to the nearest km in that dataset would be reported with different accuracy or location uncertainty. |
Thanks @smrgeoinfo ! Would it be similar for time? I.e. if one has a dataset with three observations, two that are one second apart and the third that is one year later than the other, would one say the temporal resolution is also one second? |
W.r.t. the time question, as long as the encoding scheme for temporal position has precision sufficient to resolve one second, yes. |
Labelled "future-work" as for discussion in the 2019-11-05 telecon and related resolution |
ok, thanks @smrgeoinfo ! |
Good, Thanks @aisaac and @smrgeoinfo!
|
This is issue is both for spatial and temporal resolution. both are defined in terms of 'minimal separation'. But shouldn't it be 'maximal separation' instead?
For example at https://w3c.github.io/dxwg/dcat/#Property:dataset_spatial_resolution
"Minimum spatial separation resolvable in a dataset, measured in meters."
For me if a dataset has reports for points separated by one meter in some areas (e.g. in dense cities) and one kilometer in others (e.g. in remote places), then the resolution is not one meter. I'd rather say it's one kilometer, if I had to make a choice.
I'm marking this as editorial because there may be a chance that I'm simply misreading all these sentences about resolutions. Or maybe I can learn some official definition/practice that I've completely missed so far :-)
Maybe it's for future work, too
The text was updated successfully, but these errors were encountered: