-
Notifications
You must be signed in to change notification settings - Fork 1
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
errors on maps/gt - check it out #11
Comments
Frames 3378 and 3379 should be labelled as type 3 rather then as type 0 (see the map); but there is a car and probably in the GT we missed the 1 at the end; so, change GT from
saved in both
|
2011_10_03_drive_0027_sync frame 3850 missing "in crossing"
adding "1" to the GT and copying/sync this file to
frames 1055-1072 have this kind of error probably error in map issue here is the "density" of the OSM map tried to simplify the road and split the ways but there was no way to create the type 2 intersection; modifying the GT accordingly.
values before (1220-1236) are not considered and do not appear in the PNGs, skipping from 1217 to 1237 gt file stored in
|
@Pharaun85 tendria que estar terminado, pero yo creo que podemos nuevamente generar los "check_osm" y verificar todo de nuevo... tarde horas a hacer estas cosas :-( los nuevos png para controlar todo estan aca |
Secuencia 33, frame frame 964
change in GT; |
there are some errors/discrepancy bewteen the OSM ground truth and the BEVS.
After a review process performed using check_osm_with_gt.py and the associated output stored in
sftp://[email protected]/media/augusto/500GBDISK/nn.based.intersection.classficator.data/check_osm
with the output that is like an image + a txt file; if the first image differs from the last image, there is an error;
Alvaro ended up with the following issues
The text was updated successfully, but these errors were encountered: