search

polysteve / MobileLocater

API for Mobile Locater Services
MIT License
0 stars 0 forks source link

Geocoding being moved to be more accurate and partial matches to return results #12

Open polysteve opened 8 years ago

polysteve commented 8 years ago

Reproduce: get a match collection for an address. Results: Geometry extends along block Expected: Geometry restricted to property designated by address

polysteve commented 8 years ago

Reproduce: Get a match collection for an address.

Results: Geometry extends along block

Expected: Geometry restricted to property designated by address

hellokarl commented 8 years ago

I have confirmed that the coords are not returning from the geo coder.

search term in this example is "whittier hamden"

PelicanCorp.OneCall.Business\Core.cs Line 2201 addressesGeocoded = geocoder.DoGeocode(geocodeAddress, searchType, options);

addressesGeocoded[0] {PelicanCorp.Geocode.Address} Country: "" EPSGCode: "EPSG:4326" ErrorDescription: "" IntersectionStreet: "" Locality: "" Postcode: "" Provider: "PT" Result: Close State: "CT" StreetName: "whittier rd" Suburb: "HAMDEN" TownCity: "" Wkt: "" X: 0.0 Y: 0.0

addressesGeocoded[1] {PelicanCorp.Geocode.Address} Country: "" EPSGCode: "EPSG:4326" ErrorDescription: "" IntersectionStreet: "" Locality: "" Postcode: "" Provider: "PT" Result: Close State: "CT" StreetName: "whitney ave" Suburb: "HAMDEN" TownCity: "" Wkt: "" X: 0.0 Y: 0.0

addressesGeocoded[2] {PelicanCorp.Geocode.Address} Country: "" EPSGCode: "EPSG:4326" ErrorDescription: "" IntersectionStreet: "" Locality: "" Postcode: "" Provider: "PT" Result: Close State: "CT" StreetName: "whiting st" Suburb: "HAMDEN" TownCity: "" Wkt: "" X: 0.0 Y: 0.0

and so on . .

search request details

geocodeAddress {whittier hamden} base: {whittier hamden} IntersectionStreetName: "" IntersectionStreetType: "" Number: "" Prefix: "" StreetType: ""

searchType Street

options {PelicanCorp.Geocode.SearchOptions} AllowFuzzyCity: false AllowFuzzyState: false AllowFuzzyStreet: false AllowIgnoreState: false AllowIgnoreStreetNumber: false AllowIgnoreStreetType: false AllowIgnoreSuburb: false AllowSurroundingSuburbs: false Exact: false IgnoreStreetNumber: false IgnoreStreetType: false IgnoreSuburbOrientationWords: false Owen Heggen 9/11/2015 3:47:01 PM

Search results appear to be returning 0 for x,y coordinates.

This is most likely a provider issue.

exact search results do return coords, but others do not.

twigz13 commented 8 years ago

Some more examples from today Doing an intersection search for the following 'Skiff' and 'Whitney', 'Hamden' 'wayland' and 'Bayard', 'Hamden' 'jay' and 'franklin' 'new london'

it seems like you can replicate this issue by omitting the street type from the search.

While these searches return the correct results (franklin st / jay Street, NEW LONDON for example) the location it returns seems to be 0,0.

twigz13 commented 8 years ago

The previous locations are all returning correctly now.

However, I can still replicate this error by searching for "bch hamden"

Most mispelled addresses will take you to the closest match rather than giving you options (Eg: Search for "Old Hamden" and you will be given "Old Hill Road Hamden"), or give if you a failed search result if they are complete nonsense ("aserrtgsdr hamden" or "tea hamden")