# Geopoint common Schema suggestion **URL:** \ **Category:** Elasticsearch\ **Created:** [April 24, 2020, 1:18am UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562 "2020-04-24T01:18:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Patrick\_Harris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_harris/32/45627_2.png) [@Patrick\_Harris](https://discuss.elastic.co/u/Patrick_Harris)\ **Post date:** [April 24, 2020, 1:18am UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562/1 "2020-04-24T01:18:01Z")
Geopoint needs altitude added: Use cases are: Things that move need lat, long and altitude Vehicles, humans and covid are all moving. Need to correlate on altitude. Thx for considering suggestion. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [April 24, 2020, 2:29am UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562/2 "2020-04-24T02:29:36Z")
Welcome! I agree that it would be nice to have but I don't think elasticsearch can support this right now as `geo_point` datatype does not support (I think - not tester) an additional inner field than `lat` and `lon`. @webmat WDYT? ---
**Author:** ![webmat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/webmat/32/46191_2.png) [@webmat](https://discuss.elastic.co/u/webmat)\ **Post date:** [April 24, 2020, 12:05pm UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562/3 "2020-04-24T12:05:36Z")
I also don't think ES supports that. But it would be great indeed! ---
**Author:** ![Patrick\_Harris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_harris/32/45627_2.png) [@Patrick\_Harris](https://discuss.elastic.co/u/Patrick_Harris)\ **Post date:** [April 24, 2020, 3:30pm UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562/4 "2020-04-24T15:30:44Z")
Are there fundamental limitations in ES index with regard to # of inner fields associated with a type definition? Or Does the antlr4 parser need extended to see 3 fields instead of two ? And then that change breaks existing code because all existing code uses only 2 fields. Other languages faced with similar requirements to move off of flatland into 3D (aka Java, OpenGL, Xwin ) added a new type def - point3d. Changes would then be Add geopoint3d to antlr4 processing Add range query check logic for geopoint3d Add documentation threads Etc ??? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [April 24, 2020, 4:18pm UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562/5 "2020-04-24T16:18:51Z")
May be geo\_shapes could help? See > @Igor_Motov thoughts? ---
**Author:** ![Patrick\_Harris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_harris/32/45627_2.png) [@Patrick\_Harris](https://discuss.elastic.co/u/Patrick_Harris)\ **Post date:** [April 24, 2020, 5:26pm UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562/6 "2020-04-24T17:26:23Z")
I will look at geo shape / sql thx Don’t close this quite yet From SIEM perspective the geo point / shape adds consolidated processing; in some near future the routing path will be across many links in space served by commercial satcom, connected to aircraft or connected to vehicle autopilot agents or connected to humans. Without z coordinate it will be difficult to see where all those link paths exist. For covid19 people have been looking at latitude; if altitude also included it may provide insight into environmental conditions enabling its existence. If you look at Hawaii it never reached anything close to other states. I have been thinking that the few that died may have been living or working at higher altitudes. ---
**Author:** ![Igor\_Motov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/igor_motov/32/45193_2.png) [@Igor\_Motov](https://discuss.elastic.co/u/Igor_Motov)\ **Post date:** [April 27, 2020, 5:38pm UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562/7 "2020-04-27T17:38:05Z")
We allow storing altitude with geo\_point. Please see [ignore\_z\_value](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/geo-point.html#geo-point-params) in documentation. We cannot perform any functions with it. Support for such function is something we would love to add, but we are not there yet. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 25, 2020, 5:47pm UTC](https://discuss.elastic.co/t/geopoint-common-schema-suggestion/229562/8 "2020-05-25T17:47:42Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.