word salad. Many properties in ng11 clifton nottingham even if you think darwin has something to do with it.
Proper help please
word salad. Many properties in ng11 clifton nottingham even if you think darwin has something to do with it.
Proper help please
no “you’re” wrong. If you want NG11, put that in and you’ll get loads of properties. If you want properties within 1km of the centre of NG11 then go ahead and filter the results accordingly. Zero is (currently) the correct answer for that filtered search.
And if you think that postcode has a large area. Come up where I am and try searching in YO25!
If youre happy to make do with a “that’ll do attitude” good luck to you.
Better to cater for all rather than the few. Common sense approach needed.
User impatience and stupidity are entirely different things.
@tatemono Your wrong as I’m searching NG11 Clifton, Clifton is a location
give up on it now fellas
Hi Mark. The others believe Clifton is outside of Clifton… clearly not good at maps and clearly think people looking for Clifton want to miss Clifton and hope they look far outside of Clifton at other properties?? They need coffee. Thank you Mark and wake up Darwin quoter as even Darwin would want a circle around his town/village when searching the postcode and name of his town/village.
Proper assistance please as the search needs to return results
Can you see your adverts Colin in the your houses when you search for them by postcode and location name? As all landlords in NG11 are hidden in 100’s of properties far outside the postcode and location name and when I or anybody else searches the actual postcode and location name there are 0 results, which is an obvious error.
Have coffee please others and Open Rent to correct the error and locate NG11 Clifton in the location of NG11 Clifton as expected by landlords and users
If people had searched for NG11 Nottinghamshire then maybe show them the middle of nowhere but for people searching NG11 Clifton you obviously have to show them Clifton and not the middle of nowhere. This should be very obvious to all. Clifton for anyone unsure is a village and not located where Open Rent put the circle.
Open Rent to fix the error please quickly as if 50% of people visiting use a postcode and if they do not know the postcode search is broken they will believe there are 0 properties in NG11 Clifton and leave, losing many potential clients/ students that are studying at the University there and looking for accommodation, due to this obvious mapping error.
no way… it’s too much fun
Ah well there’s your problem then. If you want Clifton, Notts then search for that and, as I say, you’ll find lots of properties. If you want NG11, search for that and you’ll find lots of properties. If you want to live within 1km of the centre of NG11 you’ll have to wait as there aren’t any properties available yet.
I don’t think I’ve ever seen another user edit their posts as much as that either.
I think OR might have better things to do than cater to those who can’t use a simple search function correctly.
so the postcode search is broken and must ignore postcode search function to find correct results?
It is their simple search that is broken and blaming users is not the way to go.
Normally people would easily accept that NG11 Clifton should be located at NG11 Clifton, so cannot believe the ignorance of the issue and between that and that my letter t button doesn’t always function and because the public may read this I do edit my posts and not used to spending so much effort of an obvious error.
If you put in NG11 Clifton in Tom Tom / Google and any other map service it would show you Clifton and take you there, obviously and you would return the device if it did not.
Open Rent to fix
End user: “I can’t make it work, it’s not obvious, it’s simply not intuitive and doesn’t work as expected”
Developer: “Are you stupid? It can’t do that, it’s technically not possible”
End user: “It needs to work better, I haven’t got time to mess about with your poor web interface, I’d rather be off skiing”
Developer: “Well thats how it is, it’s my job to call you stupid for not immediately understanding my poor web interface and restrictions I have to work with”.
I’ve never met a developer who doesn’t blame the user for their own failings, so don’t worry you’re not alone with your opinion.
This mentally kills progression.
Workman, tools….you know the rest.
I do indeed … Steven45 (the workman) is blaming his tool (a 1km filtered search of postcode NG11) for not showing him results that lie outside that search.
When he says
he’s flat wrong. Searching for “NG11 Clifton” returns 128 properties.
Not when the 1km radius is selected.
Search on “NG11, Clifton” (a predefined option generated by OR when you enter “NG11) with a 1km radius and it brings back 0 properties.
Clifton is located in NG11.
This “problem” exists for the entire of the UK search, without doubt it will cause users to miss available properties. It can certainly be improved either by instruction or mechanism.
which perfectly demonstrates that the search is working as expected. There are no properties within 1km of the centre of postcode NG11
Your suggestion of having 1km mean a 1km boundary of postcode NG11 is logical in one sense, but it’s very difficult to implement for very little gain. Firstly, it would require a vast dataset that included the precise GPS coordinates of the entire boundary of every postcode. Search would then have to recalculate each of these hundreds of thousands of coordinates to recreate a new boundary 1km outside the postcode area and then plot the results within that. Secondly, this is very likely unnecessary for two reasons: 1) if someone is searching for postcode NG11, it’s likely that they actually want to live within that, not 1km from it, 2) the vast majority of users have no problems using the search as is. If the filters they add return no results, they expand the filters until they get what they want. The visual guide to the search helps with this and the default setting of 7km likely returns plenty of results for all postcode searches.
Anyone who is stumped by the ‘error’ Stephen has identified just doesn’t know how to use a search function that is pretty standard on any platform that involves using a map to search.
As mentioned, multiple times, if a user selects “NG11, Clifton” 1 km it brings zero results.
You CANNOT choose just “NG11”. if you type “NG11” the you can ONLY select “NG11, Clifton” or “NG11 Ruddington”, or “NG11, Gotham” etc.
This is incorrect. It is flawed. It’s that simple.
The technicalities are irrelevant to end users. Many will be left with low confidence in the product.
Theres always a solution, whether or not it’s cost effective is another matter entirely.
The search is not a problem to me, but the consumer is always right.
A quick “solution” might be:
If a user searches with a 1km radius with zero results then the system instead of returning zero it zooms out further to bring back results from say 1.5 or 2km IE the first level at which there are actual properties found.
Easy to implement, exposes users to properties still and solves the problem.
Data to back this up??
No room for improvement??
Data or assumption?
If they select 1km radius of NG11 then that’s what they want, otherwise they would select 0km
Note my “solution” above contradicts this, but it will at least show properties to the user to tempt them rather than nothing. Property portals usually extend the search criteria somewhat to something “slightly out side of range”.
Not standard at all. You are clutching.
Below are results from Rightmove using criteria “NG11, this area only.”
This works as expected, as it should.
ooo you are awful , but I like you (Richard Emery)
The way Rightmove search works, and OpenRent search works is simply different.
On OpenRent, it’s a point (ie. the centre of a postcode area, location, street, town etc) and then a search radius around it (1km, 10km, etc).
On Rightmove it’s an area (ie. postcode area, street, town) and then an additional distance beyond that (eg. + 1 mile, 10 miles).
It’s not that one is wrong and the other is correct, they are however different, and have different trade-offs. But both show the exact search areas on the map so it’s clear to all users what the search is doing.
We believe the OpenRent search allows for more fine-grained control. You can pin-point a location and a precise radius around it. Rightmove has non-regular “shapes” by default which is nice for some searches, but makes it harder to be more fine-grained. It’s simply a difference in default behaviour, but both systems allow you to search for properties in any area in the UK!
brilliant. Now please lock the thread! ![]()
Some people just hate facts, I love the silence.
“Standard” ![]()
I’ll stop now.
![]()
True Mark and if something broken and hiding adverts it needs fixing.
To all, there are no excuses to not locate NG11 Clifton Nottingham correctly so that the search works, it affects all out of city advertisers countrywide and easy to fix.
Mark, they are all deliberately omitting in the replies that the search is for NG11 Clifton and they only want to speak of NG11 to ignore the error. The postcode search will pinpoint every road and bus stop in Clifton by postcode and name but cannot actually find NG11 Clifton? The website dynamically adds 7km (5 miles) to the search which encompasses much more of the city to hide the error but this also hides the adverts again in the quagmire of others which is not the idea of advertising and adverts still cannot be found by reducing the distance as the error will then show 0 properties.
All the replies besides Mark hark on about NG11 and ignore the NG11 Clifton search parameter and error reported. They are trying to ignore the town and village names in the search box with the postcode and bewilder us and users by saying that they should not expect to see NG11 Clifton results or it even on the map if searching accurately for NG11 Clifton, even if it is suggested in the search box? Ridiculous reply to imply we must hide your adverts from accurate searches. We could run a competition for how many properties in NG11 Clifton and all will have a different answer and anybody being accurate with there search parameter would get a false/error 0, meaning paid for ads are hidden.
Open Rent to please fix quickly, as this principle error seems to affect all out of town properties in the country, meaning adverts only show in very broad searches thus favoring other adverts in the city with them having a double showing for both accurate and out of city searches not intended to find them but shown by imposing very broad search areas to find any location outside of a city, while adverts in the correct accurate location out of the city are hidden from accurate searches and only getting a fraction of the viewing potential in an imposed much bigger search area, if selected or if not selected hidden entirely, the larger search encompassing 100’s of properties, when the same postcode search in the city works, it can locate NG1 Nottingham property but cannot locate NG11 Clifton property and will show 0 results.
The error has been pointed out and as a professional service requires correcting as it gives unequal representation in the market place of properties inside and outside of the city when doing postcode searches which may be 50% of the time or more.
In a city the circle will be over your property at 1km distance but outside the city a circle maybe many many miles away from the location it says in the search box e.g NG12 Radcliffe On Trent is in error nearly an exaggerated plane ride away from the true location of Radcliffe On Trent, having to vastly change the scale of the map to even locate it. Open Rent encourage postcode searches, which OR then broaden to include the city, so this all favours city advertisers by including them in most postcode name searches that are miles away and further bias by hiding results on exact postcode name searches for properties out of the city and even further bias by showing correct results on an exact postcode name search in the city.
How many different ways are necessary to show the error?
Open Rent to fix the error quickly please. A solution below.
This is the map for NG11 Gotham (home of Batman
… you will notice it shows the exact same location for NG11 Gotham as for NG11 Clifton and a search for NG11 Ruddington returns the exact same location, so the name means nothing.
The easy and a good fix in the programming,
This will give accurate results and not the incorrect 0 results for NG11 Clifton, Nottingham, which is a very easy programming change. And also work for the rest of the country.
On submitting the form
IF search postcode is short,
TRUE IF search postcode number is less than 3 (ie city center),
TRUE search by postcode (ie NG1,NG2),
FALSE Substitute short Postcode for " " and perform regular OpenRent search on Names in input box (ie Clifton Nottingham),
FALSE search by long postcode (ie NG11 1AA).
END IF
Could also add an IF number of properties returned is zero increase results to 2km, etc, etc
Thank you and please fix quickly and have now realised it affects the whole country so at least NG11 is not singled out by returning huge search areas or 0 on an accurate search, but the error is a doddle to fix to not have to hide properties accurately located there or anywhere else.
Please fix quick and give the people a search that works as expected both for inner and out of city properties.
Why incessantly reply about NG11 and ignore the area name Clifton also in the box, as though the suggested place names in the search box are not important and people not expecting to find that place, it’s bewildering to spend all day with others avoiding the word Clifton in favour of only talking about NG11, like we all silly and forgot places have names and forgot that it is a parameter in the search box with the NG11 but still they ignore it upto present?
Anyway, correct please quickly as I really would like and expect properties in NG11 Clifton to show for a search for NG11 Clifton and 100% certain it is what all renters and clients expect and consider normal. This error is not unique and is countrywide to all postcodes outside of any city and a doddle to correct to be a working search like RightMove returning true results.
More bright side is that Open Rent will see the properties rent faster when found accurately 100% of the searches and not 50% if both the postcode and name searches worked as expected, faster renting would obviously be better for renters and landlords alike and Open Rent - and no false 0 results for people browsing exact postcode areas like Clifton.
Thank you and please correct the error quickly and do not lock the thread until resolved