HPE XIDs

HPE XIDs do not encode their ordinals (i.e. tags and offets). XIDData.prop is required to maintain backward compatibility.

Generate / Verify XIDData.prop

$ java -Xnoclassgc -jar $XIDSDK/bin/xidcg.jar \
     -v \
     -prop https://xid.location.studio/Tensor/V1.0.0/XIDData.prop \
     -prop https://xid.location.studio/HPE/V1.2/XIDData.prop \
     https://xid.location.studio/HPE/V1.2/HpeBLE.xid.xml \
     https://xid.location.studio/HPE/V1.2/HpeCellular.xid.xml \
     https://xid.location.studio/HPE/V1.2/HpeCore.xid.xml \
     https://xid.location.studio/HPE/V1.2/HpeGnss.xid.xml \
     https://xid.location.studio/HPE/V1.2/HpeUsage.xid.xml \
     https://xid.location.studio/HPE/V1.2/HpeWiFi.xid.xml

or

$ java -Xnoclassgc -jar $XIDSDK/bin/xidcg.jar \
     -v \
     -prop ../../Tensor/V1.0.0/XIDData.prop \
     -prop XIDData.prop \
     HpeBLE.xid.xml \
     HpeCellular.xid.xml \
     HpeCore.xid.xml \
     HpeGnss.xid.xml \
     HpeUsage.xid.xml \
     HpeWiFi.xid.xml

If xidcg reports:

Generating: xidout/meta/XID/XIDData.prop

Then something has changed and XIDData.prop needs to get updated.