Welcome to the Alloy Ideas Portal đź‘‹ Here, you'll be able to browse improvement ideas raised by our community, vote on ideas you agree with or even raise your own ideas. We review all ideas raised and we endeavour to respond to all raised ideas.
Any ideas submitted will be immediately visible on the portal for others to vote on, please do not include anything in your ideas you do not wish to be shared with others.
The Issue: If an Alloy Asset happens to overlap two or more USRN's the current permit application doesnt handle this.
By using Street Manager Street Lookup API you could populate the USRN in the application from the Alloy Job location. Regardless of what usrn the asset is connected to within Alloy.
This would also ensure it is the correct USRN, instead of a potentially outdated version of the NSG within Alloy.
Hi, thanks for the idea, sounds like a couple of things here. Regarding the first scenario, there is a ticket here for this https://ideas.alloyapp.io/ideas/ALLOYWEB-I-1391
Secondly, we do use the Street Manager Street API to lookup details of the supplied URSN (for example, the special designations and street name will be from Street Manager - even if your local NSG conditions are out of date). However, we don't use the Street API to find the 'closest' street to the job. We can't guarantee closest is the right street so we're relying on the asset data in Alloy being network referenced correctly.
Having said that, a suggestion may be to make use of the Street Manager Street API to suggest the closest street, or compare the closest street to the one selected to see if they match.
We are looking at a different solution whereby instead of using 2D line strings to define the extent of road surfaces, instead use 3D polygons derived from the OS Topographical Area dataset, that way any point that intersects the polygon can be associated with it. If you use the OS Open Linked Identifiers you can join them together, although the overlaps you mentioned (where roads can cross over each other at junctions) have 'inferred links' which you would need to disambiguate manually.
This could also be extented to an option on designs, in which all items in the design are auto network referanced to the USRN found from the API.