You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
See screenshots below
Import MGCP TRD v4.5.1 data with Hootenanny
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
Hootenanny exported data with only GFID
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.
The text was updated successfully, but these errors were encountered:
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:
Expected behavior
GFID and UID fields are preserved on data import and export.
Screenshots
Original GFID and UID on import data
Hootenanny exported data with only GFID
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.
The text was updated successfully, but these errors were encountered: