Bryan Housel

Looks like it should mostly work if the locationSets include the `.geojson` in the identifier. Also - ATMs by default get generated automatically from the banks, so I'm not sure...

It's a good idea! I don't really think it belongs in the list of trees though. Adding it as a special tree kind of increases the complexity of the existing...

From my perspective, it would be super to just increase the tagvalue length in the database to something like varchar(2000), bump the API minor version, and move on. Inventing tags...

@tomhughes : there are a few legitimate _geo_ uses of larger tagvalues, like destination sign text or inscriptions on physical monuments, things like that. We should have some kind of...

> That will for sure not work. There are lots of downstream data processors, and you need to look at this change end-to-end - starting with osmosis for the replication,...

For what it's worth, we have merged some example code into RapiD a few months ago that allows us to write components with ReactJS, but we're not using it yet....

> could you please share the documentation or description where I could find how features comes from RapID to ID? I don’t have any documentation like that, sorry..

> If I understand @bhousel correctly, he won't merge this PR since he would prefer the solution he build in RapiD. @bhousel please correct me if I misunderstood you. I'm...

> A third possibility would be to replace the rollup build with [esbuild](https://github.com/evanw/esbuild), which as a positive sideeffect would dramatically speed up build time and would add JSX (or TSX)...

> Also another great alternative not mentioned yet is YoHours. > > Maybe iD could give an hint to use one of these solutions when starting writing opening hours manually?...