Skip to content
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

Develop Geo data specification protocol #545

Closed
serahkiburu opened this issue Nov 27, 2017 · 4 comments
Closed

Develop Geo data specification protocol #545

serahkiburu opened this issue Nov 27, 2017 · 4 comments

Comments

@serahkiburu
Copy link
Contributor

From @henrykironde on November 10, 2017 3:5

From the previous discussion on issue #86
I have created a repository and I have included sample specifications that I have been working with.

Note:
As s @Stephen-Gates stated in the previous discussion

I think a worked example using real data would help to clearly separate what's needed in a :

 **spatial data package**  - similar  [tabular-data-package](http://specs.frictionlessdata.io/tabular-data-package/) tabular data package E.g. 
 - Each resource MUST be a Spatial Data Resource 
 - or could a mix of Spatial and Tabular data be in a package? 
 - should spatial and temporal extent be described at this level or for each resource?
 
 **spatial data resource** - similar to  [tabular-data-resource](http://specs.frictionlessdata.io/tabular-data-resource/) tabular data resource 
 - the spatial reference system must be included 
 - the supported file types (GeoJSON, GML, etc)
 - would a CSV with point data be a valid resource?
**layer schema** - similar to [table schema](http://specs.frictionlessdata.io/table-schema)

There are two categories

  1. Vector specifications
  2. Raster specification
  • Each category should have it's own json file.
  • Most of the vector data can be specified, including CSV geodata, GeoJSON, GML,
  • A data package can describe several resources, if these resources share some common attributes, however to keep it simple we propose a one to one mapping of spatial file to json file.
    (I think this will take care of issues relating to the level at which we describe certain properties )

For the case of raster files, the resources value is a list of bands with their identifying properties like group, variable, band name etc.

For the case of vectors, the resources are the layers for that particular dataset

https://github.com/henrykironde/spatial-packages

Copied from original issue: frictionlessdata/frictionlessdata.io#359

@serahkiburu
Copy link
Contributor Author

From @Stephen-Gates on November 10, 2017 20:11

See also https://discuss.okfn.org/t/geo-data-package/6143

@henrykironde
Copy link

@bidhya, feel free to have a look and contribute.

@Stephen-Gates
Copy link
Contributor

Now there is a Spatial Data Package Investigation report. Have a read and comment here or on the forum.

@rufuspollock
Copy link
Contributor

DUPLICATE of #86. @serahrono please can you merge relevant comments from here into #86

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

4 participants