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
I spotted two Locations issues that we may have missed in the locations refactor:
in the search results table for units, the outlinks to OSM in the "site" column are all nodes. This is incorrect, as sites may also be other geotypes (relations, ways) now. The url in the sites column should not assume the geotype is a node.
non-OSM objects may be present in the data now. They are flagged as such in location:origin ("osm" for OSM, "sfm" or other values for non-OSM). We will have to look at how we represent these non-OSM shapes across WWIC. For example, in the sites or areas of operation block in units records, non-OSM objects would not need an outlink to OSM.
Let's discuss. We can split this out into separate issues as we find a forwad path.
The text was updated successfully, but these errors were encountered:
I spotted two Locations issues that we may have missed in the locations refactor:
location:origin
("osm" for OSM, "sfm" or other values for non-OSM). We will have to look at how we represent these non-OSM shapes across WWIC. For example, in the sites or areas of operation block in units records, non-OSM objects would not need an outlink to OSM.Let's discuss. We can split this out into separate issues as we find a forwad path.
The text was updated successfully, but these errors were encountered: