Full Spatial Representation

[jwaspin]

Full Spatial Representation Feature

This issue is intended to capture the next steps for Spatial Representation within the context of the mdToolkit.

Current State

mdEditor

There is nothing, at all, in the mdEditor that represents spatial representation, so no part of the mdJson-schema is currently viewable/editable in the mdEditor.

mdJson-schema

Completed.
Related:
Issue: adiwg/mdJson-schemas#245
PR: adiwg/mdJson-schemas#258

• added scope to spatial representation in the schema.

mdTools

Completed. Temporary Link <-- if this is broken it might be updated here.

mdTranslator

Parts of the mdTranslator have been updated to handle the translation for spatial representation.
adiwg/mdTranslator#241
This PR shows the additions for scope in the mdJson reader, HTML writer, ISO 19115-1 (now -3) writer, and mdJson writer.

Next Steps

Everything should be ready for the mdEditor, so no additional work should be required to add this to the mdEditor. The next step for the mdEditor would be to add the spatial representation array in the "Spatial" tab, which would present the user with 2 dropdown menu's: one to select the type of the representation (grid/vector/georeference/georectified) and another to select the scope code. Alternatively, the mdEditor could present the user with the full scope array which is where the user would select the scope code.

Full Support

Once the scope array (or at least the code) is available, the next step would be a large effort to support the entirety of spatial representation, meaning the type of representation selected would need to change the visible form fields to the respective type.

Related

adiwg/mdJson-schemas#242
adiwg/mdTranslator#222

[hmaier-fws]

Decision made to not develop mdEditor user interface at this time. Updates to schema and translator have been completed.