Christopher Beddow

@frodrigo @MartinMikita it seems `landcover`, `landuse`, and `park` are all polygons so adding a point type to them is a bit out of place, and a tree is not really...

There are quite a few other access tags to consider also, that may be categorized as say "not normally available as a parking space" -- maybe could lump these into...

@mvexel I want to suggest also: 1) street lamps (generally quite reliable data) and 2) utility poles (not as reliable but very helpful for Youthmappers projects in Africa) for data...

For overpass de-dupe, I suggest we make a basic dict of the OSM values for each Mapillary value. Then easy to simply make an Overpass call with a small (10x10...

We may also be able to request the images associated with each object, for previewing. Once we have a list of features we want the user to evaluate, for each...

@Rubix982 looks good, do you think we need to do much more to make this possible or it's already possible?

The official list for now is under "traffic signs" and "point" here (points == map features in this context): http://web.archive.org/web/20210105003120if_/https://www.mapillary.com/developer/api-documentation/#traffic-signs http://web.archive.org/web/20210105003120if_/https://www.mapillary.com/developer/api-documentation/#points This exact list should migrate to the new API...

We'll add this after doing an official announcement!

Thanks for helping @Rubix982! Asking for feedback. I suspect Windows has something strange about the Shapely installs, sometimes Windows will not be smart about parallel installs of Python even, some...

It sounds like the way to go here is to make OSMnx a dependency to be able to use the functions here? https://github.com/gboeing/osmnx/blob/main/osmnx/geocoder.py