search

ngageoint / hootenanny

Hootenanny conflates multiple maps into a single seamless map.
GNU General Public License v3.0
353 stars 74 forks source link

Determine which source date time value to populate in TDSv61 FGDB exports #145

Closed mikejeffe closed 8 years ago

mikejeffe commented 8 years ago

When hoot conflates two input layers, the source date time values get merged into a source:datetime tag that is semi-colin deliminated (e.g. date1;date2). This becomes an issue when exporting to TDSv61 as a file geodatabase because the tag will exceed the 20 char limit defined for the ZI001_SDV (based on the spec) causing the export to fail. As a work around we are just populating this field with the first date but we need to know the best way to populate this attribute.

The first value in the list? The earliest value? The last value?

jasonsurratt commented 8 years ago

@mjeffe98 Can we assign this to someone to run down a user requirement? If not these types of tickets tend to languish in backlog until they get closed as OBE. @sisskind?

mikejeffe commented 8 years ago

Assigned to @sisskind to track down an answer.

mikejeffe commented 8 years ago

The feedback from the TEM was to use the reference layer which I am fairly certain we have implemented. @mattjdnv can you update this ticket with the status of that?

mikejeffe commented 8 years ago

The data will export cleanly now but there is further refinement needed to build the internal business logic within the UI/core to be able to select which date to use e.g. reference vs. secondary. That work should be discussed in a separate ticket.