Skip to content
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

MGCP TRD 4.5.1 GFID and UID - UID dropped #5236

Open
tdvorakcaci opened this issue Feb 8, 2022 · 1 comment
Open

MGCP TRD 4.5.1 GFID and UID - UID dropped #5236

tdvorakcaci opened this issue Feb 8, 2022 · 1 comment

Comments

@tdvorakcaci
Copy link

Describe the bug
MGCP schema has GFID (Global Feature Identifier) and UID (MGCP Feature Universally Unique Identifier) fields. These are typically identical and in capital letters. When data is exported using Hootenanny, GFID fields are preserved (lower case letters) and the UID field was dropped into the OSMTAGS field.

To Reproduce
Steps to reproduce the behavior:

  1. See screenshots below
  2. Import MGCP TRD v4.5.1 data with Hootenanny
  3. Export data with MGCP schema switcher with Hootenanny

Expected behavior
GFID and UID fields are preserved on data import and export.

Screenshots
Original GFID and UID on import data
image
Hootenanny exported data with only GFID
image

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
There are differences in the upper and lower case GFID/UID values between the original imported data and the Hootenanny exported data.

@mattjdnv
Copy link
Contributor

I have tried a lot of options and I am unable to replicate this with the data I have.

@tdvorakcaci More info is in an email to you.

mattjdnv added a commit that referenced this issue Feb 11, 2022
mattjdnv added a commit that referenced this issue Feb 11, 2022
mattjdnv added a commit that referenced this issue Feb 15, 2022
* More fixes.

refs: #5236

* Removed commented out line

refs: #5236
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants