Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Should the simplification rules include extensions? 
    • Since this action's remit is to define additional encodings, the focus should be on simplifying structures that are deemed difficult to use, rather than duplicating information (in a complex and a simple structure) in the same data set. There may be different encodings with different levels of complexity depending on the supported use case.
    • A chapter on "extensions" should be added in the GP document on simplification rules that explains this aspect. It will also be important to define the terms "extension", "profiling", "flattening" 
  • Generic vs. theme-specific rules (for which themes?)
    • The main question here is whether the action should aim for generic or theme-specific rules?
    • It was agreed that the action should develop a list of generic simplification rules that can be applied to create an encoding as well as a default (sub-)set of these rules that should be applied to all themes (wherever possible). Additional further rules from the list might then be applied in addition for specific themes.
    • In general, the set of rules applied for a given theme and/or use case need to be validated before promoting them as a good pratice in INSPIRE.

      All to use this issue ( to propose sample INSPIRE data sets, themes and/or use cases that can be used to develop examples of the proposed GeoJSON encoding and simplification rules. These examples should serve to prototype and test the proposed approaches, to focus our discussion and to illustrate the proposed approaches in the GP documents. Where possible, please also include (pointers to) open sample data that can be re-used.

    • The following themes were already proposed in the discussion: AD, O&M (AC-MF, OF and borehole-related observations), AU (to be checked with Spain), AM (to be checked with Denmark)
  • Should the GeoJSON encoding rule include simplification rules? 
    • There could be separate GeoJSON encodings using complex or simple structures for the non-spatial properties.
    • However, since the rationale for this action is to improve usability of INSPIRE data in standard GIS client applications, the GeoJSON encoding should use simple structures as much as possible.