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
{{ message }}
This repository has been archived by the owner on May 24, 2024. It is now read-only.
It only happens in the centreline table so far. Basically the output from shared streets will be the indication that the link was matched, along with NULL values for the rest of the output fields.
The only case we have seen so far are for centreline segments with the geo_id of 30104621. This same geo_id is not in gis.centreline, it is only in gis.centreline_both_dir or gis.centreline_one_way. The segment is on Melita Crescent and seems to be pretty normal, so we do not understand why it was not matched.
The text was updated successfully, but these errors were encountered:
We currently created a list null_matched in our function conflator.ipynb to store these cases. These cases are not being inserted in the final output table.
The original geojson for two linestrings (both direction for one street segment - Melita Cres) that got matched but returned no reference_id or any attributes: Original Geojson
Kevin is tackling this. this is related to the conversion from MultiLineStrings to LineStrings. we match individual LineString features and need to split up the MultiLineStrings into individual features before we attempt matching. i think the properties are getting lost in that cleaning process.
It only happens in the centreline table so far. Basically the output from shared streets will be the indication that the link was matched, along with
NULL
values for the rest of the output fields.The only case we have seen so far are for centreline segments with the
geo_id
of30104621
. This samegeo_id
is not ingis.centreline
, it is only ingis.centreline_both_dir
orgis.centreline_one_way
. The segment is on Melita Crescent and seems to be pretty normal, so we do not understand why it was not matched.The text was updated successfully, but these errors were encountered: