# Custom Geocode format to be used in Cesium

**URL:** <https://community.cesium.com/t/custom-geocode-format-to-be-used-in-cesium/7300>\
**Category:** CesiumJS\
**Created:** [August 15, 2018, 9:51am UTC](https://community.cesium.com/t/custom-geocode-format-to-be-used-in-cesium/7300 "2018-08-15T09:51:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ladislas\_Quazza](https://avatars.discourse-cdn.com/v4/letter/l/8edcca/32.png) [@Ladislas\_Quazza](https://community.cesium.com/u/Ladislas_Quazza)\
**Post date:** [August 15, 2018, 9:51am UTC](https://community.cesium.com/t/custom-geocode-format-to-be-used-in-cesium/7300/1 "2018-08-15T09:51:43Z")

</div>

Hi Cesium team! I've been working on a Cesium app over the last few weeks and am currently stuck. I want to create a custom geocode (I'm planning to automatically generate a json file from lon/lat coordinates that I have and give them all the necessary information) and replace the bing geocode. The aim is to only be able to search for these new custom places.

I've had a look around the forums and the sandcastle example but the one thing I can't seem to work out is the format I need to give to my json file. In other words, which keys ("location", "name", etc.) can I and do I have to include for this to work. If there is a standard somewhere I haven't managed to find it.

If you could please indicate where I could find such a standard or give me a list of things I could/should include I'd be really grateful.

I'm working with the latest version of Cesium in the latest version of Chrome.

In any case I love the library, the community and can't wait to see all the new features that you guys plan to include!

Ladislas

---

<div class="post-metadata">

**Author:** ![Gabby\_Getz](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/gabby_getz/32/7838_2.png) [@Gabby\_Getz](https://community.cesium.com/u/Gabby_Getz)\
**Post date:** [August 20, 2018, 8:47pm UTC](https://community.cesium.com/t/custom-geocode-format-to-be-used-in-cesium/7300/2 "2018-08-20T20:47:50Z")

</div>

Hi Ladislas,

The geocoding in Cesium is now done with the [Pelias Geocoder](https://cesium.com/blog/2018/08/14/geocoding-with-pelias/) instead of Bing, which is cool because it’s open source!

I would suggest taking a look at that blog post and the [pull request that the change to Pelias was implemented](https://github.com/AnalyticalGraphicsInc/cesium/pull/6453/files). It shows how to integrate a different geocoder service. Let me know if you have anymore questions.

Thanks,

Gabby

---

<div class="post-metadata">

**Author:** ![Ladislas\_Quazza](https://avatars.discourse-cdn.com/v4/letter/l/8edcca/32.png) [@Ladislas\_Quazza](https://community.cesium.com/u/Ladislas_Quazza)\
**Post date:** [August 22, 2018, 8:18am UTC](https://community.cesium.com/t/custom-geocode-format-to-be-used-in-cesium/7300/3 "2018-08-22T08:18:35Z")

</div>

Thank you for the reply! This looks like it should help me to do what I have in mind