Hi Priyanshu,
Yep, definitely sounds like a bug then, especially with what Andrea says. I'd
suggest starting by reporting it as such to the issue tracker so it doesn't get
lost:
https://osgeo-org.atlassian.net/projects/GEOS/summary
As to contributing, the devs can offer insight into that, but there's also this
page which may be of use -
https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md
Cheers,
Jonathan
---- On Thu, 28 Dec 2017 08:50:15 +0000 Priyanshu Agarwal
<priyanshu6...@gmail.com> wrote ----
Hi guys,
Appreciate the quick response. Thanks!
@Jonathan:I don't think that all data is put as JSON string, there are fields
like "__mlocate__created_by": 1, where values are not in quotes, indicating
numbers.
Also, the problem appears to be in MVT format only as GeoJSON and TopoJSON are
returning me the value in expected format, i.e., as decimal numbers.
@Andrea:
I will be happy to take this task and make improvements. Since I am total
newbie to Geoserver, I would very much appreciate if you could broadly point me
to where I should start looking or connect me with someone who can do so.
Meanwhile I'll go through the Geoserver contribution guide.
Cheers,
Priyanshu
On Wed, Dec 27, 2017 at 8:13 PM, Andrea Aime
<andrea.a...@geo-solutions.it> wrote:
Hi,yeah, I think it's a general limitation and a few output formats just don't
recognize BigDecimal (whatever gets recognized gets a special treatment,
everything else is normally turned into a string)
Formats can be improved of course, pull requests welcomed.
Cheers
Andrea
On Wed, Dec 27, 2017 at 3:15 PM, Jonathan Moules
<jonathan-li...@lightpear.com> wrote:
Hi and welcome to the list!
I've not used vector tiles myself so my reply is limited, but I can see your
JSON problem is as you describe:
"id": "27283",
"lat": "27.038510519999999",
"lng": "88.459210400000003",
They're all encoded as JSON strings and should be of type Number: "id": 27283 -
no quotes around the value.
Looking through the three GeoServer doc pages that mention "pbf", they all
demonstrate JSON that seems to be correctly encoding numbers, but I don't see
anything about configuration (maybe I missed it). I'd suggest this may be a
bug, but others who know more should hopefully be able to clarify further.
What version of GeoServer are you using?
Also - does it do it for all formats? MVT, GeoJSON and TopoJSON? -
http://docs.geoserver.org/stable/en/user/extensions/vectortiles/tutorial.html?highlight=pbf#vector-tile-formats
Cheers,
Jonathan
---- On Wed, 27 Dec 2017 10:58:33 +0000 Priyanshu
Agarwal<priyanshu6...@gmail.com> wrote ----
Hi all,
This is my first post to the list so please pardon any mistakes.
I started using geoserver recently to generate vector tiles for mapbox-gl and
am facing a strange behaviour. One of my database tables has some attributes of
'numeric' type. On the geoserver portal, their data type is being shown as
'BigDecimal'. But when I request a vector tile in .pbf format, the JSON object
on the from object shows the data as String and hence unable to perform
range-based styling. Is there some configuration I need to mention how to
interpret this particular data type?
I have posted this question on stackexcahnge in detail with screenshots and
code fragments.
Any help is greatly appreciated.
Thanks!
--
Priyanshu Agarwal
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Regards,
Andrea Aime
==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo
è consentito esclusivamente al destinatario del messaggio, per le finalità
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro
sistema. Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse,
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act (Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in
accord with its purpose, any disclosure, reproduction, copying, distribution,
or either dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the intended
recipient, please contact immediately the sender by telephone, fax or e-mail
and delete the information in this message that has been received in error. The
sender does not give any warranty or accept liability as the content, accuracy
or completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
--
Priyanshu Agarwal
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
