afischerdev

> If we generate new segments using this update lookups.dat all users must update their segment files as soon as they get the new lookup.dat. Correct? Yes. When the server...

@polyscias All your wishes are already done: > * railway=platform [update](https://github.com/afischerdev/brouter/blob/4cae6202ff84569602a58e6b1bb9c4a28eee07e4/misc/profiles2/lookups.dat#L404) > * public_transport=platform [update](https://github.com/afischerdev/brouter/blob/4cae6202ff84569602a58e6b1bb9c4a28eee07e4/misc/profiles2/lookups.dat#L323) > * man_made=pier [update](https://github.com/afischerdev/brouter/blob/4cae6202ff84569602a58e6b1bb9c4a28eee07e4/misc/profiles2/lookups.dat#L321)

@abrensch @nrenner Are there any timelines for publishing this update?

Thanks for the reply. > Do you really think it's neccessary to change the major lookup version? I'm not sure. My understanding until now was the minor version is for...

I add a lookup without major change All deleted lines have a dummy for the index All new values are at the end of section. For testing: [lookups_no_major.dat](https://github.com/afischerdev/brouter/blob/update-lookups/misc/profiles2/lookups_no_major.dat)

What are the blocker to publish a new major lookups.dat? I don't see problem on the web clients. They will find new lookups.dat and new generated tile in segment folder....

@polyscias Ok I add the breaking entries again.

> Is there any way to test if a new lookups.dat is compatible with the older? I would think we could test a new lookup against the standard profiles. >...

> I am not worried about handmade profiles, like I wrote I did check all public available profiles I could find and no problems apart from those 4 mentioned key-values....

To get this PR a little bit forward I made a test with an new app to handle the described problems on a version change. It notified a version change...