directoryfan

Hi @kiranprajapati,
and thank your for your attention and for looking into the address format issue.

I think the issue with the search restriction and optimization is important for local directories. If someone is searching for a very popular address, then the response from Nominatin API will often not include it in the proposals for automatic completion. Even addresses from other countries are proposed.

Please take a look at the Nominatin API and params: https://nominatim.org/release-docs/develop/api/Search/

As my project is restricted to one German state how should I use these params for the search query?:

accept-language='de'
countrycodes='de'
viewbox=7.5,47.6,10.5,49.8
bounded=1

to have something like this:

https://nominatim.openstreetmap.org/search?q=Hauptstra%C3%9Fe%2015&accept-language=de&countrycodes=de&viewbox=7.5,47.6,10.5,49.8&bounded=1&format=json&addressdetails=1

The JS code is here:

https://github.com/AyeCode/geodirectory/blob/master/assets/leaflet/osm.geocode.js

And Stiofan changed it for me in v1. It will be perfect if you could add some backend settings for the advanced search like: countrycodes, viewbox and bounded. Like that, the Nominatin API will respond much faster and the user can use the proposals in case of popular street names in that country or language.

Please add this as feature request to github or please help me to to customize the osm.geocode.js.

Greetings

Hi Alex, and thank you for explaining this! This helped me a lot.

Under the place settings the timing field and under the event settings the event_dates field are both selected to display on the listings output location. And this works great, just that the event_dates field does not use the WP date format (under WP:Settings GD:Settings:Events is the format what I want to have: d.m.y)

For me this should be enough without using some extra shortcode for the archive item template, but the event_dates field does not apply the date format.

Do you think this is a bug?

Greetings, Marius

Hi @kiranprajapati,
and thank you for your help! I’ll try to be more clear about the problem with the German address format for OSM.

1. Address format for Germany

Yes, the response is O.K., it is like it should be.

[
  {
    "place_id": 169981210,
    "licence": "Data © OpenStreetMap contributors, ODbL 1.0. https://osm.org/copyright",
    "osm_type": "way",
    "osm_id": 352879183,
    "boundingbox": [
      "48.5723478",
      "48.5724337",
      "7.9127649",
      "7.9129952"
    ],
    "lat": "48.57238835",
    "lon": "7.912879965448619",
    "display_name": "10, Messingstraße, Willstätt, Ortenaukreis, Baden-Württemberg, 77731, Deutschland",
    "class": "building",
    "type": "yes",
    "importance": 0.22100000000000003,
    "address": {
      "house_number": "10",
      "road": "Messingstraße",
      "village": "Willstätt",
      "county": "Ortenaukreis",
      "state": "Baden-Württemberg",
      "postcode": "77731",
      "country": "Deutschland",
      "country_code": "de"
    }
  }
]

Just that the house number starts the string in the field display_name. But in Germany the house number is after the street name, so how can you change this?

This is how it should be, after choosing the autocomplete address string:

address.road address.house_number, address.village

like in the Nominatin docs: de street_name {street} {house_number} (https://wiki.openstreetmap.org/wiki/Nominatim/Country_Address_Format)

2. Search restriction and optimization

Please take a look at the Nominatin API and params: https://nominatim.org/release-docs/develop/api/Search/

In order to restrict and optimize the search and the country address format (feature request: could be super cool to have these options in the back-end)

As my project is restricted to one German state how should I use these params for the search query?:

accept-language='de'
countrycodes='de'
viewbox=7.5,47.6,10.5,49.8
bounded=1

Please help me, this will be great for different countries, since different countries have different address formats.

Greetings, Marius

Hi @kiranprajapati,

and thank you Kiran for your great help! The city field is saving now the right data.

1. You have some php tags in the snippet, is this OK? I have no error in the backend, it is just unusual.

2. How can I change the address format of the address field, not the city field. Now I have 5 Street – but the German is Street 5, so first is the street and then the street number.

Thank you so much for your help!
Marius

Thank you Kor for your help and snippet!

Unfortunately the code breaks the calendar widget. And between max-width:800 and min-widht:992 it does not change the break.

Would you like to take a look, maybe like that is easier for us to solve this. Thank you very much!

Marius

And now I have tried with the key timing and it is without double dates, but the format is still the wrong one.

[gd_post_meta key="timing" location='listing']

So is this a bug, why it does not apply the standard date format?

Hi Alex and thank you for the hint, I`ll try and come back to tell you, if this is working.

Is there another GD theme with 2 columns for the listings on the smartphones?

Thanks!