Async export with topographicPlaceExportMode=ALL produces duplicates in netex

entur / tiamat

Module also known as the backend for Stop Place Register ("nasjonalt stoppestedregister - nsr")

https://stoppested.entur.org

European Union Public License 1.2

15 stars 6 forks source link

Async export with topographicPlaceExportMode=ALL produces duplicates in netex #8

Closed mhicauber closed 6 years ago

mhicauber commented 6 years ago

Using async export with topographicPlaceExportMode=ALL, I get a netex file with :

All counties at the top of the file,
Then all municipalities

But, when a municipality refers to a county as a parent topographic place, the county is included a second time in the netex file, just before the first municipality refering to it.

I'll try to fix it if I get some time.

csolem commented 6 years ago

It could be related to the usage of ParentTreeTopographicPlaceFetchingIterator in StreamingPublicationDelivery

It should probably not use the parent fetching iterator for export mode ALL.

csolem commented 6 years ago

I managed to reproduce it using an integration test. Will try to submit a fix soon.