-
-
Notifications
You must be signed in to change notification settings - Fork 505
add datepicker with indeterminate position to iso19139 schema. fix datepicker. layout fix #9151
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
base: main
Are you sure you want to change the base?
Changes from 8 commits
be90512
29726d8
e544915
fa6fb38
8638316
a243b37
efd8b22
fd322b0
2ef8342
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -159,6 +159,7 @@ | |
| elementRef: "@", | ||
| id: "@", | ||
| tagName: "@", | ||
| assumeGmlNs: "@", | ||
| indeterminatePosition: "@", | ||
| required: "@", | ||
| hideTime: "@", | ||
|
|
@@ -358,14 +359,26 @@ | |
| scope.dateTime = ""; | ||
| } | ||
|
|
||
| //if we don't know what this namespace is (findNamespaceUri returns undefined), | ||
| //then we don't add it! | ||
| var elementNSDef = ""; | ||
| var namespaceURI = gnSchemaManagerService.findNamespaceUri( | ||
| namespace, | ||
| gnCurrentEdit.schema | ||
| ); | ||
| if (namespaceURI !== undefined) { | ||
| elementNSDef = " xmlns:" + namespace + '="' + namespaceURI + '"'; | ||
| } | ||
|
Comment on lines
+365
to
+371
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would not be more efficient to put this code in the else of: //if data-assume-gml-ns is set, then don't put in the NS declaration
if (scope.assumeGmlNs === "true" && namespace === "gml") {
elementNSDef = "";
}
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think efficiency is important here.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In that case is ok. |
||
|
|
||
| //if data-assume-gml-ns is set, then don't put in the NS declaration | ||
| if (scope.assumeGmlNs === "true" && namespace === "gml") { | ||
| elementNSDef = ""; | ||
| } | ||
|
|
||
| scope.xmlSnippet = | ||
| "<" + | ||
| tag + | ||
| " xmlns:" + | ||
| namespace + | ||
| '="' + | ||
| gnSchemaManagerService.findNamespaceUri(namespace, gnCurrentEdit.schema) + | ||
| '"' + | ||
| elementNSDef + | ||
| attribute + | ||
| ">" + | ||
| scope.dateTime + | ||
|
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |




There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@david-blasby this change target better the element and solves the problems with the full view. Please give a try and let me know.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had some issues with the sample data, so I had to update this to:
match="gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement[//local-name()='beginPosition']"
(i.e. handle multiple GML "versions" by using
local-nameinstead of a prefixed name (ie.gml:beginPosition)).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@josegar74 - I'm not sure how that will work. Here is a typical
beginPositionXML (from the GN sample data):I'm not sure how:
match="gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification/gmd:extent/gmd:EX_Extent/gmd:temporalElement[gmd:EX_TemporalExtent/gmd:extent/gml:TimePeriod//gml:beginPosition]"
will match this. Perhaps I am unfamiliar where the "
[" will occur. I I thought it would evaluate at thegmd:temporalElementlocation (i.e. requiresgmd:temporalElement/gmd:EX_TemporalExtent/...).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@josegar74 - I've pushed another commit.
local-namematching for thegml:/gml320:prefixeslocal-namematching)I'm not sure how to test what you found (unable to add
TimeInstant). I think (not sure) that its still problematic.