File naming doesn't follow a consistent scheme. I implemented _ delimited {type}_{id} but that won't work for some files because of GW_, HY_, and 00463X0036_H1.2. In other parts of the app, I did {organization}/{featuretype}/{usecase}/{id} would it be possible to use this convention for these? I changed some file names and made up a usecase id for each as you'll see in the content I commit.
The @id element references a WFS. I'm not sure what the right way to connect these files to the ELFIE demo URLs is, but we should do something so they are connected?
https://github.com/opengeospatial/ELFIE/blob/master/data/FR_surface_ground_water_interaction/GW_HydrogeoUnit_121AT01.json and https://github.com/opengeospatial/ELFIE/blob/master/data/FR_surface_ground_surface_roundtrip/Aquifer_507AC00.json have
{"gwml2":"http://opengeospatial/def/ontology/gwml2"}
as an item in their context. This doesn't seem right?File naming doesn't follow a consistent scheme. I implemented
_
delimited{type}_{id}
but that won't work for some files because ofGW_
,HY_
, and00463X0036_H1.2
. In other parts of the app, I did {organization}/{featuretype}/{usecase}/{id} would it be possible to use this convention for these? I changed some file names and made up a usecase id for each as you'll see in the content I commit.The
@id
element references a WFS. I'm not sure what the right way to connect these files to the ELFIE demo URLs is, but we should do something so they are connected?