Where:
Text:
Object IDs:
Time:
Time Relation:	Include start and end Include start and exclude end Exclude start and include end Exclude start and end
Input Geometry:
Geometry Type:	Envelope Point Polyline Polygon Multipoint
Input Spatial Reference:
Spatial Relationship:	Intersects Contains Crosses Envelope Intersects Index Intersects Overlaps Touches Within Relation
Distance:
Units:	Feet Meters Kilometers Miles Nautical Miles US Nautical Miles
Relation:
Out Fields:
Return Geometry:	True   False
Return True Curves:	True   False
Max Allowable Offset:
Geometry Precision:
Output Spatial Reference:
Having Clause:
Return IDs Only:	True   False
Return Count Only:	True   False
Order By Fields:
Group By Fields (For Statistics):
Output Statistics:
ReturnZ:	True   False
ReturnM:	True   False
Geodatabase Version Name:
Historic Moment:
Return Distinct Values:	True   False
Result Offset:
Result Record Count:
Return Extents Only:	True   False
SQL Format:	None Standard Native
Datum Transformation:
Parameter Values:
Range Values:
Quantization Parameters:
Feature Encoding:	EsriDefault
Format:	HTML JSON KMZ GeoJSON PBF

# records: 1

ref_no: 46339
place_name: Gympie
alt_name: null
type: LOCB
description: Locality Bounded
status: Y
currency: N
gazetted_date: 1267747200000
gazette_page: 497.0
plan_no: QPN1058
modified_date: 1526392246000
lga_name: Gympie Regional
comments: Derived from town name which was derived from Kabi language word "gimpi", indicating stinging tree (Laporta moriodes). Named and bounded by the Minister for Natural Resources 1 December 2000. Regazetted by the Minister for Natural Resources, Mines and Energy and Minister for Trade on the 5 March 2010 due to the council amalgamations under the Local Government Reform Implementation Act 2007.
longitude: 152° 40' 05" E
latitude: 26° 11' 10" S
longitude_dd: 152.66806
latitude_dd: -26.18611
origin:
history:
links:
Point:
X: 152.66806000000008
Y: -26.18610999999993